test content
What is the Arc Client?
Install Arc

Energy Builder Macro

Archived PostArchived Post Posts: 1,156,071 Arc User
Hey folks,
There probably isn't an answer to this one, but I have a problem with continually accidentally de-activating my energy builder (EB) as I'm frantically hitting buttons to activate powers. I got round this by re-binding the EB to my middle-button which helps a bit, but ideally what I'd like is to bind MMB to "turn EB on" not "Turn it on or off"

Is that possible?
Post edited by Archived Post on

Comments

  • Archived PostArchived Post Posts: 1,156,071 Arc User
    edited February 2010
    I know this may be a bit late but if you go to the options you can actually set it so that your energy builder never turns off when you switch targets. It takes some getting used to but its awesome. The only time it turns on or off is when you press the hotkey.
  • Archived PostArchived Post Posts: 1,156,071 Arc User
    edited February 2010
    I think I know how to do this. To make the on button, just do (<key> is any key you want):

    /bind <key> "powertrayexec 1 0"

    for the off button use:

    /bind <key> "powertrayexec 0 0"

    the first number is as a 1 or 0 marks on or off, and the second number describes which power slot (you take the number of the slot and subtract 1). To be totally honest I have not used it for my eb before, but it should work just like it does for all the other powers.
  • Archived PostArchived Post Posts: 1,156,071 Arc User
    edited February 2010
    isometry wrote:
    To be totally honest I have not used it for my eb before, but it should work just like it does for all the other powers.
    Nope, EB is special. What you want is DefaultAutoAttack 1 (I think; play with args if that doesn't work).
  • Archived PostArchived Post Posts: 1,156,071 Arc User
    edited March 2011
    What I'd (and I think - the OP) like to do, is have my Energy Builder on 'Toggle, cancel on no-combat' - or whatever it's called, and then have a bind like
    /bind e "+PowerTrayExec 0 $$ +PowerTrayExec 1" - but one where 0 (EB) won't get toggled off.

    In english: cast Firestrike, activate Throw Fire
    in contrast to: cast Firestrike, toggle* Throw Fire

    *or cast, depending on your toggle setting.
  • Archived PostArchived Post Posts: 1,156,071 Arc User
    edited April 2011
    BoneDuck wrote:
    What I'd (and I think - the OP) like to do, is have my Energy Builder on 'Toggle, cancel on no-combat' - or whatever it's called, and then have a bind like
    /bind e "+PowerTrayExec 0 $$ +PowerTrayExec 1" - but one where 0 (EB) won't get toggled off.

    In english: cast Firestrike, activate Throw Fire
    in contrast to: cast Firestrike, toggle* Throw Fire

    *or cast, depending on your toggle setting.

    Try PowerTrayExec 1 0 instead of +PowerTray Exec 0. The "+" means toggle. You don't want that. PowerTray Exec 1 0 says turn the power in PowerTray Slot 0 on. (PowerTray Exec 0 0 would be to turn it off, although the default toggle would also do that.)
  • Archived PostArchived Post Posts: 1,156,071 Arc User
    edited April 2011
    DiasRaven wrote:
    I know this may be a bit late but if you go to the options you can actually set it so that your energy builder never turns off when you switch targets. It takes some getting used to but its awesome. The only time it turns on or off is when you press the hotkey.
    Oh, hey now, I'm going to have to check that out. Seems like a more simple solution to the problem as well.
  • Archived PostArchived Post Posts: 1,156,071 Arc User
    edited April 2011
    Be sure to turn off auto-targeting objects.

    Otherwise you'll spend all your time in a fight shooting at boxes.
  • Archived PostArchived Post Posts: 1,156,071 Arc User
    edited June 2011
    Setting options to "Toggle, cancel on no-combat" and using
    /bind e "DefaultAutoAttack 1 $$ +PowerTrayExec 1"
    seems to work
  • Archived PostArchived Post Posts: 1,156,071 Arc User
    edited June 2011
    This thread is being closed due to content which violates the Atari Community Rules and Policies ~InfoNinja
This discussion has been closed.