UTAN Ban Manager

Version 1.03

Copyright © 2003-2007 Unreal Trusted Admin Network

What is UTAN?

UTAN basically is a central database for managing UT2004 server bans across game servers. You can sign up at the UTAN website and maintain your own ban list, which can be downloaded by all your game servers. (provided they run the UTAN Ban Manager)
The people running UTAN (aka. the UTAN admins) also provide a list of globally banned GUIDs, that are known to be either associated with warez CD keys or used by known cheaters. The UTAN admins make their best effort to keep this list up to date so you have less trouble with cheaters on your servers. Of course you don't have to accept the global ban list for all of your servers. You are free to configure the UTAN Ban Manager to only accept the bans you entered into the UTAN database.
If you need to contact a UTAN admin, please use the UTAN Forum. Note that ban appeals should go to the special Ban Appeals Forum and will only be dealt with there, not via private message, email or IRC.

What is UTAN not?

Even though UTAN bans known cheaters, it does not replace a real anti-cheat tool. The UTAN Ban Manager does not detect cheating, it merely applies the bans you can manage through the UTAN website.

What's new in version 1.03?

We have recompiled UTAN to adjust the URL that it uses to contact the UTAN database. You *must* upgrade to this version.

Installing the UTAN Ban Manager

Extract the content of the ZIP file to your server's base directory. The archive contains directory information, so the files should end up where they are supposed to be: LibHTTP4.u, UTANBanManager103.u and UTANBanManager103.ucl in the System directory and this file in the Help directory.
Add the line ServerActors=UTANBanManager103.UTANServerActor to the [Engine.GameEngine] section of your server's INI file and restart the server to load the ban manager.

Note: Clients do not need to download or install the ban manager. It will also not be sent to clients if you add it to the ServerPackages list.

Using the UTAN Ban Manager

When you first start your server after installing and configuring the UTAN Ban Manager, it might create a new log file in your server's UserLogs directory that looks similar to the following:

Start log session for xDeathMatch on DM-Antalus at 2006-03-11, 13:21:45
UTAN Ban Manager v1.03 build 2006-03-11 13:17 Copyright (c) 2003-2007 UTAN
Match started at 2006-03-11, 13:21:45
[2006-03-11 13:21:45] - Local UTAN ban database is empty
[2006-03-11 13:21:45] - Last ban update: Unknown
[2006-03-11 13:21:45] - [ERROR] No UTAN user name specified!

You need to configure the UTAN Ban Manager via your server's webadmin interface if you get an error like this. Once you configured your UTAN account name and password hash, you should get a log file like the following on the next map change or restart:

Start log session for xDeathMatch on DM-Antalus at 2006-03-11, 13:23:28
UTAN Ban Manager v1.02 build 2006-03-11 13:17 Copyright (c) 2003-2007 UTAN
Match started at 2006-03-11, 13:23:21
[2006-03-11 13:23:21] - Local UTAN ban database is empty
[2006-03-11 13:23:21] - Last ban update: Unknown
[2006-03-11 13:23:21] - Contacting the UTAN server to check for ban updates...
[2006-03-11 13:23:28] - Processing ban list update...
[2006-03-11 13:23:28] - [UPDATE] New global ban #1 [8a179dd23034a17ed315344ea82a11af] 80.200.4.87
[...]
[2006-03-11 13:23:28] - [UPDATE] New global ban #10332 [0be00dc05eb0d732c55e99e339236526] 86.208.173.252
[2006-03-11 13:23:28] - Received new ban list with 874 total bans, 846 new global, 28 new non-global
[2006-03-11 13:23:28] - Last ban update: Sat, 11 Mar 2006 11:21:12 GMT

The Ban Manager downloaded the complete list of bans affecting your server, based on the options you specified. The ban list is stored in a data package in your server's Saves directory. This is a much more efficient way of storing the bans than an INI file.
From this point on, the ban list is updated incrementally, i.e. only information about new, modified or deleted bans is sent by the UTAN masterserver. The entire ban list is only sent if the ban manager options changed, the local ban database cannot be opened or when you force a complete refresh. (see "Configuring the UTAN Ban Manager")
The UTAN Ban Manager will always generate a log file when it received a ban list update or after it kicked a player that matches a ban in the local database.

