?setemail

[★ CypherJF]

Currently, both SSC and Accede allow the e-mail address of a user to be set once.

 

Should user's be allowed the ability to change their e-mail multiple times?

 

Please provide feedback as necessary!

[rootbear75]

you should allow it a few times so that way people can update their emails, but having it unlimited encourages name trading

[Smong]

While offtopic, to avoid name trading you could add a ?name command. This would change your display name the next time you login. It should also be possible since the biller gets a chance to tell the server what name to give the player.

 

This is how Steam does it, fixed account name and unlimited changes to the display name. It would be up to the game server to reject or rename attempted logins from a name that is already playing on the server, for example "John Doe" and "John Doe (1)". One of the problems with this system is messaging people, you have to know their account name. The way Steam handles this is a player list in the client and a button saying something like "Add selected player to friends list".

[Cancer+]

Allow them to change it as many times as they want. If they are stupid enough to name trade, and the other guy is smart enough to put his email on it, sucks for the other guy.

[★ CypherJF]

While offtopic, to avoid name trading you could add a ?name command. This would change your display name the next time you login. It should also be possible since the biller gets a chance to tell the server what name to give the player.

 

This is how Steam does it, fixed account name and unlimited changes to the display name. It would be up to the game server to reject or rename attempted logins from a name that is already playing on the server, for example "John Doe" and "John Doe (1)". One of the problems with this system is messaging people, you have to know their account name. The way Steam handles this is a player list in the client and a button saying something like "Add selected player to friends list".

 

I like this idea, and it could potentionally be done. For example, your profile username could be the user's e-mail address. Once logged in it could utilize the first part infront of the @ for the userid until you setup a alias afterwhich you can own.

 

But, with VIE login the rejection message is hardcoded within the client ("Invalid name. Your name must start with a letter or a number. Please choose a new name."). So if someone entered in a non-valid e-mail address format the new player wouldn't have a clue of what to do. But, first login with a unique e-mail address they can be immediately bumped off until they validate they own the e-mail they provided which would be nice.

[tcsoccerman]

You should allow it x per x time period. For example, you can only change your email twice a week or something like that. It would probably discourage name trading and would allow you to always update you're email even on an old account.

[★ doc flabby]

why not just have a confirmation email sent to the email address you have to click on before being allowed to change. (much like paypal or similar)

[rootbear75]

While offtopic, to avoid name trading you could add a ?name command. This would change your display name the next time you login. It should also be possible since the biller gets a chance to tell the server what name to give the player.

 

This is how Steam does it, fixed account name and unlimited changes to the display name. It would be up to the game server to reject or rename attempted logins from a name that is already playing on the server, for example "John Doe" and "John Doe (1)". One of the problems with this system is messaging people, you have to know their account name. The way Steam handles this is a player list in the client and a button saying something like "Add selected player to friends list".

to counter this, allow any ?messages sent to the "active" display name, and the previously 1 or 2 names, to be fowarded to your inbox.

that way, 1) you dont have to give out your account details. 2) this way if you change your name, people will still be able to message you until you tell them that you have changed names

[★ Dav]

as many times as you like i think.

 

Name trading will happen anyway, at least if the e-mail can be changes its less likely to end up as fraud.

[🜲 PoLiX]

Like Dav said. It was turned off due to a high spurt in name trading and stolen names being unretrievable by the original owner. But really, name trading(/character trading) is unavoidable in any game.

[rootbear75]

maybe have a seperate password that you type in to set your email

like ?setmail

[★ CypherJF]

maybe have a seperate password that you type in to set your email

like ?setmail

This could be plausable...

[JoWie]

Or make it so the old email is notified + it takes 30 days before the change has gone through + in that 30 days you keep seeing a message at log on.

[rootbear75]

Or make it so the old email is notified + it takes 30 days before the change has gone through + in that 30 days you keep seeing a message at log on.

that, or you must confirm the change through an old email address

[★ Ceiu]

why not just have a confirmation email sent to the email address you have to click on before being allowed to change. (much like paypal or similar)

 

This idea is probably the best, save for one problem: If the user no longer has access to the email (dead domains, lost passwords, etc). Typically, this is the only reason to change the email in the first place and by the time people realize they need to change their email, it's already too late.

 

Why not simply have a command which sets a flag for the name to have it resend the registration info (?resetemail, perhaps)? This way you can check the user's new IP, Mac ID and IDData for a match. If the info matches what we already know about the user, it's probably still them. The only downside I can see would be that you may need to re-register from the same machine for the changes to take effect (depending on how the check is performed).

[Arry]

In addition, since you're considering opening up the delivery of ?message to the user's email address then you'll either need to send a verification email or perhaps limit the number of changes to changes per day(s). Otherwise spammers could keep changing their own address in order to send out spam.