-
Posts
2 -
Joined
-
[ QUOTE ]
Does powexec_toggleon Sprint have to come after +forward?
If that's the case, would this combination work for running then?
UP "+forward$$powexec_toggleon Sprint"
DOWN "+backward$$powexec_toggleoff Sprint"
[/ QUOTE ]
Exactly. The "+" at the beginning is what gives the "forward" and "backward" commands the "turn on when pressing down, turn off when releasing the key" functionality. The "+" has to be the first thing in the bind. You can only use the "+" with certain commands (primarily movement.) Basically, it makes the bind execute once when you press down on the key, then again when you release the key.
"Forward" and "backward" act as toggles - toggled on when you press down, then toggled off when the bind is executed a second time as you release the key. When you do not have the "+" at the beginning of the bind, the entire bind is executed only once - when you press down on the key. "+" also forces the first execution to be "toggleon" - i.e. "+forward" always toggles "forward" on when the key is pressed. If it is at the beginning of the bind, then it also toggles "forward" off when the key is released, otherwise, "forward" just stays on.
[ QUOTE ]
Whould this work for bailing out of trouble?
V "local I'm out of here!$$++up$$++forward$$powexec_toggleon Super Jump"
[/ QUOTE ]
Almost. You want:
V "++up$$++forward$$powexec_toggleon Super Jump$$local I'm out of here!$$"
You may also have to swap the "up" and "forward". It shouldn't make any difference, but I use "++autorun$$++up$$powexec_toggleon Super Jump". You will also need to cancel both the "foward" and the "up" movement by hitting keys bound to "+forward" and "+up" seperately. Just tapping your "forward" key will stop forward movement, but leave you hopping in place.
There are a few other tricks to that - but I'm going to be late for work... -
[ QUOTE ]
[ QUOTE ]
The toggleon/toggleoff is better then I expected!
Not only will it allow you to make one key for all your toggle activations, but you can make a true "toggle" key! Try this one out:
/bind w "+forward$$powexec_toggleon Sprint$$powexec_toggleoff Sprint"
this will result in you running forward with Sprinit turning on... when you release the key, sprint turns off!
Jumpers and superspeeders now have an equivilant to
"+forward$$powexec_name Fly$$powexec_name Hover"
[/ QUOTE ]
This may work, but you might have a problem if you hit 2 movement keys at the same time (1st hit will turn you on, the 2nd off & the release back on again) - Try out Gnarly's Speed on Demand Binds for that functionality: http://www.jim.cavanaugh.net/sod.htm
[/ QUOTE ]
True... but if you only add the toggle to your forward movement key, or maybe your forward key and your back key (which you are much less likely to hit at the same time) all you would loose is the ability of strafe quickly. And you could still hit forward + right or forward + left and keep sprinting.
I'm definately going to try out some variation of this on my flyer and my jumper. Gnarly & co. did some great work with the Speed on Demand binds, but I still found them too prone to 'breaking', and getting the toggles reversed.