|
1.0.0 - BACKGROUND INFORMATION 4.0.0 - CONTROLS & USER INTERFACE 8.0.0 - SERVER SETUP & ADMINISTRATION 8.1.0 - Server Setup [step by step instructions] |
8.0.0 - SERVER SETUP & ADMINISTRATION There is a Server Setup & Administration Forum available for server admins. If you are running a server and have the time, drop in there and leave a note about your server [address and so on]... the more the merrier! Also, we'll answer any technical questions in there. 8.1.0 - Server Setup [step by step instructions] 8.1.1 - Step 1: Installation Windows Here are the nessesary files: - Quake3:Arena 1.32 Point Release (Id Software FTP) Start out by installing Quake3:Arena from the retail CD. Next, run the Quake3:Arena 1.32 Point Release, making sure to install it in the same directory. Now start Quake3 to make sure that it's working. If everything is working properly, run the Urban Terror 3.0 installation. Lastly, copy the Contest Mappack into the q3ut3 directory that will be inside the main Quake3:Arena install directory. (eg. C:\Program Files\Quake3 Arena\q3ut3\) Linux Here are the nessesary files: - Quake3:Arena 1.32 Point Release (Id
Software FTP) I am assuming from this point on that you are logged in as the user that you would like to run the Urban Terror server as (ie. NOT root). I am also assuming that you have placed the nessesary files into the user account's home directory. The first thing you need to do is to create the directories for the install: $ cd ~ You will now need to copy the pak0.pk3 file from the retail Quake3:Arena CD to the directory you just created. Be warned, the pak0.pk3 file is about 600 MB so it'll take a while to copy over. $ cp /mnt/cdrom/baseq3/pak0.pk3 ~/quake3/baseq3 The next step is to run the point release file and upgrade the server to 1.32. To do this, simply make the .run file executable, and then run it: $ chmod u+x linuxq3apoint-1.32.x86.run When asked where your Quake3 installation is, point it to ~/quake3 If all has gone well up to here, you should have a fully functioning Q3A install that is patched to 1.32. To verify that it is working, cd into your quake3/ directory and attempt to start the dedicated server: $ cd ~/quake3/ You should see some text scroll past. The very first line should say "Q3 1.32 linux-i386 October 7 2002". If it does not, or if there is an error, then the install was NOT successful. Next up is to install Urban Terror. Move the Urban Terror installation zip file into the "quake3" directory and unzip it: $ mv ./urbanterror3.zip ./quake3 And lastly, the optional Contest Map Pack install. Move the mapcontest.zip file into the newly created "q3ut3" directory under "quake3" and unzip it: $ mv ~/mapcontest.zip ~/quake3/q3ut3 8.1.2 - Step 2: Configuration There are two configuration files that you need to make changes to before starting the server. The first and most important is the server config file. This file contains all the settings for your server. Here are a couple of example config files: - Internet
Server More detailed info on the different configuration options, such as Gametypes and Master Servers, can be found in the 8.2.0 - General Info section of this manual. You can also find out about all the possible game settings in the 8.3.0 - Urban Terror CVARs section. Once the server configuration is set, you'll need to set your map rotation. This is done by editing the mapcycle.txt file. The simplest way of setting up the map rotation is just to list each map, one line at a time, in the order you wish. Here is a sample map rotation: It is also possible to create more advanced map rotations. To learn more about this please refer to the 8.2.3 - Map Rotation section of this manual. 8.1.3 - Step 3: Activation When starting up the server, there are a few things that you need to add to the command line. The most important of which are: +set fs_game q3ut3 "fs_game" is used to set the game to "q3ut3", rather than the default "baseq3". "com_hunkmegs" is the amount of memory that Quake will set aside for running the server. A good way of determining the amount of hunkmegs needed, is to multiply the number of maxclients by 2.5 (ie. 20 clients * 2.5 = 50 hunkmegs). com_hunkmegs must be set in the command line when starting the server (+set com_hunkmegs 50). The default for Quake III is 56. This does not need to be changed for Urban Terror. As a general rule of thumb, you shouldn't set this value too high or Quake3 will start using virtual memory, which will slow down your computer a lot. There are a couple of other settings that can only be set on the command line during server startup: +set dedicated 2 (this makes the
server startup as dedicated. Set it to 1 to stop it from reporting
to the master servers) Here are a couple of example command lines: Windows "C:\Program Files\Quake III Arena\quake.exe"
+set fs_game q3ut3 Linux ./q3ded +set dedicated 2 +set net_IP 192.168.0.1 +set net_port 27960 +set com_hunkmegs 56 +set fs_basepath ./ +set fs_game q3ut3 +set ttycon 0 +exec server.cfg Optionally you can also create and use a shell script similar to this, it will restart a crashed server: #!/bin/bash while true Save this in a file called "startq3ut.sh", and place it your home directory. Assuming screen is installed (it usually is on Linux systems), you can run the script and start your server with: $ screen -m -d sh startq3ut.sh which would start your Urban Terror server already detached from the current client. You could then log out of your machine, and come back later on to get back into the console. To do so, run: $ screen -r If you've only got one screened process running. If you have more than one, run: $ screen -list to see all of them, and then choose the one you want to get back into by using: $ screen -r pid.host where pid.host is the line from the "screen -list" command. 8.2.0 - General Info 8.2.1 - Urban Terror Gametypes Free-For-All (gametypes 0, 1 and 2) You are against everybody and everybody is against you. After a preset number of minutes the round will end and the winner is the person with the greatest number of kills. If you are killed you will respawn at a random location on the map after a short delay. Team Deathmatch (gametypes 3) Your goal is to accrue kills for your team. After a preset number of minutes the round will end and the winner is the team with the greatest number of kills. If you are killed you will respawn at a random map location after a short delay. Team Survivor (gametype 4) Your goal is to annihilate the opposing team. The round ends when all the members of one team are killed, the team left standing is awarded a point. If you are killed you cannot respawn until the next round. Follow the Leader (gametype 5) At the beginning of each round the server selects one person on your team as a leader. The leader is designated by a red or blue helmet. A flag also spawns with your team. Your goal is to score as many points as you can. Points are awarded as follows:
Only the leader can get points from touching the enemy flag. The round ends when a leader on a team touches an enemy flag, or either team is killed. If you are killed you cannot respawn until the end of a round. Capture & Hold (gametype 6) Numerous flags are positioned around the map. When you walk over them, they get changed to your team's color (red or blue). Every minute your team scores a point for each flag of your team's color. Your goal is to have as many flags a possible at each scoring time. If you get killed, you can respawn after a brief delay. Capture The Flag (gametype 7) Each team has a home base which holds a flag. The team's goal is to get their flag from the enemy base and bring it back to their base. You must prevent the enemy from doing the same. If you are killed you must wait a short time before coming back into the game. Points are awarded as follows:
Bomb & Defuse (gametype 8) The Red Team is always the offensive team, who attempts to plant the bomb in one of two bomb spots. The Blue Team defends the bomb spots, either trying to kill the entire team or to defuse the bomb once it has been planted. The attacking team has the full round time limit to plant the bomb. Once the bomb has been planted, the clock will stop which will result the bomb exploding or the defending team defusing the explosive. The offensive team scores a point by either detenating the bomb or killing the defending team. The defensive team will receive a point for defusing the bomb or preventing the bomb from being planted by killing the attacking team. 8.2.2 - Master Servers You need to add a list of master servers to the master server list in the server config file. By default sv_master1 is set to the Id master server. You are able to add up five master servers in total. set sv_master1
"master3.idsoftware.com" 8.2.3 - Map Rotation Map rotations in Urban Terror have been redone to make them easier. Now, instead of having strange commands in your server.cfg, Urban Terror loads maps and sets information from a simple text file. By default, the map rotation file is called mapcycle.txt. This file must be placed in the q3ut3 folder of the server. You can change the name of the map rotation file by setting the g_mapcycle cvar to the name of the alternate file. For example, to use a map rotation file called mymaps.txt, you'd go to the console and type: /g_mapcycle " mymaps.txt" The map rotation file is a basic text file (you can use MS Notepad, BBEdit, vi, etc to create it). In its most simple form, the file is just a list of maps, one map to a line. When the last map is finished, the first map in the file is loaded and the process repeats. So, for example, a mapcycle.txt that looks like this: ut_ricochet Would load up ricochet, then swim, then uptown, and then start again. You can also use the map rotation file to set any server cvar. The format for this is: [mapname] [cvar] is the name of any Urban Terror server cvar (eg: g_gametype) and the value is the value you want it set to. In the following example, the first example has been extended to set cvars on ut_uptown: ut_ricochet 8.3.0 - Urban Terror CVARs First off, a CVAR is a value you can set in the console. To check the value of a CVAR you type the CVAR's name into the console with a slash in front of it. The console will then tell you the value that the CVAR has been set to. To set a CVAR, you simply type the name of the CVAR [with a leading /] and then the value you want to set it to, for example, /cg_drawgun 1. Urban Terror has added a number of new CVARs. You don't need to use them, but people who like to tweak the game may want to find out about them. 8.3.1 - Client Cvars Client cvars can be changed by anyone, but they only affect what happens on your computer - you cannot affect what other people see or hear by changing client cvars. To change a cvar, go to the console (press the ~ key) and type a slash (/) followed by the name of the cvar, followed by the value you want to set it to. For example: /cg_maxFragments 16 This cvar would set the cg_maxFragments cvar to "16". You can enter the name of the cvar without a value to see what it is presently set to.
8.3.2 - Server Cvars Server cvars can only be changed by people with access to a server. Generally, if you are playing in an online game your console commands will have no affect on the server cvars. The only time you need to worry about server cvars is if you are running a server or playing a single-player game against bots. For a description of all the Quake3:Arena CVARs see Command Keen's Quake 3 Console Page.
8.3.3 - Modified server cvars g_friendlyfire - Setting g_friendlyfire to 2 enables friendly fire but disables automatic kicking of offenders. Normally you would set g_friendlyfire to 2 for closed LAN games or during matches. 8.4.0 - Remote Control (Rcon) "Rcon" is short for remote control; it allows you to make changes to the server and gives you access to administrative commands when you're connected to a remote server. To use the rcon, you first need to enter the password by typing: /rconpassword [yourpassword] After you have enter the rconpassword you can access all the rcon capabilities, by typing: /rcon [command] 8.4.1 - Kicking a player from the server There are two ways to do this. The first is to kick them using their player name: /rcon kick [playername] The second is to use their user number on the server: /rcon status (this is to get a
list of players and their user numbers) 8.4.2 - Restarting the server using Rcon While you can't actually restart the server, you can reload the server.cfg, which amounts to about the same thing. /rcon exec server.cfg 8.4.3 - Baning an IP The first thing that you have to do before banning anyone is to add this line to the server.cfg file: set filterBan 1 Now you can add an IP to the ban list by typing at the console: /rcon addIP [ip_address] (you can also use IP masks) To remove an IP from the list: /rcon removeIP [ip_address] To list the IPs currently banned: /rcon g_banIPs See the section on new commands above for extensions added to banning functions in Urban Terror. 8.5.0 - Referees Referees are an experimental feature that has been added to help server admins manage their servers. This feature will expand and be modified as more servers start running beta 2 and admins start giving feedback about what needs to be implemented. The referee is like a less powerful version of rcon: you can set a password and give it out to trusted players. Unlike rcon, the referee has limited control over how they can affect the server. It gives them the ability to do things like mute annoying players, kick them and even ban them from the server for up to 3 hours. All referee commands start with the ref command. The basic referee command looks something like this: ref {refcommand} [{parameters} ...] Referee commands can only be used by a client who has logged on as a referee using the reflogin command with a valid password. If a password has not been set, or if the server has disabled the referee function, no one will be able to login as a referee. 8.5.1 - Enabling referees on a server To enable a referee, a server admin first needs to set the referee password: /g_refpass "password" Then set whether the referee can ban people:
Finally enable referees: /g_referee 1 Be very careful with allowing referees to ban players on your server, unless you can trust them to use the power with responsibility. Otherwise, you might find angry players boycotting your server! 8.5.2 - Logging on as a referee To login as a referee you need to ask the server administrator for the referee password. Once you have it, you can login by pulling down the Quake III console and typing: /reflogin "password" If you enter the password correctly and the server is set up to allow referees, then you will receive a message telling you that you have successfully logged in. Once logged in you can use all the referee commands. These commands and their effects are listed below. 8.5.3 - Referee commands
8.6.0 - Server Troubleshooting 8.6.1 - Why can't I get Urban Terror to run under Linux? To get an Urban Terror server running properly, you need to add this to this command line when starting the server: +set vm_game 2 +set vm_ui 2 +set vm_cgame 2 8.6.2 - Why is the hostname and other settings not showing up properly? There is a file that Quake3 uses to store default settings called q3config.cfg. For some reason, with the lastest Point Release, Id has set things up so that this file is the very last thing loaded when starting a server and changing maps. The problem with this is that the settings contained within this file will override some of your settings in the server.cfg file. There are two ways to fix this. The first will work if you plan to run only one server on the computer that you are working with. Just delete the q3config.cfg file and let Quake recreate it with your server.cfg settings as the default. The second way is to clear the contents of q3config.cfg, so that it is an empty file, and then make it read only (Linux- chmod 444 q3config.cfg, Windows - right click/properties/select read only). NOTE - If you do this, you must exec a server.cfg file when starting the server or the server will crash, due to not having any default settings to load. 8.6.3 - Why does the server try to give connecting clients files they don't need? It is recommended that allowing clients to download files be turned off. If not, when players connect, they will automatically begin to download the necessary files in order to play on that server. You can turn off allow downloads through the menus by:
It can also be done in the clients.cfg file: seta cl_allowDownload "0" 8.7.0 - Resources - Id Software
FTP |