Quick Guide To Binds & Macros Version 1.1

Checking the old thread it reminded me that I had a few problems with the old one. Here's the new one with incorrections fixed.

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: chan_send "[channel]" [message]
Power activation by name: powerexc_name [power name]
Power activation by slot: powerexc_slot [slot]
Emote: em [emote]
Character information:

Command matches the action. For example, $name would show your character name.

$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 enter "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!$$powexec_name Bright Nova"


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

Following from version 1.0, Coolio_Wolfus posted this very excellent mini add-on:

[ QUOTE ]
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...

[/ QUOTE ]

I think that's about it...right?

---

[ QUOTE ]
I think that's about it...right?

[/ QUOTE ]
Not quite - the typo on the command pow_exec is still in there. Quick, before the editing window closes!

---

[ QUOTE ]
[ QUOTE ]
I think that's about it...right?

[/ QUOTE ]
Not quite - the typo on the command pow_exec is still in there. Quick, before the editing window closes!

[/ QUOTE ]

[ QUOTE ]
powexec_name

[/ QUOTE ]

This?

---

Yes - IIRC the system ignores the "_", and will look for a match at the start of the command when trying to process things, so either of our options will do. I have to agree that powexec_name makes the meaning of things clearer though, so I'd go with that.

---

Ah, so I'm in the clear...

---

[ QUOTE ]
/bind startchat $$AFK Typing

[/ QUOTE ]

This should be:/bind enter "startchat$$afk Typing..."

---

The wisdom of Shadowe: Ghostraptor: The Shadowe is wise ...; FFM: Shadowe is no longer wise. ; Techbot_Alpha: Also, what Shadowe said. It seems he is still somewhat wise ; Bull Throttle: Shadowe was unwise in this instance...; Rock_Powerfist: in this instance Shadowe is wise.; Techbot_Alpha: Shadowe is very wise *nods*; Zortel: *Quotable line about Shadowe being wise goes here.*

[ QUOTE ]
[ QUOTE ]
/bind startchat $$AFK Typing

[/ QUOTE ]

This should be:/bind enter "startchat$$afk Typing..."

[/ QUOTE ]

Ty for pointing that out. I am not going to bother making version 1.2 over one small typo, so I'm going to ask GR to edit this.

---

The_Phantoms, firstly thank you for the mention and quote...
[ QUOTE ]
Following from version 1.0, Coolio_Wolfus posted this very excellent mini add-on:

[/ QUOTE ]
Secondly I think the typo Standoff was refering to was your use of 'powerexc_',
rather than the 'powexec_' you quoted me using.

I refer you to Paragon Wiki's 'The Incomplete and Unofficial Guide to /bind'

And yes Standoff the command interpreter ignores _'s, meaning that pow_exec_, powexec_ and p_o_w_e_x_e_c_ are technically the same, however you may wish to drop the _'s when you are entering very long command chains to conserve space.

---