Configuring the UTAN Ban Manager

It is recommended you configure the UTAN Ban Manager from your server's webadmin interface, but if that is not possible, you can add the following lines to the server's INI file:

[UTANBanManager103.MutUTAN]
UTANUserName=
UTANPasswordHash=
bReceiveUTANBans=True
bReceiveGISPBans=True
bReceiveIPs=True
bReceiveAimbot=True
bReceiveAnnoyance=True
bReceiveSkinHack=True
bReceiveWallHack=True
bReceiveOther=True
bShowInServerName=True
LogFileNameMask=UTAN_%i_%p_%y-%m-%d_%h-%n-%s_%g_%l
LogFileTimeStamp=[%y-%m-%d %h:%n:%s] -
BanDatabaseName=

This corresponds to the default configuration. The UTAN Ban Manager will automatically fill in a name for the local ban database package, consisting of "UTAN103BanDatabase_" followed by four random digits. It is not possible to share a ban database package among multiple servers running from the same directory.

UTANUserName

This is the name of your UTAN account. Put the exact same name here as you use to log into the UTAN website. If you don't have an account yet, sign up at the UTAN registration page.

UTANPasswordHash

This is a hash of the password for your account. You can get the password hash from the UTAN website after logging in.

bReceiveUTANBans

Whether the server should accept global UTAN bans at all.

bReceiveGISPBans

Whether the server should accept your own non-global bans you entered into the UTAN database.

bReceiveIPs

Whether the server should accept IPs for global UTAN bans. It is recommended to keep this enabled because often cheaters only change their GUID while still keeping the same IP for a while. IPs associated with your own non-global bans are still included, even if you disable this option.

bReceiveAimbot

Whether the server should accept global UTAN bans with the reason 'Aimbot'.

bReceiveAnnoyance

Whether the server should accept global UTAN bans with the reason 'Annoyance'. It is highly unlikely anyone will ever be globally banned with this reason, though.

bReceiveSkinHack

Whether the server should accept global UTAN bans with the reason 'Skinhack'.

bReceiveWallHack

Whether the server should accept global UTAN bans with the reason 'Wallhack'.

bReceiveOther

Whether the server should accept global UTAN bans with the reason 'Other'. Warez CD keys without any evidence for cheating might be listed in this category as well as attepts to crash servers, so it is recommended you let the server receive bans from this category.

bShowInServerName

Whether the [UTAN] tag should be added in front of your server's name. You don't have to keep this enabled, users can also see the ban manager as "MutUTAN" in the server details, but it's less obvious.

LogFileNameMask

This tells, how the log files generated by the ban manager should be named.
The variables %y, %m, %d, %h, %n and %s represent year, month, day of month, hour, minute and second, respectively. If you include "am" or "pm" in the string, %h will be expanded to 12-hours format instead of 24-hours format.
The variables %i and %p represent the server's IP and port respectively, %g stands for the gametype and %l for the current map.

LogFileTimeStamp

This is the timestamp format to use in the log files. You can use the same percent variables as for the LogFileNameMask.

BanDatabaseName

The name of the ban database package. If left empty, the UTAN Ban Manager will automatically generate a database name.

bGetFreshList

This option should always be kept disabled. It tells the ban manager to request the entire ban list from the UTAN masterserver. If you really need to do this, you should just temporarily enable this option through your server's webadmin interface. It will be disabled again automatically after receiving a fresh ban list.

Other features offered by UTAN

If you think a particular cheater deserves a global UTAN ban, you can submit your non-global ban for upgrading in the Ban Submission Forum. UTAN also offers a GUID track service in the Traq Request Forum for server admins that need to find out more about the player(s) who used a specific GUID.
For both forums, please read the instructions in the corresponding forum's sticky thread or announcement.