feretheatre.blogg.se - Best xmage server for us

#BEST XMAGE SERVER FOR US UPDATE#
#BEST XMAGE SERVER FOR US FULL#
#BEST XMAGE SERVER FOR US REGISTRATION#
#BEST XMAGE SERVER FOR US PASSWORD#

If you have a public XMage server and would like to have it added to this list, please post below or message the moderators XMage - Magic, Another Game Engine. A server run by the community over at XMagePlayers, who focus on weekly events as well as a tight-knit community.

#BEST XMAGE SERVER FOR US UPDATE#

I haven't used Xmage for a little over a month, but I came back today to update and. New comments cannot be posted and votes cannot be cast. Is there any website that tracks the online status of xmage servers? 3 comments. You can also host your own server to play against the AI and/or your friends, Supports special formats like Commander (up to 10 players), Cube, Tiny Leaders, Super Standard, Historic Standard, There are two tournament types supported (elimination or swiss type handling), which can be played with up to 16 players. Public servers where you can play XMage against other players.

You can find and test new cards and features that is not yet released. BETA server is a custom xmage server that run latest developer version.

#BEST XMAGE SERVER FOR US FULL#

Official site Github Latest news Latest changes Donate XMage Today US, EURO and BETA Servers Download full BETA client. I'll start implementing above shortly.Server Name Server Address Status Ping* : :17171: 13 ms: Xmage Euro Server: eu.xmage.today:17171: 6 ms: Xmage US Server: us.xmage.today:17171: 85 m. Please let me know if you guys have thoughts on it.

#BEST XMAGE SERVER FOR US PASSWORD#

So password is visible if a user is in a same network as another user.

Encryption of server-client communication.

Things that are not included at least to the initial implementation:

Email address validation functionality.

New dialogs for sign-up and password-reset.

Things that need to be implemented In addition to the current pull request:

XMage updates the persistent DB entry with the provided password.

User enters the token and a new password to the password-reset dialog.

XMage server generates an authentication token, sends it to the email address and stores it to a temporary DB.

User enters their email address to a password-reset dialog.

Now the user can log in with their user name and password. The entry in the temporary DB is cleared and the entry in the persistent DB is marked as validated. The user name, (hashed) password and email address will also be stored to another persistent DB, with a flag indicating the entry is not validated yet.

XMage server generates a token for an email address validation, sends it to the email address and also store it to a temporary DB.

When connecting to a server for the first time, user opens up a sign-up dialog and inputs their user name, password and email address.

Then we can start extending the functionality. Reply to this email directly or view it on GitHub /issues/478#issuecomment-72770732.Īs an initial implementation I propose to start from a very simple authentication flow with a minimum user attributes stored (user names, hashed passwords and email addresses). You can also store number of games person abandoned (disconnected before the actual game finished).

Anyway, who would bother doing that? Also, people can decide if they want to play with newcomers based on number of games they played.

#BEST XMAGE SERVER FOR US REGISTRATION#

Sure, this doesn't prevent users from creating multiple profiles but registration doesn't either. The only disadvantage is that you have to teach users that they have to export their identity (pub/priv key) and store it somewhere in order not to loose their identity. You don't have to give any personal information such as e-mail. You are not bound to single username (you can use any as you are identified by your public key). There's no problem with forgotten username/password. TeamSpeak 3 has introduced password-free authentication based on that method and I must say it works quite well. My proposition is public-private key authentication. Subject: Re: Hold users in DB and users have to sign on with a password ( #478) Too much work for the average player.įrom: Mike [mailto: Tuesday, Febru7:05 PM