UrT0 Bot (aka Mandingo) is a bot for the Urban Terror chat system.
Here are some key features of "UrT0 Bot":
· Advertising Purpose
· Administration Purpose
· Statistical Purpose
ADVERTISING PURPOSE
Mandingo is able to warn the following events:
· Headshots
· Lemmings
· Flags Captures
· Flags Recover
· Killing Spree
· Top Players (End Match Players Top Skils)
· On Join Welcome (whith GeoIp support)
It's also possible to request useful info by UrT "say" command line.
Normal players are allowed to the following commands:
· [T|t]eams - Mandingo do a teams balance (an useless Teams request will be punished by a players Advise, after a predefined number of Advises players will be kick)
· [S|s]tats - Mandingo display personal player statistics
N.B.: [T|t]eams syntax mean thath "teams" command can be typed with capital or lower case first digit (Teams or teams will be considered valid, TEAMS or TeAmS will be ignored);
ADMINISTRATION PURPOSE
The most useful Mandingo feature is the Master/Protection list. Player will be able to authenticate himself as a Master with an authentication sequence.
Master are able to type following commands:
· [A|a]uth - Authentication command! (es.: Auth:aAdf) N.B.: How to get an authentication token will be discussed later
· [L|l]oadconf - Mandingo will load preexistent UrT-Rcon formatted directives filled files presents on a predefined fs directory (es.:> Loadconf:prova.cfg)
· [R|r]eload - Server will be reloaded (es.:> Reload)
· [V|v]etovote - Veto an active vote (es.:> Vetovote)
· [A|a]dvise - Admin are able to increment players advise counter (es.:> Advise:1)
· [K|k]ick - Admins are able to kick a player (es.> Kick:1)
· [S|s]lap - Admins are able to Slap a player (es.:> Slap:1)
· [N|n]uke - Players Nuke! (es.: Nuke:1)
· [F|f]loodslap - Start a 10 slaps sequence, 1 per sec, against a player (es.:> Floodslap:1)
· [F|f]loodnuke - Start a 10 nuke sequence, 1 per sec, against a player (es.:> Floodnuke:1)
STATISTICAL PURPOSE
Actually Mandingo is able to store event-triggered statsistics (DSTATS) to a file (this is useful for all players that would to follow a CW/PCW scoring without connect to the server).
DStats will be stored in HTML files. Every Round an HTML file will be generated!
Installation
Source Code:
Source code installation could be a little bit tricky depending on hosting distro! You need a set of library that you can find on cpan mirror (http://search.cpan.org) or on apt repository (if your distro is debian based). You can find a list of all packages needed at the following links (some can be shipped directly with your perl distribution)
http://urbanterror.techfusion.it/Modules-Requirements
N.B.: Modules Installation depending on you distribution method or by cpan method
bash:# perl -MCPAN -e shell
When all module dependencies will be resolved you can start Mandingo by:
bash:# perl UrtBot.pl urtoconfig.cfg
Binary Chroot:
UrT0-Mandingo deploy pack contain a CHROOT filesystem for the following reasons:
Security. UrT0 will open a listening socket (authentication backend); I don't want to generate hipotetical buffer overflow on m8 servers!
Maintainance. UrT0 will be deployed as a precompiled binary (ELF 32bit) dinamically linked, then he need some library. Admin will not looking for missing libraries on theri systems.
For these reason Urt0 deploy pack will be a little bit oversized (9 megs)!
Installation Steps:
Uncompress:
bash:# tar jxpvf UrT0-Mandingo-18012008.tar.bz2
A folder will be created (UrT0), in this folder you'll be found a chroot (UrT0-env) and Manding startup script (UrT0-Mandingo).
Chdir to the base directory:
bash:# cd UrT0
At this point you sould to configure UrT0 by editing urtoconfig.cfg present in the chroot:
(use your preferred text editor)
bash:# vi UrT0-env/etc/urtoconfig.cfg
UrtoConfig is very verbose (aid comment), you shouldn't have problem to undestand it (pay attention, wrong value may compromise bot functionality)
Now let configure Urban Terror Server.
For a full log players hits description (head, arms, legs, torso, etc etc) we must increase log hits verbosity. Set CVAR to do that:
seta g_loghits "1"
Now we need unbuffered logs:
seta g_logsync "1"
Now we should to configure something a little bit hard, first of all, where UrT Server will write log file
With the following syntax:
seta g_log "ioUrTserver.log"
Cos
Comments not found