Stupid bind question


Callista

 

Posted

Erm, does it work if you write it fulcrum_shift? I'd say /bind f "powexec_name fulcrum shift" but I never tried it your way. Never had Fulcrum Shift yet, though, so I don't know if it's a power specific problem.


 

Posted

yeah, I guess your problem is the _. You don't normally need them in binds.


 

Posted

Well, /bind b "powexec_name speed_boost" works just fine.

Putting a space in the power name would imply 2 arguments, but powexec_name only takes one.


Omnes relinquite spes, o vos intrantes

My Characters
CoX Chatlog Parser
Last.fm Feed

 

Posted

Hmm, must be something else then. I did think it would have been a bit too obvious

It definitely works with the space too, though. I find the syntax used in binds a bit muddy sometimes


 

Posted

[ QUOTE ]
Well, /bind b "powexec_name speed_boost" works just fine.

Putting a space in the power name would imply 2 arguments, but powexec_name only takes one.

[/ QUOTE ]
The command language is batty. Some commands, like powexec_name can take a sequence of words as args and will always treat it as one.
The underscore working is interesting. My guess is the power is known by two names internally.

Don't for one moment think this language is designed properly

macro_slot is completely broken for example. It won't parse unless typed on the command line, and then it puts your macro in the wrong slot!

Dammit - that command would have been *so* *useful*!!


[i]If they get there first they'll make our dreams come true.
If we get there first we can stop them.[/i]

 

Posted

[ QUOTE ]
Why doesn't: /bind f "powexec_name fulcrum_shift" work?

[/ QUOTE ]

It will be the _ character /bind x "powexec_name Bright Nova" works fine for me ... obvously not fulcrum shift but same idea, I thing it takes whatever is after Powexec_name as one argument no matter how many words are used until it gets to the $$ sign.


 

Posted

Bind seems to have very loose syntax so that it can interpret the same command in several different ways.

For example, I have a bind "/bind lshift+lbutton "powexec_name teleport" and it works in practice but gives an error whenever I hit lshift by itself, because then it interprets lbutton as the start of actual command . It annoys me but I haven't figured out if there's a completely correct way to put it.


 

Posted

Wouldn't /bind key powexec_name "fulcrum shift", or just /bind key powexec_name fulcrum shift work?


 

Posted

Try /bind f " $$powexec_name Fulcrum Shift". Might work but im not sure


@Scorpio EU

 

Posted

/bind key "powexec_name fulcrum shift"

there.


[CENTER]Euro side: [B]@Orion Star[/B] & [B]@Orions Star[/B][/CENTER]

 

Posted

Orion has the cookie, the quoations make the bind recognise the entire string as one argument.

As said, CoH language is weird.


 

Posted

[ QUOTE ]
Well, /bind b "powexec_name speed_boost" works just fine.

Putting a space in the power name would imply 2 arguments, but powexec_name only takes one.

[/ QUOTE ]

As long as you use "":s the number of arguments doesnt seem to be an issue. Game will consider everything after powexec_name and before " or $$ part of that name. When chaining multiple commands just use $$.

Im 100% sure the correct form is /bind key "powexec_name fulcrum shift". Forget using _ in names, but always use "".

.. I have had practise with multiple arguments with Mastermind binds Like /bind key "petcom_name bob follow aggressive". Im not sure what would happen if the pet has a 2 part name though, have to test.


 

Posted

As far as I can tell, the game ignores all _'s you put in your bind: powexecname and powexec_name both work, similarly with bind_load_file and bindloadfile. I'm pretty sure that p_o_w_e_x_e_c_n_a_m_e would also work I guess that's why Fulcrum_Shift doesn't work.


IN MEMORIUM OF GAYBABY
CRUELY TAKEN FROM THIS WORLD WHILE SO YOUNG

 

Posted

/bind b "powexec_name speed_boost" :: DONT use
/bind b "powexec_name speed boost" :: DO use

/bind b "powexec_name fulcrum_shift :: DONT use
/bind b "powexec_name fulcrum shift :: DO use

The power arguments confuse CoX.

all power names shud be as they are displayed in game:

Dawn Strike
Bright Nova
Fulcrum Shift
Healing Aura
etc
etc

No need for the "NAME_NAME" part.. just stick to the "NAME NAME".. life becomes easier and everything works XD