B
Bazerka
Guest
At the request of many customers, we've installed the following cheat protection on all our servers :
Delator 2
When used in conjunction with a client side utility (RconDelator), Delator2 server-side pk3 allows checking for the following
hacks : No Fog, White Walls, Wall/Door Hack, 3rd Person, OGC Aimbot, Glowing/Suspicious Skins and modified binaries. The file
may be obtained at : http://play.game.net/Games/Download...alofhonour/mods/cheatprotection/delator20.zip
DMZ Dogtag 1.7b
Server-side pk3 containing a script which covers : Security (disabling of Force Models, and enforcing team skins), Auto Team
Balancing, various map fixes for default MOH maps, and an Objective Text scroller. We have added additional code to this script
to allow configuration via Cvars, and to allow server owners the option to disable specific parts of Dogtag. The original file
may be obtained at : http://play.game.net/Games/Download...s/cheatprotection/zzz_beta_dmz_dogtag_17b.zip
Timber's CODE Security
Server-side pk3 containing a script which covers : modified binary detection, the ability to force all connected clients to take
a screenshot, experimental alias hack detection, and team management (ratio of Allies to Axis, and also a server wide swap team
command). The file may be obtained at : http://play.game.net/Games/Download...fhonour/mods/cheatprotection/codesecurity.zip
PLEASE NOTE :
Due to the nature of MOH server scripts, all of these packages have the potential to cause bad server performance if incorrectly
configured. However, if sensible values are used to control the protection then you should not experience any performance issues at all.
How to configure your GAME.net MOHAA server to use Cheat Protection
On the booking/custom config pages for MOHAA Default Modes / CK Realism / Evo Realism, there is now an additional tab labelled
"Cheat Protection Settings". On this page are all the cvars used to control DMz Dogtag and Timer's Code Security. Delator 2 is
purely configured and controlled via the client side RconDelator utility, and an extensive README is available in the Delator file
on our FTP.
By default, your server will be configured with Cheat Protection disabled. This means that the only functionality enabled is the
DMz map fixes. Should you want to disable the map fixes, you will need to enable Cheat Protection, and then disable map fixes along
with any Cheat Protection functionality you want disabled.
The following describes what each of the settings mean :
Cheat Protection
DMz Dogtag 1.7b
The following fields are used to enable/disable the various routines of Dogtag.
The following field is used to configure the auto team balancing. This setting only takes effect when Cheat Protection is enabled, and dmzdt_enable_autoBal is set to 1.
The following fields are used to configure the map fixes. These settings only take effect when Cheat Protection is enabled, and dmzdt_enable_mapFixes
is set to 1.
The following fields are used to configure the Security settings. These settings will only take effect when Cheat Protection is enabled, and dmzdt_enable_security is set to 1.
The following settings are used to configure the Scroller settings.
Timer's CODE Security
For further information on CODE Security Team management and rcon commands, please refer to the README in the CodeSecurity zip on our FTP.
Regards,
Jase.
Delator 2
When used in conjunction with a client side utility (RconDelator), Delator2 server-side pk3 allows checking for the following
hacks : No Fog, White Walls, Wall/Door Hack, 3rd Person, OGC Aimbot, Glowing/Suspicious Skins and modified binaries. The file
may be obtained at : http://play.game.net/Games/Download...alofhonour/mods/cheatprotection/delator20.zip
DMZ Dogtag 1.7b
Server-side pk3 containing a script which covers : Security (disabling of Force Models, and enforcing team skins), Auto Team
Balancing, various map fixes for default MOH maps, and an Objective Text scroller. We have added additional code to this script
to allow configuration via Cvars, and to allow server owners the option to disable specific parts of Dogtag. The original file
may be obtained at : http://play.game.net/Games/Download...s/cheatprotection/zzz_beta_dmz_dogtag_17b.zip
Timber's CODE Security
Server-side pk3 containing a script which covers : modified binary detection, the ability to force all connected clients to take
a screenshot, experimental alias hack detection, and team management (ratio of Allies to Axis, and also a server wide swap team
command). The file may be obtained at : http://play.game.net/Games/Download...fhonour/mods/cheatprotection/codesecurity.zip
PLEASE NOTE :
Due to the nature of MOH server scripts, all of these packages have the potential to cause bad server performance if incorrectly
configured. However, if sensible values are used to control the protection then you should not experience any performance issues at all.
How to configure your GAME.net MOHAA server to use Cheat Protection
On the booking/custom config pages for MOHAA Default Modes / CK Realism / Evo Realism, there is now an additional tab labelled
"Cheat Protection Settings". On this page are all the cvars used to control DMz Dogtag and Timer's Code Security. Delator 2 is
purely configured and controlled via the client side RconDelator utility, and an extensive README is available in the Delator file
on our FTP.
By default, your server will be configured with Cheat Protection disabled. This means that the only functionality enabled is the
DMz map fixes. Should you want to disable the map fixes, you will need to enable Cheat Protection, and then disable map fixes along
with any Cheat Protection functionality you want disabled.
The following describes what each of the settings mean :
Cheat Protection
- Cheat Protection Enable : If set to yes, enables the use and configuration of the MOHAA Cheat Protection packages that are installed. If set to no, this disables Cheat Protection and all the settings below (apart from Map Fixes).
DMz Dogtag 1.7b
The following fields are used to enable/disable the various routines of Dogtag.
- dmzdt_enable_autoBal : If set to 1, this enables the Auto Team balance routines of Dogtag. 0 is disabled.
- dmzdt_enable_mapFixes : If set to 1, this enables the Map Fix routines of Dogtag. 0 is disabled.
- dmzdt_enable_security : If set to 1, this enables the Security scan routines of Dogtag. The scans are used for controlling force models and team skins. 0 is disabled.
The following field is used to configure the auto team balancing. This setting only takes effect when Cheat Protection is enabled, and dmzdt_enable_autoBal is set to 1.
- dmzdt_autoBal : If set to 1, enables Auto Team Balancing. Start switching when there are X number more players on a team. 0 is disabled.
The following fields are used to configure the map fixes. These settings only take effect when Cheat Protection is enabled, and dmzdt_enable_mapFixes
is set to 1.
- dmz_map_mohdm2 : If set to 1, enables "mohdm2 - Destroyed Village" map fix. This will spawn a Stuka which will block the path under the map.
- dmz_mapVis_mohdms2 : If dmz_map_mohdm2 is set to 1, this cvar controls whether or not the spawned Stuka is visable. Use 1 to make the stuka visible, 0 to make it invisible.
- dmz_spawn_mohdm2 : If set to 1, enables "mohdm2 - Destroyed Village" experimental spawn kill fix. 0 is disabled.
- dmz_map_mohdm4 : If set to 1, enables "mohdm4 - Crossroads" map fix. 0 is disabled.
- dmz_grenade_obj_team1 : If set to 1, enables "obj_team1 - The Hunt" experimental grenade spam fix. 0 is disabled.
- dmz_map_obj_team3 : If set to 1, enables "obj_team3 - Omaha" map fix. 0 is disabled.
- dmz_cliff_obj_team3 : If set to 1, enables "obj_team3 - Omaha" experimental cliff block fix. 0 is disabled.
- dmz_map_obj_team4 : If set to 1, enables "obj_team4 - The Bridge" map fix. 0 is disabled.
The following fields are used to configure the Security settings. These settings will only take effect when Cheat Protection is enabled, and dmzdt_enable_security is set to 1.
- dmzdt_pauseSecurity : Number of seconds between security scans. This setting only takes effect if the Security Scan routines are enabled (that is, if dmzdt_enable_security is 1).
- dmzdt_sec_forceModel : Selects type of forcemodel security to use (client or server). If set to 1, then the value of dmzdt_securityForceModel is used to set the clients cg_forcemodel cvar value.
- dmzdt_securityForceModel : If set to 1, enables Force Models. If set to 0, disables Force Models. This setting only takes effect if dmzdt_sec_forceModel is 1.
- dmzdt_sec_playerModel : If set to 1, use the skin name set in dmdt_securityPlayerModel for all Allied players. If set to 0, clients can choose their own skin.
- dmzdt_securityPlayerModel : Name of Allied skin to force.
- dmzdt_sec_playerGermanModel : If set to 1, use the skin name set in dmdt_securityPlayerGermalModel for all Axis players. If set to 0, clients can choose their own skin.
- dmzdt_securityPlayerGermanModel : Name of Axis skin to force.
The following settings are used to configure the Scroller settings.
- dmzdt_pauseLong : Number of seconds between scroller updates. This setting has no effect if dmzdt_scroll is 0.
- dmzdt_scroll : If set to 0, use the default MOH objective text scoreboard settings. If set to 1,2 or 3 use the Dogtag scroller.
Timer's CODE Security
- g_rndShot : If set to 1, enables the forcing of random screenshots to be taken on all clients connected to the server, in TDM mode only. 0 is disabled.
- g_rndShot_time : Number of seconds between random screenshots. This setting only takes effect if g_rndShot is 1.
- g_announce : If set to 1, enables the CodeSecurity announcement. 0 is disabled.
- g_antiHack : If set to 1, enables the periodic anti-hack scan. 0 is disabled.
- g_max_allies : Team management - maximum percentage of players that can join Allies team. 0 is disabled.
- g_max_axis : Team management - maximum percentage of players that can join Axis team. 0 is disabled.
- g_min_allies : Team management - minimum percentage of players that can join Allies team. 0 is disabled.
- g_min_axis : Team management - minimum percentage of players that can join Axis team. 0 is disabled.
For further information on CODE Security Team management and rcon commands, please refer to the README in the CodeSecurity zip on our FTP.
Regards,
Jase.