Results 1 to 10 of 12

Hybrid View

  1. #1
    Player
    Ninster's Avatar
    Join Date
    Jan 2014
    Location
    Limsa Lomisa
    Posts
    411
    Character
    Ninster Barlow
    World
    Goblin
    Main Class
    Arcanist Lv 90
    Quote Originally Posted by Canadane View Post
    The order doesn't affect what you're experiencing.
    The problem you're having is with the way macros work themselves. Normal abilities can be queued to be used next while you are still casting or your GCD is still counting down. Macros cannot do this. As such, the normal 'flow' of actions you have may be severely interrupted by the use of a macro. I don't use a single macro in battle anymore because of this. A simple Provoke not working at the intended time can lead to a party wipe. The party doesn't need to know I provoked, there's many different ways of seeing that this happened.

    The best possible advice I can give you to avoid using macros in battle. They only cause problems.
    If you absolutely must use a macro, then use a wait before informing the party. This way you're not spamming the chat log.
    An example,

    /ac Action Name <t> <wait.1>
    /p Obnoxious line about using Action Name goes here!

    This is what I was looking for. And I'll definitely go back over macros here in a bit. The only "important" skills I have macro'd are my Raise skills because of Swiftcast, and even at that I might see if I can rearrange my hotbar to where I can manually hit Swiftcast when I need it.
    (2)
    Last edited by Ninster; 01-28-2016 at 05:24 AM. Reason: Can't even quote people because of the dumb character limit