Good afternoon. I want to make it so that a user on the server cannot change his own nickname. So that only people from a certain group (relatively admins) can change nicknames. Tell me which permission is responsible for this?
Names are User’s choice only. No other user can change them.
The only thing you can do is to ban names on your server.
4 Likes
Right now a client can only change its own nickname — there’s no way for an admin to set or correct someone else’s, even with full permissions. I’d like a server-side option, gated behind a new dedicated permission (default-denied, power-level aware like kick/ban), that lets an authorized user change another client’s displayed nickname, ideally with an optional lock so the user can’t immediately revert it.
The use cases are everyday community moderation: normalizing names to a format standard, neutralizing impersonation, and replacing an offensive name instead of kicking the person over it. Admins can already kick and ban — the most destructive actions on a server — so being unable to perform the least destructive identity action is really just a gap in the permission model. A single opt-in permission would close it without changing default behavior for anyone who doesn’t enable it.
Obviously we would need come up with solution for the 1 that is appended to a duplicate client. Perhaps just don’t append a visual 1 on the username?
In my opinion, choosing one’s own nickname should remain a personal decision for the user.
Unwanted or offensive names can already be blocked via the ban list or with the help of bots, which are running scripts. There is no need to be able to override another client’s name on the server side.
Normally, many users consciously associate themselves with their myTeamSpeak name. This name often serves as their cross-platform identity and is recognized on various servers. If a server admin can change this name at will, that very recognizability is lost. The user then appears under a name they never chose themselves, which causes unnecessary confusion.
Furthermore, this would not truly solve the problem of the appended “1” for duplicate names; it would merely shift the issue elsewhere. From a technical standpoint, unique names remain necessary.
In my view, it would make more sense to further expand existing administration tools rather than transferring control over a client’s identity to the server admin.
I am resolving this with a bot that warns by poking, and bans if not resolved in a certain amount of time, with ban time multipliers if they continue to violate.
I was just looking from a WoW guild point of view, so we all know who is who, especially for a new person not knowing how to associate a person with their in game name.