Quick Guide to Binds & Macros

Here's a little guide I'm writing on Binds and Macros. Enjoy!

I. What is a bind?

A bind is a in-game action that is tied to a key, for example, I can tie Fly to F or something. It is really as simple as that.

II. What is a macro?

A macro is a grey circle on your tray with a word on it. Like a bind, it's tied to something. For example, I could create a macro called 'Fly' and it would appear as a spot on my power tray, and when I click it I could activate Fly.

III. How to make a Bind

Making binds is pretty simple. I have to type /bind then a letter and then I can do a number of commands. I've compiled a list of these and what code that needs to be used. Please contact me if there's any missing:

Chat message: say [message]
Chat message on specific channel: say $$[channel] [message]
Power activation by name: powerexc_name [power name]
Power activation by slot: powerexc_slot [slot]
Emote: em [emote]
Character information:

Remember, character information binds must start with beginchat. For example /bind z beginchat $name $level

$name
$level
$archetype
$origin
$target

White Box When Typing: startchat $$AFK [message] (remember -this can only be binded to a key, not done automatically when typed!)

You can also mix these binds together. For example:

/bind s em dance say Let's dance!

IV. Example Binds

Here are some example binds. They are the binds shown and then what they will do.

/bind z beginchat [$name $level]

/bind startchat $$AFK Typing

/bind F1 say It's woopin' time!


V. How to make a Macro

Macros work very much like binds. Here's a quick example:

/macro level say Congratulations on your new level $target!

Now the a grey circle will appear on my tray called "level". When I click it, my toon will say "Congratulations on your new level [his/her target]!"

So, as you can see, you can use all the actions you could use in binds in macros. In fact, macros are nearly the same as binds - just that they're a big grey circle on your power tray. And before I forget, here's the macro stripped down to its beginnings:

/macro [macro name]

Now just add any action as normal and you're off!

VI. Example Macros

Works the same as Example Binds.

/macro squid say SQUID FORM! powerexc_name Bright Nova

/macro box em boombox say Can you feel the music?

Thanks for reading this quick guide on binds and macros. I hope it informed you of what binds and macros are and what you can do with them. Good luck, and have fun using binds and macros!

NOTE: Criticism is fine. Actually, I want it! If I'm wrong on a bit, correct me, and I'll fix it!

You seem to be missing command deliminators in a lot of the chain binds.

EG :
/macro squid say SQUID FORM! powerexc_name Bright Nova

should be :
/macro squid say "SQUID FORM!"$$powerexc_name Bright Nova

or similiar.

[ QUOTE ]
You seem to be missing command deliminators in a lot of the chain binds.

EG :
/macro squid say SQUID FORM! powerexc_name Bright Nova

should be :
/macro squid say "SQUID FORM!"$$powerexc_name Bright Nova

or similiar.

[/ QUOTE ]
I've never seen powerexc_name used before - I'd go for:

/macro squid say "SQUID FORM!"$$powerexec_name Bright Nova"

...with a closing quote too.

[ QUOTE ]
[ QUOTE ]
You seem to be missing command deliminators in a lot of the chain binds.

EG :
/macro squid say SQUID FORM! powerexc_name Bright Nova

should be :
/macro squid say "SQUID FORM!"$$powerexc_name Bright Nova

or similiar.

[/ QUOTE ]
I've never seen powerexc_name used before - I'd go for:

/macro squid say "SQUID FORM!"$$powerexec_name Bright Nova"

...with a closing quote too.

[/ QUOTE ]

Bah. Damn you standoff, you win this round

