+ Reply to Thread
Results 1 to 6 of 6

Thread: Macro Lag

  1. #1
    Shadowlander
    Join Date
    Nov 2011
    Posts
    43

    Default Macro Lag

    Gang,

    Been seeing "macro lag" come up a lot lately with the talk of new specs and rotations. Can someone please explain what kinds of macros make this happen, and how to avoid it? Or simply explain a bit more about it? Thanks.

  2. #2
    Ascendant Credo's Avatar
    Join Date
    Jan 2011
    Posts
    4,172

    Default

    Don't use macros.

  3. #3
    Rift Chaser Sharpshooter's Avatar
    Join Date
    Feb 2011
    Posts
    354

    Default

    Macro lag is usually created by macroing skills that have conditions.
    For example if you macro Bladedancer's Quick Strike.
    The condition is that it can only be used after Keen Strike.
    Or when you are macroing things like Break Free.
    Any skill in a macro which the game needs to check whether its condition is met will create a macro lag thus should be avoided.
    Sharp - Moirae - Icewatch - EU
    http://moirae.guildlaunch.com
    Balaenae nobis conservandae sunt!

  4. #4
    Ascendant MoonfireSpam's Avatar
    Join Date
    Jul 2011
    Posts
    4,730

    Default

    Should be noted that this was kind of a relatively recent development =P

    Most notably after conquest was introduced.

    I don't know what they screwed up... or just how much of their system resources CQ eats up, but some of the geezer specs of forever ago used giant one button spam macros with everything in it (most notoriously the old shaman)... and it was never an issue with a macro that had half a dozen conditional abilities.
    So long, and thanks for all the fish~

  5. #5
    RIFT Guide Writer
    Join Date
    Mar 2011
    Posts
    2,422

    Default

    Quote Originally Posted by MoonfireSpam View Post
    Should be noted that this was kind of a relatively recent development =P

    Most notably after conquest was introduced.

    I don't know what they screwed up... or just how much of their system resources CQ eats up, but some of the geezer specs of forever ago used giant one button spam macros with everything in it (most notoriously the old shaman)... and it was never an issue with a macro that had half a dozen conditional abilities.
    No it's not a recent development and has nothing to do with conquest. Cooldowns are not the same as conditions.

    Sharpshooter already explained it but I'll go a bit deeper into why it happens. Let's take an example of the most typical laggy macro which is quick strike+keen strike.
    Case 1. Keen strike has been used so you want quick strike to get used with the macro. Your macro tries to queue quick strike just like you want and it goes in the ability queue waiting for gcd to be over. This case works as intended.

    Case 2. Keen strike has not been used so you want keen strike to get used with the macro. When you use the macro your client only tries to queue quick strike. It will not try to use keen strike at all until your global cooldown is already over. Your first attempt to use the macro after gcd is over will result in the server denying the use of quick strike and the macro goes forward to using keen strike. However all this wastes a lot of time and is known as macro lag.

    Another common occurrence of macro lag happens if you have backstab in a macro and you are positioned in front of a mob.

    Client checks for cooldowns when using macros so those can be all macroed together without lag.

  6. #6
    Shadowlander
    Join Date
    Nov 2011
    Posts
    43

    Default Got it

    Thanks for the detailed explanations

+ Reply to Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts