Keybinding
& Aliases
Version 1.03 – 29-Oct-00
2 The UT System
Console and the Advanced Options. 1
5 Useful Aliases
& Keybinds. 52
This keybinding and alias guide for Unreal
Tournament is a subsection of “Cleaner’s big
unofficial FAQ for Unreal Torunament”. For information about the game, the
author, download, and much more, please read that FAQ!
This is an unofficial FAQ. Nothing of what is written herein has been authorized by the makers of UT: Epic Games, Digital Extremes or GT Interactive Software.
I wrote the FAQ based upon my best knowledge, but like any human, I make errors. ;-) What is stated in this FAQ shall not be considered as fact, but only my very own personal opinion. If you feel, that I am wrong about anything written in this FAQ, please e-mail me to Cleaner.CH@gmx.ch and your input will be checked.
You alone are responsible for your computer system! If following any of the suggestions in this FAQ causes your UT or even OS to crash, I shall not be held liable for that. You are strongly recommended to back-up your UT and OS system files before doing any modifications as suggested in here.
Unreal and Unreal Tournament copyrights and trademark by Epic Games and GT Interactive Software. All rights reserved.
My credits for this guide go to the two sites, that tought me the basics of Unreal keybinding and aliases:
Ozh from the TheFrenchFragFactory.
Easy from EzUnreal.
You can also use the simple console command line by hitting the [Tab] key. Here you can only enter commands, but not read the system messages.
Bring up the console (see above) and type "preferences" (without the ") and the advanced options window will pop up. I’d recommend to switch UT to windowed mode before, so you can leave both windows permanently open and can see the effect of your changes instantly.
For users, who work with the AOs frequently, I recommend to bind a key to:
ENDFULLSCREEN | PREFERENCES
The official list of UT starting parameters, console commands and cheatcodes can be found on Epic's Unreal Tech Page:
unreal.epicgames.com/utconsole.htm
The page contains a few errors and the explanation of the commands is often very brief, but it is virtually the only list available. All other lists are just mirrors.
In the console, hit the cursor up key to repeat the last command. The same works with text messages using the SAY command ([T] key) or TEAMSAY ([R] key) command.
There are 5 ways to do that, depending a little on what you want to do. The result is the same: In any case, the resulting keybind is saved to the ..\UnrealTournament\System\User.ini.
This is the fastest way for the standard UT command repertoire. Choose the menu [Option]® [Preferences] ® [Control], look for the action you want to bind and enter your key directly
This is exclusively for voice messages and team orders. And it is especially important because the UT voice menu is complete sh*t. (Sorry Epic, I had to say it that hard.)
Choose the menu [Options]®[Preferences]®[Input]®[Speech Binder]. Bind your favorite messages to keys. (All of my num keypad – except numlock! – is binded to team messages.
Note that UT will automatically assign team messages to your team. E.g. “Somebody get our flag back!” can only be heard by your teammates.
Due to a bug, UT does not list all voice binds, if you defined more than 8. This does not mean, they are not working, they are just not shown in the speech binder! You can still use them and change them by way 3.
If the command you want to bind is not listed in the menus named in 1. or 2., you have to go the basic way:
Through the Advanced Options or by editing the ..\UnrealTournament\System\User.ini.
I personally prefer the AO, because I can keep UT running in the background and switch back and forth between UT and the AO and see the effect virtually instantly without restarting UT. (Each time you close the advanced options, UT activates the changes you made!) This is even easier, if you switch UT to windowed mode before you enter the AO. Furthermore in the advanced options the keys are sorted alphabetically; in the INI they are not.
Open the console and type:
Set input <key> <command>
For example to bind the left mouse button to fire:
Set input leftmouse fire
The key is binded permanently. You can check the result in the AOs or the user.ini.
So, open the AO
as described above and
expand the
[Advanced] ® [Raw Key Bindings] view.
Look for the key you want and put your command behind it.
Close the AOs. That’s all! =)
Open your ..\UnrealTournament\System\User.ini and look for the [Engine.Input] section. On top of that section, you find the aliases. Further down you find all the key-binds. Look for the key you want. Do not add a line for your key as this may mess up the keybind! It is already there somewhere, so just search. When you’ve found it, put in your command. Now save and close the file and restart UT.
Any console command (see above) can be binded to a key directly or via an alias. Furthermore there are the basic commands, that are not listed on Epic’s console command page. Look through your ..\UnrealTournament\System\defuser.ini for these simple commands.
Yes you can. Divide the commands with a “|”. So for example to jump and at the same time fire, the command would be:
Jump | Fire
If your command sequence does not work, you do not have to abandon hope. For a reason I don’t understand, many sequences, that do not work as a simple keybind, work fine, if you define them as an alias. So try that!
Yes, you can not only assign a command to the striking of a key, but also to the releasing of a key! So a common combination is to assign one command to pressing a key and an other to releasing a key. For example:
F1=ShowScores | onrelease ShowScores
This makes the Scoreboard come up when you hold down F1 and makes it disappear, when you release F1.
This can be useful in some cases. For example if you want to have several taunts, but only one key.
You have to define an alias (see next section) for each command, like this:
Aliases[x]=(Command=<command_1> | set input <key> <name_2>,Alias=<name_1>)
Aliases[x+1]=(Command=<command_2> | set input <key> <name3>,Alias=<name_2>)
…
Aliases[x+n-1]=(Command=<command_n-1> | set input <key> <name_n>,Alias=<name_n-1>)
Aliases[x+n]=(Command=<command_n> | set input <key> <name_1>,Alias=<name_n>)
<key>=<name_1>
Look below in the alias list, item 4, for a simple example.
Virtually any setting that can be changed through the menues and (even some that are in no menu) can be changed in-game through console commands. And as I said: Any console command can be bind to a key. Only some few changes need a re-connect or map-change to take effect.
The powerfull allround command is:
Set <class> <variable> <value>
Now all you have to do is find out the class and variable for the setting that you want to change. To do this, search through your user.ini and your unrealtournament.ini files. Find the line that is most likely the setting you want to change. Check how the paragraph is called that the line is in. The name is in [...] brackets on top.
For example if you want to change your mouse sensitivity, you'll find the following paragraph and line in the user.ini:
[Engine.PlayerPawn] <- This is the class.
...
MouseSensitivity=4.500000 <- This is the variable and value
So the command to change the mouse sensitivity through console to a value of 8 would be:
Set Engine.PlayerPawn MouseSensitivity 8
An alias is a pre-defined sequence of commands assigned to a name for faster execution. Aliases can be bind to keys as a single command or be used in other aliases.
UT’s aliases are not as powerful as those for other games, which is fine to me. Many people - incl. myself - consider too powerful aliases as cheating. Your skill in UT should be based on how well you can handle mouse and keys, not how good you can write scripts!
Just like advanced keybinds, you can do it two ways: Through the Advanced Options or through editing the ..\UnrealTournament\System\User.ini file. For the same reasons as explained above, I recommend using the AO. Even more here, as an alias will usually not work with the 1st attempt and the easy switching between UT and the AO w/o UT restart gives it a clear advantage.
So, open the AO as described above and expand the [Advanced] ® [Key Aliases] view.
Each alias consists of two lines:
The name line and the command line.
Put in your command sequence and give it a name. Done!
Aliases[0]=(Command="Button bFire | Fire",Alias=Fire)
Just add your alias to the bottom of the list by putting in your command sequence and giving it a name.
Aliases[<put number here>]=(Command="<put command here>",Alias=<put name here>)
Save and close the file.
You can now use the alias name as a command, just like any other command. =)
This is a list of aliases, that I found useful, so I have been using them or still use them:
MouseWheelUp=Getweapon PulseGun | getweapon
ut_biorifle | Getweapon UT_Flakcannon
This is just an example for weapon grouping.
What the keybind will do is switch to the last weapon of the row, that you have
and that you have ammo for. If your already hold that weapon the moment you
press the key, you switch to the next lower weapon. This way you can define a
weapon group (here: Short Range Weapons) with priority increasing to the end of
the group and cycle between the best two weapons of that
group.
You can use any weapon in these groups and as
many as you want. These are the correct names to be used:
Translocator, ImpactHammer, ChainSaw,
Enforcer, SuperShockRifle, DoubleEnforcer, PulseGun, SniperRifle, Ripper,
UT_Biorifle, Minigun2, UT_FlakCannon, ShockRifle, UT_Eightball,
WarheadLauncher
Aliases[#]=(Command="Axis
aBaseX Speed=-20.0 | Axis aStrafe
Speed=+300.0",Alias=CycleStrafeRight)
Aliases[#]=(Command="Axis aBaseX
Speed=20.0 | Axis aStrafe Speed=-300.0",Alias=CycleStrafeLeft)
<key>=CycleStrafeLeft
<key>=CycleStrafeRight
Beginners may find it useful to get some help with cyclestrafing. This alias will make you turn while sidestepping, so you do an automatic cyclestrafe. You can adjust the radius of the cyclestrafe by adjusting the aBaseX Speed. The higher the value, the more you turn.
<key>=ShowScores | onrelease ShowScores
Lets the Scoreboard show up only as long as you hold down the <key>.
<key>=setinstantrocket 0 | onrelease
setinstantrocket 1
Players using Instant rockets by default may
want to load multiple rockets from time to time. This keybind disables instant
rocket firing as long as you hold down the key. If you use instant rockets off
by default, just reverse the keybind for the opposite effect.
For a one-key-toggle, you would have to use
the command cycle technique described above:
Aliases[#]=(Command= setinstantrocket 0 | set input <key> IR_on,Alias=IR_off)
Aliases[#+1]=(Command= setinstantrocket 1 | set input <key> IR_off,Alias=IR_on)
<key>=IR_on
Aliases[#]=(Command=" getweapon translocator | onrelease altfire |
onrelease switchtobestweapon",Alias=translocate)
Beginners, who are not so trained with fast
wepon switching may find a keybind useful, that helps you with fast translocator
switching. This is the one, that I found most useful. You press the key, hold it
down, fire the TL where you want it (manually) and release the key to be
translocated. Afterwards you automatically switch to the best
weapon.
Aliases[#]=(Command="jump | fire",Alias=jumpfire)
<key>=getweapon impacthammer | onrelease jumpfire | onrelease switchtobestweapon
This lets you do a small hammerjump (hammer not fully loaded). Just press the key, hold it and point the hammer at the ground, then release the key. It is not as high as the real hammerjump, but it is easy to time and is high enough to do the most useful hammerjumps (to the sub in CTF-November, from the red flag in CTF-EternalCave, …)
To do a full height hammerjump, use:
Aliases[#]=(Command="onrelease jump",Alias=releasejump)
<key>=Fire | releasejump
It’s strange, but it doesn’t work to bind the onrelease jump directly to the key. You need the alias.
Aliases[#]=(Command="altfire | onrelease
fire",Alias=Combo)
<key>=Combo
This alias isn’t very useful IMHO, because it
doesn’t help you at all with those things, that make the combo difficult: Aiming
and Timing. But I list the alias by popular demand, just to show you, that it
works. ;)
Sorry, there is no alias for dodging.
Hundreds of people have tried to find it and AFAIK, nobody has managed to do
it.
<key>=menucmd 2
1
This brings up the player setup menu for
faster team switching.
For example:
<key>=speech 1 1 0 | teamsay Friendly
Fire hurts! | taunt wave
I like to combine voice messages, text
messages and gestures. The one above (just one example) sends the voice message
“Hey, same team!”, prints the text message “Friendly Fire hurts!” and makes me
wave.
<key>=iamtheone | god | loaded |
allammo
Sometimes, it is just necessary to cheat to
do some tests. ;)
<key>=behindview 1 | FOV 120 | onrelease behindview 0 | onrelease FOV 90
Did you know that in behindview mode, you can look around corners? This works even better with an increased “field of view” (fish-eye). This keybind switches to fisheye behindview while holding down the key.
If FOVs >90 are disabled by the server admin, this part of the alis is ignored, but the behindview still works.
It’s also handy to switch to 1st person view while spectating a teammate.
<key>=viewteam | behindview
0
Cycles through the views of your teammates in
1st person view. To switch back to your own view,
use:
<key>=ViewPlayerNum
0
<key>=getweapon sniperrifle | toggle
bDuck
While I snipe (which doesn’t happen very
often), I like to crouch, so I’m harder to see and and to hit and other snipers
can’t headshot me. This keybind gets the sniper rifle and goes to permanent
crouch. As soon as the normal crouch key is hit, everything is reset to
normal.
<key>=EndFullscreen | Preferences
I use the advanced options quite often, so I bind a key to it. Furthermore I like to switch to windowed mode, so I can test the result of the changes I made without switching back and forth.
<key>=Cancel |
disconnect
To deal with the UT bug, that some servers
keep sending your data packets after disconnect, bind a key to disconnect and
hit that key repeatedly to make sure, that the server got your
command.
<key>=mutate TossRelic
The well known command to drop a relic from Epic’s UT bonus pack.
These are just a few, that I found useful. There are a lot more.
Check the sites listed below in the links.
Provided that you did the above mentioned thing right, there are still several reasons why an alias may not work, although it consists of a sequence of commands, that work very well, when they are used single:
-
Epic disabled the combination of some
commands
As I understand, Epic made it impossible to use certain commands together in an alias to prevent aliases to become too powerful. This applies especially for most movement commands (forward/back/strafe) in combination with fire commands and onrelease.
Sometimes you can still get the command to work in an alias /keybind trying around with splitting it into several aliases /keybinds and then combine them.
-
Wrong key
Some keys seem to
have problems to be recognized correctly by UT. These are especially LeftShift /
RightShift and LeftCtrl / RightCtrl. But
there are some more. So if your alias doesn’t work with the keys you
want, try an other one before you give up.
-
Timing problems
Be aware, that a sequence of commands defined in an alias is executed virtually instantly at the same time. There is no way to delay the execution of a command. But some commands (for example switching a weapon) need some time to be executed. So if you put other commands behind a command, that needs time to be executed, these following commands may get lost.
-
Online problems
I had many
cases, where an alias worked perfect offline, but was not reliable online. Some
commands out of the sequence randomly got lost. I guess this has to do with the
same timing problems as mentioned above in combination with the lag and
packetloss of online gaming.
Sometimes strange effects happen with aliases, especially online:
If you get killed while holding down the key or parts of the command sequence get lost due to online lag, the alias key doesn’t do any more what it is supposed to do:
For example the above mentioned:
F1=ShowScores | onrelease ShowScores
If one of the two commands is lost, the command will be reversed: The scoreboard will be permanently visible and disappear while you hold down F1. The only way to get out of this in this case is to enter “ShowScores” into the console.
Equal problems happen with weapon switching aliases and set-input commands.
Often the only solution to get out of this is to disconnect and restart UT. Very annoying, when you have a good game. =(
An other solution is to bind a key, that resets your keybinds.
Epic’s Console
Page: http://unreal.epicgames.com/UTConsole.htm
FFF’s
Aliases:
http://frenchfragfactory.net/ressources/utconfig/utconfig.shtml
Easy’s U1
Aliases:
www.unreality.org/ezunreal/control.html
Easy’s UT
Aliases:
www.unreality.org/ezunreal/UTalias.html
Morningstar’s 7th seal : www.seventhseal.co.uk/utres.html
Riskable’s UT
tips:
http://riskable.youknowwhat.com/ut2.html