Hate your name on clash? Click here

There's many of you out there who would like to change your name a second time, including myself. We've all tried messaging Supercell that we've gotten bullied with the name we had to have our name changed, but that still did not work as Supercell replied, they would like to be fair with every player. Well here's an idea: why not charge a certain amount of gems for a 2nd name change? It'll make a lot of us happier, and it'll be fair for every single player on Clash. Microsoft charges a fee for Xbox online ID changes, so I say Supercell should too (with gems). It'll be a win-win situation for Supercell and the player.

What's the quantity of gems you're talking about?

Quote:

---

Originally Posted by Lavablast

What's the quantity of gems you're talking about?

---

I'd say around the 250-450 area but at the end of the day, it's Supercell's decision. That's if this idea gets passed down to their game.

SC has already stated that there will not be any additional name changes due to account security reasons. Sorry to be the bearer of bad news.

Quote:

---

Originally Posted by Radiating

SC has already stated that there will not be any additional name changes due to account security reasons. Sorry to be the bearer of bad news.

---

Hmm, well this idea was already pitched to the game team. You're 100% right but we have the voice to change that. "Security reasons," such as??? I just needed support from the community and you were a BIG support. Thanks Rad. :)

Interesting idea, both for players and SC

If they changed their name to something stupid they deserve to be stuck with it.

Unless a friend or some other force outside of their control changes it.........

Quote:

---

Originally Posted by 0zero0

If they changed their name to something stupid they deserve to be stuck with it.

Unless a friend or some other force outside of their control changes it.........

---

That's what happened to me. My stepbrother changed my name to his name "Kevin 2.0". I'm doing this for the people who had their name changed without their consent. However, who am I to say: people who changed their name to "Deez Nuts" because it was a trend, that they can't change it anymore. This idea: to change your name for gems, seems fair. The first name change was free and was a courtesy of Supercell, I know. But if you hate your name that much (like I do), we should try and pass down this idea to the game.

Quote:

---

Originally Posted by themythTHELEGEND

Hmm, well this idea was already pitched to the game team. You're 100% right but we have the voice to change that. "Security reasons," such as??? I just needed support from the community and you were a BIG support. Thanks Rad. :)

---

SC appears to be rather firm on this topic, and it hasn't changed after many months. I'm merely quoting SC.

Glad to help. :smirk:

This could really create more problems. In your situation someone was able to access your account and change your name, which made it permanent and something you didn't like. If SC allowed players to use gems, wouldn't the same problems occur, but this time you are short a couple hundred gems and need to spend even more to change it back? Win for SC but not really for the player.

Maybe if Supercell made name changes for 500 gems available, the training time and upgrade cost might reduce to 15%!!! ;):D

If they cannot easily support name changes then they didn't develop the software to support the name change they already provided in a very robust manner.

In their account system, there should be an account anchor entity that is just a map between your account id and a recovery email. The "Display Name" should be an attribute on an [Alias] table with [ActivationDate] and [DeactivationDate] properties.

On game startup, the account id can be identified from the Google Play email address and then a secondary lookup to the Alias table can identify the display name. If they are using an RDBMS for their persistence management, this secondary lookup can be stored in a view that gets queried by the game. The "Current" display name is the one that has an [ActivationDate] in the past and a null [DeactivationDate].

onNameChange () should submit to a stored proc that enters the [DeactivationDate] for the "current" alias and enters a new record for the "new" alias.

SC would now have the ability to pull a full Alias history for any any account and identify the dates that names were changed and any player could change their name at any time (for a cost)

...you're welcome.

Quote:

---

Originally Posted by DraakarDraekonis

If they cannot easily support name changes then they didn't develop the software to support the name change they already provided in a very robust manner.

In their account system, there should be an account anchor entity that is just a map between your account id and a recovery email. The "Display Name" should be an attribute on an [Alias] table with [ActivationDate] and [DeactivationDate] properties.

On game startup, the account id can be identified from the Google Play email address and then a secondary lookup to the Alias table can identify the display name. If they are using an RDBMS for their persistence management, this secondary lookup can be stored in a view that gets queried by the game. The "Current" display name is the one that has an [ActivationDate] in the past and a null [DeactivationDate].

onNameChange () should submit to a stored proc that enters the [DeactivationDate] for the "current" alias and enters a new record for the "new" alias.

SC would now have the ability to pull a full Alias history for any any account and identify the dates that names were changed and any player could change their name at any time (for a cost)

...you're welcome.

---

Well, you're welcome too.

"you're welcome" in the sense that what I outlined is about 3 hours worth of work unless the source has a significant amount of technical debt that is in the way.

Totally agree.... this idea gets my vote

Name change for xxx amount of Gems