(although you've got an extra quote in there somewhere so lets call it a score draw )

/macro squid say "SQUID FORM!"$$powerexec_name "Bright Nova"

?

[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
You seem to be missing command deliminators in a lot of the chain binds.

EG :
/macro squid say SQUID FORM! powerexc_name Bright Nova

should be :
/macro squid say "SQUID FORM!"$$powerexc_name Bright Nova

or similiar.

[/ QUOTE ]
I've never seen powerexc_name used before - I'd go for:

/macro squid say "SQUID FORM!"$$powerexec_name Bright Nova"

...with a closing quote too.

[/ QUOTE ]

Bah. Damn you standoff, you win this round

(although you've got an extra quote in there somewhere so lets call it a score draw )

/macro squid say "SQUID FORM!"$$powerexec_name "Bright Nova"

?

[/ QUOTE ]
You're right - but I'll try to pull ahead with a bit of further quote fiddling:

/macro squid "say SQUID FORM!$$powerexec_name Bright Nova"

...so, a pair of quotes surrounding the entire "active" part of the bind, but no other quotes anywhere at all. Your turn!

Erm....

Hey, look over there. Summer Glau in a bikini looking for someone to put suntan lotion on her back.

*runs*

(yep, that last one looks right to me. I lose on penalties*)

(*Not often I get to use football metaphors. Next I'll be citing the offside rule at you, if I knew what it was)

Hey, it is Summer too - cheers Carni!

/em scampers off

/em comes back with dopey grin

Actually, a few more things regarding the OP (this could invoke the offside rule for all I know...)

* You don't need to use beginchat when including character information:

/bind h "say Hi $target, how's things?"

...is entirely acceptable.

If present the beginchat would copy the rest of the bind into the chat box, ready for final manual editing and/or the pressing of the return key to set if off.

* To speak to a specific channel, use chan_send "[channel]", not say $$[channel]. For example:

/bind h "chan_send "Union Overlords" Hey, $name is back!"

More realistically:

/bind h "beginchat /chan_send "Union Overlords" "

...to enter chat mode with the prefix to talk to a specific channel pre-entered.

[ QUOTE ]
* You don't need to use beginchat when including character information:

/bind h "say Hi $target, how's things?"

[/ QUOTE ]

Except that bind doesn't have a thing to do with character information on channels.

[ QUOTE ]
[ QUOTE ]
* You don't need to use beginchat when including character information:

/bind h "say Hi $target, how's things?"

[/ QUOTE ]

Except that bind doesn't have a thing to do with character information on channels.

[/ QUOTE ]
Never said it did; it was a response to where you said:

[ QUOTE ]
Remember, character information binds must start with beginchat. For example /bind z beginchat $name $level

[/ QUOTE ]
...which also doesn't mention channels.

[ QUOTE ]
NOTE: Criticism is fine. Actually, I want it! If I'm wrong on a bit, correct me, and I'll fix it!

[/ QUOTE ]
Or not.

As the edit period has presumably lapsed, it might be best to post a suitably updated version of the original as a new thread, then ask GR to delete this one entirely.

If you want a bit of proofreading for any repost you're welcome to PM me.

Er..

Isn't it powexec_name?

[ QUOTE ]
Er..

Isn't it powexec_name?

[/ QUOTE ]
You're a week behind Standoff

(but yes it is)

Ok a useful enough starting point but the testosterone level's gone up a bit. I've gotten a bit confused about the function of the " within a bind and macro - what do they do and where should they go?

And never mind the off side rule, if you know the LBW law THEN you... Oh, wait... I know the LBW law

"You got to dig it to dig it, you dig?"
Thelonious Monk

I was kind of replying to both you and Standoff. Should really have quoted both and explained myself better.

It should be:

powexec_name

not powerexec_name as Standoff mentioned.

Edit:

Scarlet, I'm not all that up on where the quotation marks go, I usually take a few trial and error attempts it until it works.

bind keyboard-key(inc LShift+key) "<quotes due to spaces in power name/slot toggles etc.>"

macro macro-name("<if it has spaces in it>") "<quotes due to spaces in power name/slot toggles etc.>"

powexec_name
powexec_toggle_on
powexec_toggle_off
powexec_auto

Hint: Because of the " " between 'powexec_name' and the power you activate you need the "" to read that as a single command otherwise the game would stop reading that command after the second space.

/<command signal>
bind/macro<command type to create>
<space before>
key/macro-name<obvious>
"<space before command section marked by a ">
commands to issue$$<$$ to combine commands into a string>
remaining commands including needed spaces"<command section terminated with a ">

/bind F10 "$battlecry$$em roar"
(Notice the space between 'em' and 'roar'...)

/bind F10 "local Ok $target, $battlecry"
(Notice the text there had three spaces in the "", oh and that 'local' <space> told it which chat type to use.)

Examples from the above bind in local chat:
[ QUOTE ]
Ok Deathhead Gunner, You're doooooooooomed!

[/ QUOTE ]
[ QUOTE ]
Ok Ripper,

[/ QUOTE ]

Nuff said...

What would the bind be that would trigger a) Lightning field b) Flight then c) the spacebar?

[ QUOTE ]
I was kind of replying to both you and Standoff. Should really have quoted both and explained myself better.

It should be:

powexec_name

not powerexec_name as Standoff mentioned.

Edit:

Scarlet, I'm not all that up on where the quotation marks go, I usually take a few trial and error attempts it until it works.

[/ QUOTE ]
You're 100% right Biscuits...

Damn, that means I surrendered for no reason.

/em Kirk : STAAAAAAAAAAAAAAAAAAAANDOFF

Hmmmm, wazzzat?

Ooooh, yes, Biscuits is exactly right; I was so busy looking at one error that I added another all of my own making.

Erm, it must be Vista's fault.

/em Rapid withdrawal

is there a guide or list anywhere that shows macro's and their uses, with a breakdown of what each part of the macro does...? love to start using them.

[ QUOTE ]
is there a guide or list anywhere that shows macro's and their uses, with a breakdown of what each part of the macro does...? love to start using them.

[/ QUOTE ]
Try looking through some of these (in second part of the post):
http://boards.cityofheroes.com/showt...age=0&vc=1

How would you bind a key to change to the 5th costume slot?? the keybind option in options only goes to 4.

The command to change cossies is cc, so as your primary slot is designated as 0, changing to the 5th slot should be

/bind x "cc 4"

You can do it manually in the chat line; type in (including quotes):

/bind k "cc 4"

...then hit RETURN, to make the "k" key switch to the 5th slot[1]; replace the "k" with the number or letter you want to use, of course!

[1] The slots are numbered 0-4 in binds - it's a dev thang.

Edit: Fixed typo

uuh.. thanks alot saved me e bunch of time..

btw small update, it appears the commands for

<border #00000000>
<bg #00000000>

have changed to

<bordercolor #00000000>
<bgcolor #00000000>

for text binds, which is why mine were screwing up in I12, so if your chat binds look wrong, check to see if its these command changes that are doing it!