[Malachi]

Originally Posted by Powerlord I've heard that the SMAC version is better... this plugin hasn't even been touched in several years so I couldn't even tell you if it still works.

It works fine:

Originally Posted by Malachi Just in case anyone else would find it useful, I made a mod of this plugin that doesn't have time limits. Instead it resets on map change. Also, it warns the player when they've reached the name change limit. And when it kicks/bans someone, it notifies all the admins on the server.

I didn't test the ban functionality, but we use this on our server and it routinely kicks hackers.


I haven't had a chance to evaluate SMAC - there was a lot of stuff to look over, and it wasn't clear what some stuff did or how it did it. I really hate having to dig through code just to answer a basic question.

[emr]

Does this work with CSGO right now?

This name changing hackers are so annoying. They keep coming and coming :S

[Powerlord]

Incidentally, I forgot to mention this, but keep in mind that some games have the sv_namechange_cooldown_seconds and users can only change names this often. By default, it's 20 seconds on Team Fortress 2, so set this plugin's settings accordingly.

[Vastrix]

Hey o/
Feature Request: (if you want ;)

• ncp_detectiontime: Any chance you can Make -1 an option (For their entire stay)?
• Any chance that you can add a second "module" that checks if the name == someone else's name and if so execute punishmode(Or another punishmode var?)?

Either way, Thanks!

[Vastrix]

Maybe a note on your comment at the top of the first post:

On games that support sv_namechange_cooldown_seconds (HL2M, DoD:S, CS:S, TF2, and possibly others): You should adjust the ncp_detectiontime based on the values you use for sv_namechange_cooldown_seconds. For instance, if sv_namechange_cooldown_seconds is 20 (the default), ncp_detectiontime should be somewhere between 25 and 30.

if sv_namechange_cooldown_seconds is on 20 then ncp_detectiontime would be best on 60.
and ncp_detections on 3

because if ncp_detections is left on 5(default), it will never catch anyone if ncp_detectiontime is set to 25-30, the maximum it can catch is 1
(so it won't ever catch a namechanger...?)
Just fyi.. (hope i'm right)

ncp_detections <= (floor(ncp_detectiontime/sv_namechange_cooldown...))

Thanks!
p.s: If you agree, maybe change the default values?

[Malachi]

Originally Posted by Vastrix ncp_detectiontime: Any chance you can Make -1 an option (For their entire stay)?

Not quite what you're asking for, but my mod counts name changes by map.

[Neevar]

it seems like it only affects console name change?
I had a player who frequently changed names

But after he used steam profile to change his name and not the console, this seems to be not useful because the profile name change was done quite a number of times more than the limit set for name change.

Any fix on this?

[SuperU]

Hello, Powerlord i have a quick question what is the difference between your plugin and this one
https://forums.alliedmods.net/showthread.php?p=1931639

I know yours work with all games, but i want to know if plugin generates a a cfg to setup the config.

[Powerlord]

Originally Posted by SuperU Hello, Powerlord i have a quick question what is the difference between your plugin and this one https://forums.alliedmods.net/showthread.php?p=1931639 I know yours work with all games, but i want to know if plugin generates a a cfg to setup the config.

I haven't looked at the code for the other plugin, but from the documentation...

The main difference is how their settings work.

In this one, time is counted between each name change.

In the other one, time is counted from the first name change.

Part of the reason mine works the way it does is because it was written somewhat quickly to counter a specific attack that was going around at the time.

[SuperU]

Thanks for your answer i will try it