Results 1 to 10 of 14

Hybrid View

  1. #1
    Player
    wdbgeo's Avatar
    Join Date
    Sep 2013
    Posts
    2
    Character
    Aeliya Ashengaurd
    World
    Behemoth
    Main Class
    Gladiator Lv 30
    Here is what I use.

    /micon Physick
    /ac Physick <mo>
    /ac Physick <t>
    /pac Embrace <mo>
    /pac Embrace <t>

    This will make either Eos or Selene cast Embrace on the same target you are healing. You still get the error message though. You can turn that off in chat settings. You con hover over the target or the party list. Either one works. The Embrace CD is also a bit longer than your Physick. Hope this helps.
    (0)

  2. #2
    Player Nadirah's Avatar
    Join Date
    May 2015
    Location
    Gridania
    Posts
    1,978
    Character
    Nadirah Serenity
    World
    Excalibur
    Main Class
    Paladin Lv 60
    Incredibly annoying.

    Why can't they use a macro system that *doesn't* suck? Lol
    (0)

  3. #3
    Player
    Lyrica_Ashtine's Avatar
    Join Date
    Dec 2013
    Posts
    1,132
    Character
    Sadako Yamamura
    World
    Phoenix
    Main Class
    Marauder Lv 1
    Quote Originally Posted by Nadirah View Post
    Incredibly annoying.

    Why can't they use a macro system that *doesn't* suck? Lol
    The macro system itself is fine, it's the targeting mechanism that's a bit funky for healing.
    If you target an illegal target to heal (ie: a monster), the spell would be aimed back at the caster. Same applies to your pets.

    However, this does not apply if the target doesn't exist in the first place, thus the <mo> combined with <t> would work:
    /pac "Embrace" <mo>
    /pac "Embrace" <t>

    If you haven't pointed your mouse at anything that can be a legal target, <t> would apply. But with some monsters being as big as they are or as close as you have to be or with people running all over the place, you have to really pay attention to where your cursor is pointing at. Even pointing it at your party list would trigger the <mo> line.

    There is also the thing that the second line for <t> wouldn't be anywhere as fast as normal for some reason.
    (0)