ReadMe.txt

(14 KB) Pobierz
+*****************************************************************************+
* Project          : Unreal Tournament Damage Control (UTDC)                  *
* Version          : 1.7c                                                     *
* Protects against : Hooking of UT99 engine (external cheats)                 *
* Made by          : Troublesome                                              *
* Clan             : VIP                                                      *
* Cool Qnet channel: #unreal.vip                                              *
* UT admin sites   : http://www.unrealadmin.org & http://www.anticheat.co.uk  *
*                                                                             *
+*****************************************************************************+

[Information]

UTDC is a protection against hooks. It is highly configurable and will detect all publicly known hook based cheats (as of this date 29/01/06). However since the detection methods are in constant development it may contain bugs!


[Notice]

Clients will be limited to running windows(if they are checked), because they will have to run native code contained in utdcv**.dll.


[Server Installation]

1: Extract UTDCv17c.u, UTDCv17cdll.u and UTDC.ini in the zip file to your server's UnrealTournament\System directory.
2: Add the following lines under [Engine.GameEngine]:
ServerPackages=UTDCv17c
ServerPackages=UTDCv17cdll
ServerActors=UTDCv17c.SMain
3: Modify settings in UTDC.ini
4: Start server

Clients will then be asked to confirm the automatic installation of the utdc dll when they join the server. Automatic installation may fail for some clients so you may provide a download link for manual installation (see settings)

[UTDC Forum]

Find answers and post bugs on the UTDC forum:
http://www.unrealadmin.org/forums/forumdisplay.php?f=183

[Commands]

You can use these console commands to get information or trigger a check during game:

*(mutate) utdc commands
-This will show you which UTDC console commands. Work without being admin.

*(mutate) utdc settings
-This will show all current settings. Work without being admin.

*(mutate) utdc check
-This will show you who is checked by UTDC and who is not checked. Work without being admin.

*mutate utdc shot <shotpassword>
-This will send a screenshot from all players to the UT server or Screenshot server.

*mutate utdc shot <shotpassword> <playerid>
-This will send a screenshot from the player with the given playerid to the UT server or Screenshot server.

----------- Admin commands -----------
*mutate utdc memory
-This will trigger a full memory scan for all players.

*mutate utdc processcheck
-This will trigger a check of running processes for all players.

*mutate utdc allowone
-This will allow the next player who join the server not to be checked by utdc.

*mutate utdc shot
-This will send a screenshot from all players to the UT server or Screenshot server.

*mutate utdc shot <playerid>
-This will send a screenshot from the player with the given playerid to the UT server or Screenshot server.

[Settings]

You can modify these settings to decide your security/load balance. If you log in as admin you can use these console commands to modify settings contained in UTDC.ini:

----------- Enable / Disable Detection Commands -----------
*mutate utdc set utdc on
-This will enable the UTDC protection.

*mutate utdc set utdc off
-This will disable the UTDC protection.

*mutate utdc set servercheck on
-This will make the server query the clients for a check every x seconds. That will make sure that the clients run the check.

*mutate utdc set servercheck off
-This will turn off the server query.

*mutate utdc set sfrequency <value>
-This will set the time between the server queries where value is the time in seconds (3-30).

*mutate utdc set clientcheck on
-This will make the client check it self every x seconds.

*mutate utdc set clientcheck off
-This will turn off the client selfchecking.  

*mutate utdc set cfrequency <value>
-This will set the time between the client selfchecking where value is the time in seconds (1-10).

*mutate utdc set memoryscan on
-This will do a full memory scan when players join the game.

*mutate utdc set memoryscan off
-This will turn off the full memory scan.

*mutate utdc set processcheck on
-This will do a check of running processes when players join the game. Required if detection of timer programs is wanted.

*mutate utdc set processcheck off
-This will turn off the check of running processes.

*mutate utdc set packagecheck on
-This will do a MD5 check of specified packages when players join the game.

*mutate utdc set packagecheck off
-This will turn off the MD5 check of packages.

----------- Enable / Disable Ban Or Kick Commands -----------
*mutate utdc set ban on
-This will ban players who got caught.

