I think server owner is too kind-hearted to ban him immediately. Perhaps he will try to talk with that supposed cheater.

wrote:

Name: Grassor
Country: Poland
Server: Wyczerpy Fans Częstochowa
Time: ~2am
Date: 15.03.2014
IP: 46.113.119.173
GUID: Unknown

Read the story by clicking here

I suggest to ban him on every railonly server, go ahead server owners.

It's pointless to ban this IP, once you check by 'whois' you'll see that its mobile 'Play' internet provider,
it's a net range of 46.0.0.0/8 and most probably, once he log off/on his IP is entirely different, so banning the whole range of 46.x.x.x just for an one guy that wasnt even really catched on cheating, but just said he have q3 hook is stupid too I think

That server Wyczerpy I suggested the owner to upgrade from 1.32 to ioquake3 for better autodownload speed, he could even turn on sv_awh for the anti wallhack protection and also xp_antiCheatLevel to 4 to detect any illegal mouse cheats xD

Oh, always wondered about that. How comes the guid can be unknown? You check status and you see unknown guid and it's so frustrating.

wrote:

xp_antiCheatLevel to 4 to detect any illegal mouse cheats xD

:>>>>>>>>>

wrote:

wrote:

Oh, always wondered about that. How comes the guid can be unknown? You check status and you see unknown guid and it's so frustrating.

This should do the work:

IP { "" { Reason: "go use proxys some other place" } }
Guid { NO_GUID { Reason: "Enter a valid CD-KEY" } } 
Guid { unknown { Reason: "Enter a valid CD-KEY" } }

by adding that to bans.txt

or sv_strictauth 1 to dissalow people joining without cdkey.
but I think camels method is more effective.

wrote:

strictauth only allows original q3 keys - gl having one.

I think it doesnt work that way anymore. because It does no longer sync guid with master server.
so original or not, may aswell work.