RELEASE: AntiBS AntiCheat mutator

[worluk]

Hi,

due to continous new cheats and hacks we (roladder.net) had to do something. This something is an AntiCheat mutator. It will recognize and log certain cheats that were made public recently. It's up to the serveradmin wether the mutator just logs, kicks the cheater, session bans or bans for good. The mutator also logs 16bit users, it will not kick them however

It will be required in ladder matches from this week on and I hope more server admins will make use of this to stop those annoying little kiddies.

The mutator comes with a readme on howto install it. If you got questions feel free to post here, write me a PM or join #roladder on quakenet.

Here is the link

regards,

worluk

 

[Бользен]

Is it a tested version? Any stability issues? Will it work with the CC addon?

 

[worluk]

It is tested
so far we didnt have any stability problems pure or with TeamReadyMutator
And yes it will work with CC

 

[Бользен]

Good, good... Russian community server will be running it for sure.

Thanks for your work guys!

 

[Бользен]

All right, I must be missing something. It says:

Dont add the mutator via the webadmin!

But how do we alter the settings?

Also, is there a way to track the bans?

 

[worluk]

All right, I must be missing something. It says:


But how do we alter the settings?

Also, is there a way to track the bans?

The mutator is added via ServerActors. So far you have to do changes through the ini. Didnt get around to add webadmin settings. You can make the mut log to a seperate filewith bUseCustomLog, the filename is specified with the line below. If you do so, make sure the UserLogs folder in your RO folder exists. It should be created but, well, just make sure its there

Bans bans will only happen if you set WhatToDo to 3 and should be found as other bans too.

 

[Бользен]

The mutator is added via ServerActors. So far you have to do changes through the ini. Didnt get around to add webadmin settings. You can make the mut log to a seperate filewith bUseCustomLog, the filename is specified with the line below. If you do so, make sure the UserLogs folder in your RO folder exists. It should be created but, well, just make sure its there

Bans bans will only happen if you set WhatToDo to 3 and should be found as other bans too.

Thanks for clarification. I guess a separate log is not really necessary if all the bans made by this mutator are reflected in Defaults----> Access Policies list. Am I right on this?


Also if I want to set a permanent ban for violators:

[AntiBS.ROChecker]
Checks=(FName="AntiBS.u",MD5="92072963087c39f1a34b7b4ea60bc7a7",MD5Type=2,GUID="103F303948B1AF89C3D87C9C89B06FC2",MaxGenerations=1)
WhatToDo=3
TimeoutSeconds=60
bKickOnTimeout=false
bCheckSets=false
bUseCustomLog=false
LogFileName=AntiBS

That means
0=do nothing (what's the point of having it by default?)
1=kick
2=kick+sessional ban
3=global/permanent ban

Is that right? bCheckSets=false - shouldn't it be "true" or something as well?

Finally - where do I check 16bit users detected on the server? Is there a separate log for it?

Thanks

 

[Atomskytten]

Did not know for certain that hacks/cheats existed for RO. Just for information only, so I know what to look for if a player is suspiciously good, what kind of cheats/hacks are being used by the bloody cheats? Wallhacks, aimbots etc. etc.?

 

[Бользен]

Yeah, it looks like the thing really works We've just got the first cheater banned on our server.

 

[Deeival]

Nice to hear that

 

[Zetsumei]

Did not know for certain that hacks/cheats existed for RO. Just for information only, so I know what to look for if a player is suspiciously good, what kind of cheats/hacks are being used by the bloody cheats? Wallhacks, aimbots etc. etc.?

No recoil, no sway, wallhack, see through smoke, instant reloading, infinite stamina. Stuff like that ;p.

Aka you can't track it with normal sense, beside retards using it that obviously show it.

 

[[5thW]Rehakles[TRO]]

looking forward to see some swines removed from certain servers. Once again, nice job there, worluk

 

[Machoman]

I would be thankfull if someone is able to write the config to:

1

 

[worluk]

[AntiBS.ROChecker]
Checks=(FName="AntiBS.u",MD5="92072963087c39f1a34b 7b4ea60bc7a7",MD5Type=2,GUID="103F303948B1AF89C3D8 7C9C89B06FC2",MaxGenerations=1)
WhatToDo=3
TimeoutSeconds=60
bKickOnTimeout=false
bCheckSets=false
bUseCustomLog=true
LogFileName=AntiBS.log

will log to ./UserLog/AntiBS.log and ban cheaters (16bit will still only be logged)

 

[Machoman]

Thx for it... This is what I wanted...

If I set my config to 16 bits and go in, I would see the log and then I can delete my ban by webadmin, isnt it?

Thx.

 

[[5thW]Rehakles[TRO]]

Thx for it... This is what I wanted...

If I set my config to 16 bits and go in, I would see the log and then I can delete my ban by webadmin, isnt it?

Thx.

=>

will log to ./UserLog/AntiBS.log and ban cheaters (16bit will still only be logged)

I believe he answered that question even before you asked....

No Ban for using 16bit, only a log-entry...

 

[Machoman]

Thx all for your help... I've done it and it works perfect... It has logged my id and the reason...

Nice work...

 

[Бользен]

The only problem I have is AntiBS.log.tmp which is locked by the system (win2003), there is no such problem in unix, but that's how different OS handle opened files and not really mutator related .

 

[Deeival]

The only problem I have is AntiBS.log.tmp which is locked by the system (win2003), there is no such problem in unix, but that's how different OS handle opened files and not really mutator related .

We have the same problem with a win server here.
Just shut down the server when you want to check the file.

 

[Бользен]

Also the log is quite messed up with all those ignoring spectator lines and returning 16bit users (got like 10 of them for the last 24 hours!!!) Still dont know what to do with em - ban or not?

Furthermore, has it been tested against norecoil? I have some reports it does not detect it. Not sure if it's true but seems like a thing to look at for the next version.