I have a script to record binaries in a seperate log (simpler and easier to use the data for me) but I was wondering whether I can specify between known cheat binaries and unknown client binaries. I was thinking perhaps disallowing players with a cheat binary whilst allowing players with an unknown binary to play (then speccing/checking them).
I know there are the g_ClientBinaries parameters (1) but I assumed this is going to kick all unknown binaries, which I don't want as i'm certain some players use custom ET builds and I don't want to kick these without any valid reason.
1 Don't allow players with unknown client executables.
2 Log unknown executables to the g_cheatLog. Note, if the server does not allow unknown client binaries the log message will be different for message.
4 Report unknown executables to admin chat. Note, if the server does not allow unknown client binaries the players will not be reported to admin chat.
So, is it possible to differentiate between known and unknown binaries? Such as et_ClientBinary( clientNum, checksum, type) where type would be 'known' or 'unknown' for example. Then in my script I can specify actions for players with a cheat binary and ignore those without.
Called when a player connects with an unrecognized client executable. Also called if the player connects with a known cheat binary.
Syntaxet_ClientBinary( clientNum, checksum )
- clientNum is the slot number of the player
- checksum is the 32 character MD5 checksum of the client executable (ET.exe)
Edited by Arcane, 11 May 2013 - 06:12 PM.