One of the greatest games I’ve ever played is Urban Terror. Urban Terror takes Quake 3 and transforms it to near perfection (in my opinion). Urban Terror is one of the the most successful open source, free-to-play, games of all time. The amount of time to play it, learn it, master it, is a great pleasure. This guide will show how to optimize and setup Urban Terror for best performance and usability.
Urban Terror is based on the Quake 3 engine that was released by id software in 2005. Since then it has been edited, refined, fixed, and added to under the name of the ioquake engine. The ioquake team has done an awesome job of keeping the engine up to date and running well as well as adding 64bit support, ogg support, in engine VOIP support… The current version of Urban Terror is 4.2 and you should be able to find it in the repositories for your distribution.
Though the default layout of Urban Terror keybindings can be gotten by with, advanced users know that having to take the hands off the default keyboard positions too many times means trouble. In a game were milliseconds count this best be avoided. Keeping grouping of commonly used keys close to your left hand is good practice. This keyboard layout groups commonly used functions but is generic and should work well for any game type. However, since I find myself playing capture the flag most of the time, the automated chat (radio commands) are for CTF (the radio commands are easy enough to change in the configuration below):
id software really knows how to make a game engine, the capabilities and options in the engine seem nearly unlimited. I’ve gone through and discovered the most important values to set on Urban Terror.
The configuration files are stored in
~/.q3a/q3ut4/. For automatic configuration inheriting, Urban Terror will look for a file called
autoexec.cfg here. Instead of going over all the settings that can be done, I’ll just provide the configuration file which has comments on all the settings.
Testing edits to the configuration can be done within the games’ console. Pressing the tilda key (
`) will bring it up. First thing I do is change
4 and turn full screen off to be able to reach the configuration in the text editor:
r_mode 4 r_fullscreen 0 vid_restart
Changes in the console will not make changes to
autoexec.cfg. Testing settings can be typed directly in the console or make the edit to the configuration and type (to reload it):
If there are errors in the configuration file they will be displayed after typing this.
Configuration file below will need a quick go-ever before using but is mostly good. Edits needed will likely be
sensitivity and maybe a few others. Forgive the syntax highlighting below, github does not correctly recognize id config files, Yeesh.