AutoLagTolerance

Generally, setting your Lag Tolerance to even 400ms isn't detrimental any more, as the "ability-lock" first introduced with the Ability Queue is no longer in place (i.e. hitting an ability after an ability has been queued will now override the queued ability). The use of this mod is simply up to whether or not you find that having your Ability Queue's time being close to your latency is what you find most comfortable.

Usage:

AutoLagTolerance will work automatically without any user intervention, and no game setting need to be changed. If you wish to change some of ALT's settings, you can use the commands listed below.

For best results:

Due to the WoW function for returning latency only updating 30 seconds, AutoLagTolerance works best as a means to set your Lag Tolerance to your general latency, and not as a means to instantly set your Lag Tolerance to always be equal to your exact latency.

If your Ability Queue seems to become too short, or too long, play around with the Min and Max settings so that your Lag Tolerance always stays within boundaries you are comfortable with.

Lag Tolerance adjusts how long before an ability has come off of GCD, that using another ability will put it in the queue.

However, this is WoW, and our latency can change a lot and very frequently. Simply setting the Custom Lag Tolerance to a specific value isn't going to work when your latency dips, spikes, and fluctuates while fighting.

Commands:

/autolag - Displays a list of available commands.

/autolagoffset# - ALT will set your Lag Tolerance to equal your current latency by default. You can add a positive or negative offset via this command (in milliseconds).

Example: "/autolag offset -5" will add a negative 5ms offset to your Lag Tolerance. So if you had a latency of 80ms, your Lag Tolerance would be set to 75ms.

/autolaginterval# - Sets how frequently ALT will update your Lag Tolerance (in seconds). Since WoW only updates the Latency information every 30 seconds, leaving this at the default value of 30 is usually best.

/autolagthreshold# - The difference between your latency and the current Lag Tolerance value required to set a new Lag Tolerance value.

Example: "/autolag threshold 5" will make it so that ALT will only change your Lag Tolerance if your current latency differs from your Lag Tolerance by 5ms or more.

/autolagmin# - The minimum value which your Lag Tolerance cannot go under. Doesn't override the default WoW value, but allows you to set a value higher than 0ms.

Note: Typing "/autolag min" without a value will set ALT to use the default WoW value.

/autolagmax# - The maximum value which your Lag Tolerance cannot go over. Doesn't override the default WoW value, but allows you to set a value lower than 400ms.

Note: Typing "/autolag max" without a value will set ALT to use the default WoW value.

/autolagreset - Resets ALT settings to their default values.

0.8

TOC bump.

0.7

Updated for 4.0.6's new Home and World Latency readings.

0.6

Default Interval now set to 30 seconds

ALT will determine when the first GetNetStats() update occurs, and by default will check every 30 seconds from that point on.

0.5

ALT now automatically turns on Custom Lag Tolerance.

0.4

Added a reset command for restoring ALT settings to their defaults [/autolag reset]

More code cleaning

0.3

Added a "Current Lag Tolerance" display in chat when you type /autolag

Would anybody be able to revive this project for Mists of Pandaria (v5.0.4)? My latency including a few other friends fluctuates from 150-210ms constantly and this would be a perfect addon to help keep things in line. The current patch 5.0.4 the addon is broken.

> hitting an ability after an ability has been queued will now override the queued ability

I don't think that's actually true. Or at least the "spirit" of it does not seem to be there practically. In practice if I have it on 400ms, I can easily be stopped from using a new ability within the time frame of those 400ms (and the old initially queued ability will be always used). On 0 this never happens of course but it appears to inflict severe delays on starting the abilities themselves.

I initially suspected the ideal is the 'human reaction time' which is 200msec for most people but that appears to be too much in wow due to keyboard mashing.

Half of it might be good but I do not know how that can be based logically.

Also, the Blizzard suggestion - and what this addon does - to set it to a network latency, might be good but I've yet to see the actual rationale behind it (one that does make clear sense in the queueing discussion, connecting the queuing with the network).

edit: I tend to think the network must be ignored (since its delays will be always there in a relation that is always equivalent (unless Blizzard actively alters that relation)) and go with a fixed number that is related to the human delay that comes naturally. Since there is keyboard mashing in wow making 200ms probably too much, I suspect about half of it might be good. But I do not know if another number might be better and of course it might depend on the person's reaction.

Originally posted by Nibelheim Well, it means they can keep their playstyle, as their queue behavior and rules will remain steady throughout latency fluctuations (i.e if you like to keep a 50ms buffer between your actions, the queue and the servers response time).

If you like the behavior of the addon then use it, if not, then don't.

I don't think you understood. I didn't question your effords, I questioned the reasoning behind the Blizzard Tooltip. If it's just a buffer as many players believe, a buffer that saves pre-casting commands, then a 400msec for example will always be 400msec, having as a 'base' the real ping of the player. If one alters the 400 on the fly then the gameplay experience may be erratic since the 'base' may change while the offset does not remain the same.

i.e. I'm not conviced with the Blizzard Tooltip regarding 'use a number close to your ping'. Either many players are mistaken - which is of course very possible - thinking it's a constant buffer or Blizzard is correct but hasn't documented it clearly.

From what I'm testing I haven't got a clear view. However, I tend to think it's closer to the 'constant buffer having as a base the current ping' idea, meaning a constant 400msec set will be a constant 400msec pre-casting buffer and that's that. I'm getting more erratic behavior with a dynamically changing number. But of course I'm not certain.

Originally posted by tobindax that would mean if someone changes latency changes gamestyle!

Well, it means they can keep their playstyle, as their queue behavior and rules will remain steady throughout latency fluctuations (i.e if you like to keep a 50ms buffer between your actions, the queue and the servers response time).

If you like the behavior of the addon then use it, if not, then don't.

The use of this mod is simply up to whether or not you find that having your Ability Queue's time being close to your latency is what you find most comfortable.

I start suspecting the Blizzard tooltip is misleading and players should be using 400msec unless they want to 'save themselves from themselves' in pre-casting more than they should.

i.e. if someone is in need to just be an 'aggressive pre-caster' the max is probably the best.

There doesn't seem to be an reason to suggest to all players to have it at their ping. Having an offset makes more sense but I don't see the reasoning of Blizzard suggesting having it equal to their latency since that would mean if someone changes latency changes gamestyle!

Originally posted by hipjipp Hi. Great addon you've created here, helps me alot during those laggy periods. I just wanted to point out that since lag is now split into home and world, you need to change line 56 from:

Code:

local _,_,Latency = GetNetStats();

to

Code:

local _,_,_,Latency = GetNetStats();

We don't want to check for home-lag since it does nothing for us in the game-world.
Might get a more accurate estimation with this.
Keep up the good work. =)