Custom skins
	Way more skins than those offered by the Player Setup (Preferences) can be used. The intensive research with the UnrealEd texturebrowser resulting in a list of over 100 textures has mainly been done by (tlgm)Clalan, and as social as he is, made public despite ©atalyst's efforts to keep this a secret. Fairly complete lists can be found on the Rock'em Hard site and the (tlgm) site. These textures are not designed to be used as skins, but since UT demo needs them anyway, they can be used so. The unofficially adopted [THC] clan skin is the 'botpack.jimpacthammer' texture. It has been used in the interface, and was the base for the corporate image of the clan. To use this or other game textures, the code has to be introduced in the user.ini file of UT demo. The following information needs to be replaced with the texture code: skin = texture code face = texture code The custom skin will not show up in the Player Setup, and changes in the Player Setup can cause the loss of the custom skin. The best way to take a look at the introduced skin is with behindview 1 or by gently committing suicide.
	Keybinds
	The Controls and Input Speechbinder (Preferences) offer a lot of options to tweak the game, but even more tweaking can be done by introducing the keybind codes directly into the user.ini file of UT demo. key = say something: the message will appear as text, "something" key = speech code: the code represents a vocal expression, get a list for more info key = setname [RwS]RockHard: the name of the player will be changed to "[RwS]RockHard" key = onrelease keybind: the keybind will be executed only on release key = behindview 0: switches the view to first person key = behindview 1: switches the view to third person key = suicide: this one is lethal... but fun anyway The best part about introducing keybinds directly into the user.ini file, is the fact that it becomes possible to put multiple functions behind a single key. With a little creativity this can provide unique effects. The functions can work simultaneously by use of the command separator: key = function | keybind: combines multiple functions behind a single key
	Tweaking of the screen
	When it comes to effectiveness, tweaking the screen is quite important. The point is to see as much as possible, but without overburding the power of your computer. So in the first place, a reasonable combination of the available parameters in Video and Audio (Preferences) has to be found. Once familiar with the game and features, it is very useful to try to play without visible weaponhand. After all, the weapon on the screen takes away a considerable part of the environment, and can theoretically hide another player trying to fire a 6-pack of rockets up your ass. Playing with or without weaponhand can be set in Game (Preferences). For the same reason it is also recommended to remove all useless interface information from the screen. This can be done in HUD (Preferences). Probably the most important tweaking is the FOV, the field of view as it is projected on the screen. A low FOV provides high detail on a narrow part of the environment and low 3D effect, while a high FOV provides low detail on a wide part of the environment and high 3D effect. The choice of the FOV is very personal. The default FOV is 90, and theoretically a FOV up to 180 makes sense. Experimenting with the FOV is easy by introducing different values in console: fov angle: the field of view as projected on the screen When a certain FOV is preferred, best is to introduce the chosen value in the user.ini file as the new default FOV: defaultFOV = angle: the default field of view as projected on the screen
	Admin cheats
	Serving a game doesn't only provide a ping 0, it also makes possible the use of some hilarious cheatcodes by way of console commands. The first command to introduce is the administrative login: adminlogin password: gives the player the administrative powers Once this is done, The show can begin: fly: allows to fly around ghost: allows to fly around and move through walls god: gives invincibility slomo speed: changes the speed of the game, 1.0 is normal playersonly: pauses all non-players, great for screenshots allammo: increases the ammo of all obtained weapons to 999 addbots number: adds a number of bots to the game allammo: increases the ammo of all obtained weapons to 999 killpawns: kills all bots These cheats are just a selected few, way more cheats are available on the Epic Games site.
	Recording a game
	UT demo can record a game by way of a specific '.dem' file. The commands that need to be introduced in console are next: demorec name: starts the recording of the game stopdemo: stops the recording of the game before the game is ended demoplay name: plays back the recorded game demoplay name?3rdperson: playback in behindview 1 A recorded game should be viewable on every computer with UT demo installed. However, platform bugs have been reported. It is uncertain what viewing options (F5 and behindview) remain when playing back a recorded game. Another bug that can be resolved is caused by the fact that each computer has its specific speed and framerate. This may result in an unstable playback of the game. The following command is used to avoid this kind of problems: demoplay name?timebased: playback is based on the exact time Either way, the recorded game can not be played back using anything but the UT demo engine. On a final note, PC's may have problems creating or playing back demorecs. A patch to correct this problem can be downloaded (mcm290.tripod.com/videopatch.zip).