Explanation: [o-t] Name to Short / Unreadable

[Scuzzy]

ScuzTools ganders at people's names when they enter the server. The quickest way to private say, kick, ban, etc someone is by using their name. In order to do that we need the name to be legible and long enough that it's hopefully somewhat unique. To try and enforce that the system requires names to be at least 3 characters long and have three consecutive alphanumeric characters in a row.

Scuzzy

[zE]

Originally Posted by Scuzzy

ScuzTools ganders at people's names when they enter the server. The quickest way to private say, kick, ban, etc someone is by using their name. In order to do that we need the name to be legible and long enough that it's hopefully somewhat unique. To try and enforce that the system requires names to be at least 3 characters long and have three consecutive alphanumeric characters in a row.

Scuzzy

lol so =AS= zE is a no good nick to enter u guys server :O wtf tbh, but np.

[Ihmhi]

That's what he's saying, I think.

Does consecutive count spaces? If I went into your server as I H M H I, could I get in? What about ][ }{ /\/\ }{ ][?

I mean dude, this is why sm_admin has a GUI built into it. Yeah you gotta go into your menu, but still...

[ensiform]

This is probably the silliest excuse I've heard from someone administrating a server... Client IDs are and always will be the most reliable method of applying action to a player regardless of the engine whether it be source or quake.

[Ihmhi]

It's because scuztools uses chat-based commands. I hope it doesn't only use chat based commands...

That's like:

!ban Ihmhi
!pm Ihmhi

etc. in the chat window.

[[AE] 82694]

Actually it's a very good way of keeping unwanted trash of the server. Unfortunately it does hit none trash once in a while. There is a very popular bug going around death match where peoples name show as unconnected. It's a bug with the user name and the way it's displayed. Now when somebody connects this way their name doesn't show up or their steam ID in admin menu's so hackers/grievers tend to try to use this exploit to grief servers because admins can't ban because they don't show up. The way scuzzy has his server set up they won't even get on the server because of the name parameters.

[Scuzzy]

The system uses menus as well, but it's a hell of a lot easier and faster for us to drop to the console and type "sm_ban abc" then it is to find half a dozen /?.< characters. The guys that would come in with control characters and have no name at all show up in the character listing were a real pain in the ass, we don't see them anymore either. It's a matter of convience. 1 in 1000 people get hit by it, most of them change their name and understand the reason. If a person can't, and not having a specific eL!t3 name would prevent them from having fun, chances are they wouldn't like our environment anyway.

As for using client ids, it's not about the most reliable way, it's about the fastest way. "What's the fastest way I can get rid of this idiot so we can all play uninterrupted again." This was our solution. We don't want to admin, we want to play, this pretty much ensures that.

Scuzzy

[KubeDawg]

To ban a person in SM, the easiest way using the menu is to hit your sm_adminmenu key, goto Player Options, choose kick/ban/slap, then find the name.

Without the menu, quickly type "status" in console, find the name of choice, then copy the steamid, then type sm_ban "STEAM_ID:0:0:0" and hit enter.

Honestly, it's really not that difficult or a pain in the ass to ban someone using sourcemod. You can even modify the SM menu to remove 1 or 2 steps from the equation.

Isn't there a workaround for this issue? I mean, can't there be a list of exceptions to that name rule, so the particular name could get past that rule?

[Scuzzy]

Originally Posted by KubeDawg

To ban a person in SM, the easiest way using the menu is to hit your sm_adminmenu key, goto Player Options, choose kick/ban/slap, then find the name.

Without the menu, quickly type "status" in console, find the name of choice, then copy the steamid, then type sm_ban "STEAM_ID:0:0:0" and hit enter.

Honestly, it's really not that difficult or a pain in the ass to ban someone using sourcemod. You can even modify the SM menu to remove 1 or 2 steps from the equation.

Isn't there a workaround for this issue? I mean, can't there be a list of exceptions to that name rule, so the particular name could get past that rule?

You're talking about members who are in some cases in their 60s, giving them all the additional steps to pull a steam-id has been tried and failed in the past. The menu system is nice, but these are creatures of habit. I appreciate everyone's point of view, but this only effects very few of the people who enter our server. 99% of those affected understand and don't have a problem with it. We can't please everyone. Clan members comfort and needs trump everyone elses.

Scuzzy

[Hawk Eye]

[ban1]name
[ban2]name

Would it be possible to change the names of people joining your server that have these short names to something like the above? I think that might work out.

[Firefox11]

"][ |2()><" connected.
Admin: "][ |2()><" changed name to "I use weird names!"

=D

Because "Llama" would be too much if they didn't know about the rule.

[Scuzzy]

Originally Posted by Hawk Eye

[ban1]name
[ban2]name

Would it be possible to change the names of people joining your server that have these short names to something like the above? I think that might work out.

In TFC this is exactly how we did it, we had a pool of 50 odd names that were like "[noname] I. P. Freely". This was because we could change someone's display name (and how the server recognized them) in our server without changing their name on their computer. With the source engine it isn't that simple and the names are not stored server side. We have no way of changing someone's name without executing a command on the client's machine, and we try to avoid that at all costs. I've had multiple conversations with the SourceMod team about this issue.

Scuzzy

[ensiform]

Whats wrong with doing !listplayers snatching a list of the ids quickly from console output and then doing !action <ID> ? Thats how most other game admin mods work. Generally its either, <clientid|partial name|ip|some unique ID|number in list of objects(ban #?)>

See: Tremulous Admin / ETPub "Shrubbot"

[Circuitous]

Originally Posted by ensiform

Whats wrong with doing !listplayers snatching a list of the ids quickly from console output and then doing !action <ID> ? Thats how most other game admin mods work. Generally its either, <clientid|partial name|ip|some unique ID|number in list of objects(ban #?)>

See: Tremulous Admin / ETPub "Shrubbot"

Nothing's wrong with it - they just don't want to. End of discussion, really.

And if anyone thinks "punch in the menu command, choose the action, find the player, choose the player" is quicker than "sm_ban jackass," I got some startling news for you: you're insane.

Shit, y'know what's even faster?

bind g "messagemode sm_ban"

g -> "jackass" -> enter

[Iggy]

Originally Posted by Circuitous

End of discussion, really.

I agree. We are through here.