well, it is what I expected...
it's also not logged when you use a tool like qrcon or similar
I think it uses old code from a q3 sdk to access the stuff
(that's why it accesses the VM by offsets instead of an API),
this means it shouldn't be aware of GUIDs if I am right since it didn't exist in old Q3A.
If the servers would only allow clients using a safe client
that isn't supported by the aimbot we would not see any of them again
means only official 0.8.8 by OA devteam or any self compiled binary
where the offsets are not known by the aimbot.
ah btw. I will take a look at the !admin system during the week end, and if you're interested in enhanced builds join #h4l on quakenet
PS: !ban is working now(also writes the ban to file) but is no more checking if the player has a GUID or an IP address(!kick doesn't do that check at all), the stuff that checks it is broken and is looking like nonsense, I need to add some better checking...
btw. here is what the !ban entry in admin.dat really looks like
name = ^0Need^42^0Focus
guid = 2KNO3...
ip = 127.0.0.1
reason = banned by admin
made = 08/07/15 16:22:08
expires = 0
banner = console
!mute works now
LOL spammers will like this one MUAHAHAHA xD