DELATOR 2.0 for MoH:AA
There's two new owls in town...

This is the remote scanner app. It takes the output from the server mod and process it looking for relevant info. It's made up of 4 parts:

• Server Management:
  
  This is the main Delator screen.
  
  
  
  When you first start the app, set up your server details (IP, port and rcon password). The 'Start' button initiates the scanning process, whereas the 'Stop' button stops it (obvious :-P).
  
  The Scan players interval stands for the minutes delator would rest before a new scan of the player's settings (i.e: skin used and other details). Recommended value is 5 minutes for regular servers, or 3 minutes if your server is a conflictive one. The minimum value is 1 minute.
  
  The Patrol server setting stands for how often your server will be scanned for banned IP's. The minimum value is 30 seconds, but most of the time a 45/60 seconds interval will work even better. Both timers are represented by an associated progress bar, so that you can have an idea when the next scan is going to happen.
  
  All of the previous settings can be edited on the fly (Delator will stop scanning automatically), but the safest way to do this is pressing the "Stop" button and then adjust the settings to your liking.
  
  You can set also the following options:
  
  
  • Warn on non-optimized connections: Will warn you if a player with a broadband connection is playing on your server with a wrong network setting (i.e.: modem or ISDN). This can cause the player to experience lag on some complex maps, and can be solved easily by him typing set rate 25000 on the console (or entering the Multiplayer Options screen -F2- and selecting an appropiate connection). You can change the default message by editing the contents of the text box (the $name string will be substituted with the player's name).
  
  
  • Log Delator output to file: Enabled by default, it will record every event to the delator.log file on the Delator folder.
  
  
  • Run in Silent mode: Disabled by default, it will make Delator run unadvertedly. It won't kick/ban any player, nor throw any warning through console, but still it will log events into the log file.
  
  
  
  
  The additional info panel shows further details about your server. The server OS is relevant for ModDelator, since it will tell you whether you can use the Scheduled Commands feature on your server. The Cheat indicator will warn you if your server is running with cheats enabled (which will render Delator useless and make happy a lot of people); also, when cheats are enabled the detection for modified binaries is disengaged automatically; don't use "modified binaries" detection when cheats are enabled or all the players on your server will be kicked!!. There are two additional indicators showing the status of ModDelator and DMz DogTag.
  
  The Mini Console applet allows you to type commands on it as if you were using the real server console (i.e.: you shouldn't use the 'rcon' prefix). The 'copy' button copies console contents to the clipboard, whereas the 'clear' button empties it. You can send commands to the server even when the scanning process is not running, as long as your server details are correct.
  
  On the lower part of the screen you can check the list of the players currently connected to your server, his client number, ip, ping and the skins they're using. This list gets updated when players are scanned, not when patroling the server. By clicking one of them two buttons will appear, allowing you to kick him or ban him (either indefinitely or for a certain number of days). On the top of the list you can check the current map and game type the server is running, and also how many seconds have passed since the latest succesful connection to the server.



• AntiCheat Management:
  
  On this tab you can setup which cheats Delator will be scanning for. Every cheat has an associated punishment which will be effective if scanning for it is enabled. There are three punishment levels: Warning, Kick and Ban (either indefinitely of for a certain number of days).
  
  
  
  On the lower part of the screen you can customize the message displayed whenever a cheater is catched. You can use the following variables for this purpose:
  
  

  $name The nickname of the cheater
  $IP The player's IP
  $cheat The cheat he was using
  

  * The Glowing Skins module is the one already included on Delator 1.0 which became his core component, but it has been updated so that now you can copy/paste skin names and they work without you deleting every single space at the end of each line. Also, it's no longer case sensitive.
  
  * Support for Modified Binaries detection is still experimental (and thus, disabled by default). Use it with caution! You shouldn't use it if your server runs with cvar "cheats" set to 1; else, all the players on your server will be kicked!! Also, it presents and undesirable side-effect: legit players will see some errors on his console whenever a scan is passed. However, this errors are harmless and don't damage the game in any way.



• Clan Management:
  
  This tab is reserved to clanserver's admins, and is almost identical in features to those already present on Delator 1.0, with the only addition of the "Make private" option. To make use of this features you should fill in the textboxes with your clan tag and the password required for private clients.
  
  
  
  Making a server private: Even if you setup all your server slots as private ones and restart it, the public player that were already on the server will rest connected until either they leave or you kick them. When you click the Make private button, a message will be displayed every 10 seconds asking them to leave. After one minute, those who are still connected will be kicked. You can custom the warning notice by editing the textbox contents.
  
  Reserved skins. If you want to scan for reserved skins, click the required checkbox. Click the "View/Edit reserved skin list" and add/remove any skins according to your preferences. It has been updated so that now you can copy/paste skin names and they work without you deleting every single space at the end of each line and it's no longer case sensitive. Add only one skin name per line. The skin name is not the .pk3 file name, but the one appearing on Multiplayer options in MoH:AA. You can custom the warning message, and you can use also the $skin variable, which contains the name of the offending skin. You can also setup the punishment level for a client found using a reserved skin without the appropiate private password.
  
  Private/Public clients. If you would like to scan the private/public use of every slot, click the first checkbox. You can custom both warning messages sent by Delator, by changing the text and using two variables; $name (that would be replaced by the suspicious player nick) and $IP (the players address).
  
  Thus, if a player called IamUndercover with the IP 256.255.255.255 is using a private slot, the message:

  
  
  Warning: Public client using private slot. Player: $name IP: $IP
  
  becomes:
  
  Warning: Public client using private slot. Player: IamUndercover IP: 256.255.255.255
  
  

  If you custom the punishment level for any user, both private and public, found using an inappropiate slot.



• Penalties Management:
  
  On this tab you can setup how the different punishments will be applied to non-legit players.
  
  
  
  On the top of it you can setup the penalties conversion, i.e.: you can make a number of warnings become an automatic kick for that player, or setup an automatic ban on him when he reaches a number of kicks. If one player is breaking three rules at a time, and everyone of them is punished with a kick, it will count as three kicks for conversion purposes, even if, of course, he's kicked only once. Set warnings/kicks to 0 to prevent penalties conversion.
  
  The three lists provided contain all the history of Delator warnings, kicks and bans. By clicking an item, you can select either to remove it -so that it doesn't count towards punishment conversions- or convert it into a ban (both a warning or a kick).
  
  If the item clicked was an already existing ban, you can select either to remove it or transform it into a wider restriction, by either banning the appropiate net subrank or even the whole provider (not recommended). Temporary bans are automatically deleted when Delator starts if the required amount of days has passed.
  
  Last, but not least, on the bottom of the screen you can customize the banning notification. Available variables are $IP, $date and $reason (standing for the offending IP, the ban's starting date and the reason why that IP was banned).