When setting up a nickname, currently, if you set to the existing nickname (of someone else), the system will just take it - no error, but suffix with a number (1,2, etc.). Can we instead prompt the user that that nickname already exists?
Did you know that this isn't just a demo?
This is our live pre-sales Q&A and support forum. Take a look around and say "Hello".
I'll need to take a look at the code base that handles this. I don't see any reason why that can't happen.
It's been added to my todo list:
Minor feature released:
Error message now displays when user tries to set a nickname that is already being used by someone else.
Some side information:
Champ, in the background, uses the nickname or the user's actual name to generate @mention names.
As a result, Champ will automatically append a number after the @mention name if a duplicate one already exists. In order to ensure that everyone gets an @mention name, this is a process that is designed to work (in order to ensure things work smoothly).
I've added a restriction on users' nickname value to ensure they must be unique. Let's see how this actually works in practice. (I've tended to err on the side of designing the system to be more forgiving in user input.)