namechanging

[uNhoL]

I haven't really looked into etpub's source / silEnT mod so dunno if these features are already there.

 

1. I've seen couple admins who are bored of people communicating thru their ingame names so I was thinking about an admin command to block player from changing his name.

 

2. You've seen hacks with namestealing features? It's annoying when you can't know which one is the real player at !list. So my suggestion is that when player changes his name, check if the name already exists and change his name to (<client number>)<desired player name>.

 

It's really annoying when ppl are communicating thru their names when they're muted and it's really annoying when some hacker is using namestealer and I can't be sure who's the real player in !list so I decided to make a thread about those things. I'm sure that there are lots of admins agreeing with me. ^^

[gaoesa]

1. The etpub offers natively the option to limit name changes.

 

2. The mute is extended starting from version 0.2.1 to all chats, including private messages and adminchat.

[uNhoL]

1. The etpub offers natively the option to limit name changes.

 

2. The mute is extended starting from version 0.2.1 to all chats, including private messages and adminchat.

 

1. I find it pointless to limit name changes because you have to wait until next map to change your name. And you still have to check which one is the hacker. It would help admins a lot to ban players by ID because the the ID shows up on his name.

 

2. Yeah but I was talking about name changes Communicating thru name is annoying.

[gaoesa]

Sorry I misunderstood the namechange thing. Yes, the namechanges are limited for all players per map unless they have the shrubbot flag the excludes them from the limit. Yep, it could be usefull to single out players who do those and issue their namechange limit to full.

 

I will think how this can be done effectively with the current database and shrubbot.cfg and can it be implemented in the 0.2.2 version. The limit would of course need to continue over map changes and therefore it needs to be a stored state. Also, I don't think it is completely fair to set it automatically to all the players who are muted.

 

The players can be renamed by their name but not by their client number. And they can then change their name again. The rename and locked name using client number is worth implementing I think. I don't think it needs to continue stored over map changes though.

[uNhoL]

Sorry I misunderstood the namechange thing. Yes, the namechanges are limited for all players per map unless they have the shrubbot flag the excludes them from the limit. Yep, it could be usefull to single out players who do those and issue their namechange limit to full.

 

I will think how this can be done effectively with the current database and shrubbot.cfg and can it be implemented in the 0.2.2 version. The limit would of course need to continue over map changes and therefore it needs to be a stored state. Also, I don't think it is completely fair to set it automatically to all the players who are muted.

 

The players can be renamed by their name but not by their client number. And they can then change their name again. The rename and locked name using client number is worth implementing I think. I don't think it needs to continue stored over map changes though.

 

Yeah you're right. It doesn't need to continue stored over map changes. And it's a good thing because admin might disconnect and forget the player whose name is locked.