CodeSecurity 1.4

Click on download to download CodeSecurity 1.4

Install notes
(version 1.4)

You gotta put this file into the server's MAIN directory. That's all!
IMPORTANT: If you're using ANY OTHER mod wich has modified DMprecache.scr (like DMZ Dogtag's mod) please edit it's DMprecache.scr and at the end add the following line: exec global/codesecurity.scr

Usage

Set a few new variables in your server's config file:
sets g_rndshot 0 // 0 to turn off and 1 to turn on the random screenshot during TDM
sets g_rndshot_time 1261 // seconds beetween the random screenshots (a random time is added too)
sets g_announce 1 // this is the announce message I wrote .. you can edit that if you want
sets g_antihack 0 // this is the old fashioned antihack test (the cheat protection test)
sets g_instashot Initialized! // this is just to let you know ... instashot ready
seta g_instahexen 0 // to initialize the hack-scan (aka hexen ^.^)
sets g_max_allies 0 // see Team management
sets g_max_axis 0 // see Team management
sets g_min_allies 0 // see Team management
sets g_min_axis 0 // see Team management

use sets so you can check these settings from ASE (do NOT use LameSpy! ^.^)

inclueded in this ZIP you can find our alias config file ... use it for easier administrating.

To use this script / features:
1. hack scan
You can see if someone is using hacked MOHAA.EXE with this feature. Also if any of the cheating command he's using (without honesty.cfg) it will appear. If you see any value set to 'hacked' after dumpusering someone then make a screenshot and feel free to kick ban him. If you see any of the cheating commands set to 1 then do the same ^.^
-=WARNING! Do not dumpuser anyone in the middle of a hack-scan!=-
-=note: at every scan it sets a random number on all clients. make sure to check that too! If it's missing or not the same than others then he has his setu command hacked=-
a. instantly
Call this from console:
rcon set g_instahexen 1

b. periodically
to enable periodic hack scan write this:
rcon set g_antihack 1
to disable:
rcon set g_antihack 0

2. insta screenshot (the best feature! ^.^)
You can force ppl to make screenshots with this command. On the screenshot there will be a random number too to verify it's not a premade screenshot.
also (if all is okay) then it prints on the server the random number for the shot (so you can check the log file)
call this from console
rcon set g_instashot 1

3. the alias-hack scan (to be sure that the guy doesn't has his alias command altered)
-=note: this feature is not fully tested! but it has to work like this=-
This feature is to make sure that ppl on server did not hacked their alias command to prevent this script (or any other) making alias on their side.
call this from console:
rcon set g_magicword <anything you just want!>
make sure the word you entered is only on word (so no spaces!) and it's not "default"
example here:
rcon set g_magicword AsagiRyuuKenjutsu
then everyone will say like this (let's say the random number is 123)
Player: AsagiRyuuKenjutsu - 123
The one who misses to say this ... has his alias hacked.

4. Array / name management
There are many cases when you can't dumpuser someone cause a special character in his name ... this part is developped to kick their asses.
-=note: if someone has space in his name then use " " instead of this feature!!!=-
-=Example: rcon dumpuser "John Doe"=-
First you need everyone's arraynumber. Call this command:
rcon set g_saymyname 1
Then the one with bad-name can be forced to change his name to RenamedSoldier by:
rcon set g_badname <array number>
From now on you can dumpuser him as:
rcon dumpuser RenamedSoldier (yes~! bind it to a key ^.^)

5. Team management
-=note: this feature is not a big deal I know ... but it was requested ^.^=-
a. Swapping teams
You can make everyone to swap their teams. So all axis will become allied and all allied become axis.
you can call this from console by this command:
rcon set g_dotheswap 1

b. Maxing teams
You can manage each side by maxing the ppl who can join that side. For example if you run an Omaha only server and you're bored with ppl who always join Axis (the easier side) then you can max the Axis player's number to 6 or 8 (or any depending on the maxplayers)... with that you can make their job harder (Omaha is good if you play a 6 axis vs 10 allied for example). This feature was requested by an Omaha only server's admin ^.^
to maximize allies:
rcon g_max_allies <x>
to maximize axis:
rcon g_max_axis <x>

x is the PERCENTAGE of persons you want to be able to join that team.
set the values to 0 for unlimited person.
If you set both make sure that the sum of max_allied and max_axis is equal or higher than 100%. If these values sum set lower, then the script automatically sets both to unlimited.

also to set a minimum amount for the teams, set it by:
to minimize allies:
rcon g_min_allies <x>
to minimize axis:
rcon g_min_axis <x>

Let's see an example cause it may seem complicated:
you want min. 6 allies and 3 axis but you don't want more than 33% of the players joining axis you've got to set the following:
g_min_allies 6
g_min_axis 3
g_max_axis 33

There are 6 person on the server (3 axis and 3 allies) ...
Since the 33% of 6 is equal 2 the script would move one person to allies. But you want minimum 3 axis so the script will increase the amount of alloved axis players to 3.

So to say the numbers are working like this:
Allowed axis players = the <g_max_axis>% of the total active players but not less than <g_min_axis>
Allowed allies players = the <g_max_allies>% of the total active players but not less than <g_min_allies>

This part is going by the player's arraynumber not clientnumber (huh? ^.^) ... so it's not usefull on clanwars!!!

-=TO INTEGRATE THIS SCRIPT INTO ANY ANTI-CHEAT PROGGIE=-

integrate CODE's insta-hack-scan by the following:
everytime before (like 1 or 2 seconds) the anti-cheat-scanner checks for hacks call for
instahack-scan with the following command: rcon set g_instahexen 1
Also in the hack-scan check the values:
0 - clean
1 - means cheating ... but no mohaa hack
hacked - hacked MOHAA exe
or you can simply make kick all who has different than 0
also check for the random number. the script sets a cvar on server: random_number wich is the same as on all clients. This must be checked or else the SETU command could be hacked.