Help with a keybind


Blue_Crow

 

Posted

I tried to search for this but couldn't find it... sooooo, is there a way to get 3 actions from 1 keybind?

For example, being a buff-bot is kind of a pain in the backside at times, so I was hoping to ease my frustrations with something like this:

/bind F1 "team_select 1$$powexec_name Speed Boost$$powexec_name Increase Density"

Will that work or am I forever doomed to executing one power at a time? Any help with this would be absolutely fantastic.


 

Posted

Binds are limited to one power activation per bind. So, unfortunately, that bind will only fire off Increase Density.


 

Posted

Sorry, MrVacant.
The design of the game included prohibiting the making of bots. So the Devs decided that when it comes to binding and macros, you cannot activate two powers in one single keystroke or mouse click.


"The one thing that can stop a full team of MasterMinds dead in its tracks... a doorway!" --Frogfather

 

Posted

Quote:
Originally Posted by NeoSporin View Post
Sorry, MrVacant.
The design of the game included prohibiting the making of bots. So the Devs decided that when it comes to binding and macros, you cannot activate two powers in one single keystroke or mouse click.
THIS.

But what you can do, is set Speed Boost on auto, then use your ID binds to cycle through the team/pets, then take it off auto again.


 

Posted

There are a few ways around this limitation, however. Some binds can activate toggle powers and still do execute a click-type power. Or . . .

(There are third-party products that allow you to program macros that will execute numerous commands. This mostly include game-type controllers and keyboards.)


LOCAL MAN! The most famous hero of all. There are more newspaper stories about me than anyone else. "Local Man wins Medal of Honor." "Local Man opens Animal Shelter." "Local Man Charged with..." (Um, forget about that one.)
Guide Links: Earth/Rad Guide, Illusion/Rad Guide, Electric Control

 

Posted

Try this:

Create a binds folder on your computer (here I use C:\CoH_binds).

Create two text files and save them to your binds folder,

SB.txt, containing only the following line:
F1 "team_select1$$powexec_name Speed Boost$$bind_load_file C:\CoH_binds\ID.txt"

ID.txt, containing only the following line:
F1 "team_select1$$powexec_name Increase Density$$bind_load_file C:\CoH_binds\SB.txt"

In game, load the bind (just once for any character you want to use the binds on) by typing:
/bind_load_file C:\CoH_binds\SB.txt

SB.txt will take care of loading the other bind as soon as you press F1.

Now, the buff cast will alternate with each press of F1. Tap the key twice and you're alll set. A must have for bubblers, too.


Arc 55669 - Tales of the PPD: One Hell of a Deal (video trailer)
Arc 64511 - The Wrecking Ball
Arc 1745 - The Trouble With Trimbles
Arc 302901 - HappyCorpse

 

Posted

Quote:
Originally Posted by Xyzyx View Post
SB.txt, containing only the following line:
F1 "team_select1$$powexec_name Speed Boost$$bind_load_file C:\CoH_binds\ID.txt"

ID.txt, containing only the following line:
F1 "team_select1$$powexec_name Increase Density$$bind_load_file C:\CoH_binds\SB.txt"

In game, load the bind (just once for any character you want to use the binds on) by typing:
/bind_load_file C:\CoH_binds\SB.txt

SB.txt will take care of loading the other bind as soon as you press F1.

Now, the buff cast will alternate with each press of F1. Tap the key twice and you're alll set. A must have for bubblers, too.
Only problem I see with this is that it only targets teammate #1 and won't cycle:

SB.txt, containing only the following line:
F1 "powexec_Auto Speed Boost$$bind_load_file C:\CoH_binds\ID.txt"

ID.txt, containing only the following line:
F1 "powexecauto Speed boost$$bind_load_file C:\CoH_binds\SB.txt"
F2 "targetcustomnext teammate$$powexec_name Increase Density"

should place SB on auto on pressing F1 and load the ID.txt file, pressing F2 will target the first teammate and then should SB then ID or ID then SB, repeat F2 and it should cycle the team buffing ID and SB as you go, then F1 again should turn SB off auto and reset F1 to activate auto on SB and load ID.txt again.
Now I have not tested this, so it may not work as stated. But that should not stop you from testing it

An alternate method is the NUMPAD keys or a combination of both.

NUMPAD only:
/bind NUMPAD1 "targetcustomnext teammate"
/bind NUMPAD<number> "powexecname Speed Boost"
/bind NUMPAD<number> "powexecname Increased Density"

NUMPAD and bindloadfile:
File SB.txt:
NUMPAD2 "powexecname Speed Boost$$bindloadfile C:\CoH_binds\ID.txt"