*mutate utdc set ban off
-This will turn player banning off.

*mutate utdc set kick on
-This will kick players who fail the regular checks for a hook based cheats.

*mutate utdc set kick off
-This will not kick players who fail the regular checks.

*mutate utdc set memoryscan kick on
-This will kick players who fail the full memory check.

*mutate utdc set memoryscan kick off
-This will not kick players who fail the full memory check.

*mutate utdc set packagecheck kick on
-This will kick players who fail the MD5 package check.

*mutate utdc set packagecheck kick off
-This will not kick players who fail the MD5 package check.

*mutate utdc set timer kick on
-This will kick players who is detected with a timer program.

*mutate utdc set timer kick off
-This will not kick players who is detected with a timer program.

*mutate utdc set speedhack kick on
-This will kick players who is detected using a speed hack.

*mutate utdc set speedhack kick off
-This will not kick players who is detected using a speed hack.

*mutate utdc set safekick on
-This will only kick/ban players who got caught with a hook based cheat that can be identified

*mutate utdc set safekick off
-This will disable safekick.

------------------- Misc Commands -------------------
*mutate utdc set allow all os on
-This will turn utdc protection off for clients running linux or mac os allowing them to play on the server. This will however make the server less secure.

*mutate utdc set allow all os off
-This will turn utdc protection on for all clients and reject linux and mac os clients.

*mutate utdc set allow440 on
-This will allow clients running UT version 4.40 to play on the server.

*mutate utdc set allow440 off
-This will disconnect clients running UT version 4.40 from the server.

*mutate utdc set allow451a on
-This will allow clients running UT version 4.51a to play on the server.

*mutate utdc set allow451a off
-This will disconnect clients running UT version 4.51a from the server.

*mutate utdc set allow451b on
-This will allow clients running UT version 4.51b to play on the server.

*mutate utdc set allow451b off
-This will disconnect clients running UT version 4.51b from the server.

*mutate utdc set winampcontrol on
-This will allow clients to control winamp with console commands.

*mutate utdc set winampcontrol off
-This will disallow clients to control winamp with console commands.

*mutate utdc set forcenativespawn on
-This will force the client to spawn the check that uses native code - it can result in a crash for linux and mac clients.

*mutate utdc set forcenativespawn off
-This will make UTDC check the client OS and only spawn the check that uses native code on windows clients.

*mutate utdc set showlogo off
-This will not show the UTDC logo.

*mutate utdc set showlogo on
-This will show the UTDC logo when you join the server.

*mutate utdc set logoxpos <value>
-This will set the horizontal position of the logo where value is a number from 0 to 90 (0 being left and 90 being the right side of the screen).

*mutate utdc set logoypos <value>
-This will set the vertical position of the logo where value is a number from 0 to 90 (0 being top and 90 being the bottom of the screen).

*mutate utdc set shotwhenlog on
-This will send a screenshot of the player if he is logged.

*mutate utdc set shotwhenlog off
-This will not send a screenshot of the player if he is logged.

*mutate utdc set sendmode <value from 0 to 2>
-This will set the send mode for the sending of screenshots. There is 3 modes:
0: This will send the screenshots from the players to the UT server using the players existing connection.
1: This will send the screenshots from the players to the UT server using a new tcp connection. The port used is given in the UTDC.ini by the "ImageServerPort" field. It's not recommended to use this mode as there can be problems in some situations.
2: This will send the screenshots from the players to a screenshot server. The IP and port of the screenshot server is given in the UTDC.ini by the "ImageServerIp" and "ImageServerPort" field.

*mutate utdc set conntimeout <value from 2 to 20>
-This will set the timeout in seconds for the sending of screenshots.

*mutate utdc set jpgquality <value from 40 to 100>
-This will set the jpg quality of the screenshots that is sent to UT server or screenshot server.

------------------------- Player Screenshotting -------------------------
UTDC can send screenshots from the players to a UT server or screenshot server. Look at the above commands to figure out the commands to do it. If the screenshots are sent to the UT server, they will need to be decoded with the included "UTDCPicDecode.e...
Zgłoś jeśli naruszono regulamin