Setting Your LOX Binds
Posted: Sun Feb 05, 2006 11:24 pm
Welcome to LOX binds 101. Class is in session.
This will very briefly explain how to set up simple 1 command binds for quake 2 lox. Setting up multi-binds and aliases will be addressed another time.
I will not explain all the things you can bind here, that will come later. First you need to understand how to bind anything.
The first thing you need to do is make sure you have an autoexec.cfg text file in your lox folder. If you do not, please read this before you continue with this thread:
http://clandou.com/forum/viewtopic.php?t=1112
O.K., you have the file. You will also need to reference the config.cfg file so keep it handy.
It is recommended that you DO NOT bind anything to the 1 - 0 number keys since there are not enough keys on a keyboard for all lox weapons and commands. Therefore if you change one of the number keys, you will lose the ability to cycle through all the weapon choices for that number. Please note that the keypad numbers are not the same and you may bind to them.
With that in mind, say you love the railgunsweeper but it is a hassle to get to use the weapon because after you get the chaingun, you have to hit the number 5 key 10 times before you cycle to that choice. While you are trying to do it, {DOU}Tommy lobs a plasma cluster grenade into your pie-hole. Here is what you would do.
First choose a key on your keyboard that you want for that weapon. This is where the config.cfg comes in handy. Open that up and make sure that you are not choosing a key that is important for something else. For example, you will most likely not want to ever choose the letter g since you will need to use that to cycle through the grenade types (there are quite a few). If you are uncertain what a key that was set in the config.cfg does and are paranoid about choosing that key, just ask here in the forum and I will explain it to you.
O.K., for this example, we will say you chose the letter x for your railgunsweeper. Open up your autoexec.cfg (in your lox folder) and add a new line that reads:
bind x "use railgunsweeper"
It is that simple.
When making binds, be careful of how you spell out a weapon. railgunsweeper is not the same thing as railgun sweeper. The 2nd will not work. The best way to determine this is to simply cycle to the weapon you want while on the server. The screen will display the name of the weapons as you cycle through. Just bind to the name exactly as it is displayed.
Now here is where it gets tricky. For all weapons you will use the word "use" in the bind. It will be inside the quotes. However, not all things you will bind will contain the word use. For example if you wanted to bind the letter r to the angel of life (angelol) you would type:
bind r "angelol"
I will very soon make a post with all of the different weapons and commands to make it easier for you.
When I post all of the weapons and options I will give firther examples. Hopefully for now this will get you to at least explore and experiment with binds a bit. And don't worry if you scre up your binds. You can edit the autoexec.cfg anytime or scrap it and start a new one.
Tommy
This will very briefly explain how to set up simple 1 command binds for quake 2 lox. Setting up multi-binds and aliases will be addressed another time.
I will not explain all the things you can bind here, that will come later. First you need to understand how to bind anything.
The first thing you need to do is make sure you have an autoexec.cfg text file in your lox folder. If you do not, please read this before you continue with this thread:
http://clandou.com/forum/viewtopic.php?t=1112
O.K., you have the file. You will also need to reference the config.cfg file so keep it handy.
It is recommended that you DO NOT bind anything to the 1 - 0 number keys since there are not enough keys on a keyboard for all lox weapons and commands. Therefore if you change one of the number keys, you will lose the ability to cycle through all the weapon choices for that number. Please note that the keypad numbers are not the same and you may bind to them.
With that in mind, say you love the railgunsweeper but it is a hassle to get to use the weapon because after you get the chaingun, you have to hit the number 5 key 10 times before you cycle to that choice. While you are trying to do it, {DOU}Tommy lobs a plasma cluster grenade into your pie-hole. Here is what you would do.
First choose a key on your keyboard that you want for that weapon. This is where the config.cfg comes in handy. Open that up and make sure that you are not choosing a key that is important for something else. For example, you will most likely not want to ever choose the letter g since you will need to use that to cycle through the grenade types (there are quite a few). If you are uncertain what a key that was set in the config.cfg does and are paranoid about choosing that key, just ask here in the forum and I will explain it to you.
O.K., for this example, we will say you chose the letter x for your railgunsweeper. Open up your autoexec.cfg (in your lox folder) and add a new line that reads:
bind x "use railgunsweeper"
It is that simple.
When making binds, be careful of how you spell out a weapon. railgunsweeper is not the same thing as railgun sweeper. The 2nd will not work. The best way to determine this is to simply cycle to the weapon you want while on the server. The screen will display the name of the weapons as you cycle through. Just bind to the name exactly as it is displayed.
Now here is where it gets tricky. For all weapons you will use the word "use" in the bind. It will be inside the quotes. However, not all things you will bind will contain the word use. For example if you wanted to bind the letter r to the angel of life (angelol) you would type:
bind r "angelol"
I will very soon make a post with all of the different weapons and commands to make it easier for you.
When I post all of the weapons and options I will give firther examples. Hopefully for now this will get you to at least explore and experiment with binds a bit. And don't worry if you scre up your binds. You can edit the autoexec.cfg anytime or scrap it and start a new one.
Tommy