File ID.txt:
NUMPAD2 "powexecname Increased Density$$bindloadfile C:\CoH_binds\SB.txt"

After you have made the two files SB.txt and ID.txt in your game folder (in this case C:\CoH_binds\), start the game and load the toon you want this on and type:

/bindloadfile C:\CoH_binds\SB.txt"

this will set the wheels in motion as stated by Xyzyx.

then

/bind NUMPAD1 "targetcustomnext teammate"

then each time you press NUMPAD2 it will activate either SB or ID (whichever cycle it is on) and then load the file to set the other power to NUMPAD2. NUMPAD1 will let you cycle your teammates as before.


Cat: "Better to live 5 secs as a tiger then a lifetime as a worm"
Rimmer: "Arrh but who ever heard of a worm skin rug"

"Anyway I attack Nemesis" - Blue Crow
"What alone?" - Toon
"No No, I had my katana with me."

Fav. Book: The Atheist belief system

 

Posted

He didn't ask for it to cycle. I'm assuming he's using a different key for each teammate; personally I use the number pad, but he may be using (for example) F1 through F8.

As far as setting a power on autofire, I find that a) it's unreliable and b) it means I can't have a power on autofire for my own use, so I prefer the double-tap method I outlined.


Arc 55669 - Tales of the PPD: One Hell of a Deal (video trailer)
Arc 64511 - The Wrecking Ball
Arc 1745 - The Trouble With Trimbles
Arc 302901 - HappyCorpse

 

Posted

True about the cycling, I got that wrong, not saying that you were wrong. I just like to minimise the number of keys used and txt files created to accomplish a goal.

Thats why I suggested the combination of NUMPAD and bindload. LOL and I just thought that you can use the same for the F1 and F2 keys thus freeing up F3 to F8 for other binds.

File SB.txt:
F2 "powexecname Speed Boost$$bindloadfile C:\CoH_binds\ID.txt"

File ID.txt:
F2 "powexecname Increased Density$$bindloadfile C:\CoH_binds\SB.txt"

/bindloadfile C:\CoH_binds\SB.txt
/bind F1 "targetcustomnext teammate"

Tap F1, double tap F2. Repeat.

Not helpful to select a team member directly but you can click them with the mouse and double tap F2 in a fight.


Cat: "Better to live 5 secs as a tiger then a lifetime as a worm"
Rimmer: "Arrh but who ever heard of a worm skin rug"

"Anyway I attack Nemesis" - Blue Crow
"What alone?" - Toon
"No No, I had my katana with me."

Fav. Book: The Atheist belief system

 

Posted

Never used this myself but saw it in the big 'We hate SB thread...'

/bind alt+lbutton "powexec_name speed boost"

Which means when you hold alt down and (double?) click on a team mates name in the team list you will cast SB (not sure about the double click as I say not done this myself). To slove the OP's question I'd add:

/bind alt+rbutton "powexec_name increase density"

You could also do this through a popmenu, but I think that might be a little over the top unless you desperately need to know...


 

Posted

I've tried incorporating the teamselect into my binds, but have not been able to get it to work the way I want (cycle through team list). I even tried it in a rotating bind (one key cycles through the team list), but it always got hung up at whatever point in the list I was at.... since I couldn't target myself, the command couldn't complete and move on to the next.

Sooooo.... currently I am using the default team select (shift + number) plus these nifty binds...

I do have some powers set to fire on a downpress/release. One power fires on the downpress, the other on the release. The trick is to use the "+" in combination with the "toggleon" command. It can force a click power to behave like a toggle power within the command string. Here are some examples:

"+ $$powexec_toggleon Aim$$powexec_toggleon Build Up"
"+ $$powexec_toggleon Nova$$powexec_toggleon Conserve Power"
"+ $$powexec_toggleon Increase Density$$powexec_toggleon Speed Boost"

The last power in the string will fire first on the downpress. Then, since they are being labled as "toggles" the next power will fire on the release.

For doing this with powers that ARE toggles (not clicks), you may need to work the toggleoff command into the string.
"+ $$powexec_toggleoff spring$$powexec_toggleoff combat jumping$$powexec_toggleon spring$$powexec_toggleon combat jumping"

IOW, to make the first down/up turn stuff on, and the second down/up turn stuff off. I understand several folks with Keld builds do this for switching between forms, though I don't know if I have the right of it.

NOTE: It is necessary to use a "paused press" technique with these binds. Else, if the release is too quick, it will just que up the last power again.

Here is some info I came across while looking into this sometime back:
Quote:

Quote:
*** A note about the "+" and "++" prefixes in some of these commands ***

The short explanation of the + and ++ prefixes is that they represent how persistently the command will be carried out. Most of these keybindings represent "press and fire" commands -- that is, you press down on the button and the action will be performed once, until the button is pressed again.

With a "+" prefix the command will be carried out for as long as the button is pressed down, and ceases as soon as the button is no longer being pressed. For example, the default binding for the w key is +forward. For as long as the w key is pressed down your character will continue moving forward... but as soon as the button is no longer being pressed, the character stops moving.

With a "++" prefix the command will be toggled "on" and will continue to be activated until the button is pressed again, toggling it "off." If the w key were bound to ++forward, pressing the w key once would cause the character to move forward, and that character would continue to move forward until the w key were pressed again.

Any command that has a + prefix can work with a ++ prefix, and vice versa. This can lead to some redundant commands. For example, ++forward works exactly the same as ++autorun -- you run until you turn the command off.




Through trial and error, I've formed the following theory on how the "+" modifier works in binding.

The "+" modifier has two behaviors.
Behavior one: at all times when "+" is prepended to a command, it is the same as doing "command 1". Obviously this only works correctly on commands that take 1 or 0 as input. When other commands are prepended with it, it adds the 1 to the end of the arguments, and gives an error. This behavior is mirrored by the "-" modifier, which yields argument 0.

Behavior two: ( Only when directly in the bind.. in other words this does not work when made a macro which you then bind to a key! )when prepended to the first command in a bind (assuming that command is one that works with it, ie takes 1/0 argument), it gives the entire bind statement a "press/unpress" behavior. This means two things:

* a) the command prepended with the "+" turns on (aka is given argument 1) when you press the key as you would expect per behavior 1. Additionally it turns off (argument 0) when you unpress the key
* b) the rest of the commands in the bind are performed once when you press the key, and again when you unpress it

Note that this behavior is not mirrored by the "-" modifier.. it might be nice if it did at least the first part, ie turn a command off when you press the key and back on when you unpress, but it doesn't.

Side note: I am actually a bit surprised that they decided to overload the use of the "+" in this way. It seems to me it would have been more intuitive and useful to have another character modifier (> for instance) to prepend to a bind statement (without a necessary command after it) to extend the second behavior, with the addition that any commands following in the statement with a "+" would work in the on/off manner when press/unpressed instead of just the first one.

The secondary behavior of the "+" in binds makes several useful things possible. Especially when you realize that the first command doesn't always have to do something, since you can always override it with a "-" form of it elsewhere in the bind. For instance a simple yet very useful bind for fly which makes you fly only while you hold down "f":

* /bind f "+up$$-up$$powexec_name Fly"



Another behavior can be achieved by exploiting the "overwrite" effect of powers (aka if several powers are entered one after the other in a bind, only the last one will go off in most cases). A very useful binding for getting out of melee range quickly with hover is:

* /bind v "+up$$powexec_name Hover$$powexec_name Hover"


This makes you jump and then hover up in the air just out of melee range. Note the doubling up of the hover power.. this is because if you only have it once in the bind, it will turn hover on when you press it and off when you let go (usually.. sometimes the hover from press and hover from unpress go through together and one gets overwritten, but this is rare). Why doesn't it turn on/off quickly when you press it and on/off quickly when you let go if you enter it twice? Because of the power overwrite effect.. while it is busy doing the jump when you press the button down, both hovers go through and the second overwrites the first, resulting in hover being turned on. When you let go, it stops the jump and both hovers go through, turning hover off and back on very quickly (before you drop) resulting in you being left in hover mode. This causes a bit of spam to your combat messages window, but it's worth it. Note: the differing behavior here (ie overwrite happening on press but not on unpress) I believe is due to the interaction between commands and powers on timing in a bind, but this is just a guess.


Quote:
Don�t say things.
What you are stands over you the while, and thunders so that I cannot hear what you say to the contrary. - R.W. Emerson
The BIG consolidated LIST for BASE LUV
YUMMY Low-Hanging Fruit for BASE LUV

 

Posted

Quote:
Originally Posted by Xyzyx View Post
He didn't ask for it to cycle. I'm assuming he's using a different key for each teammate; personally I use the number pad, but he may be using (for example) F1 through F8.
Yep, that's exactly what I wanted to do... so you get a cookie!

All of the replies so far have been very helpful and I now have a few things to experiment with, so a big thanks to everyone for the assist. But, please continue to discuss the issue, since I'm sure that there are many more ways to skin this particular cat and all support toons could benefit from the information. *2 thumbs up*