Custom Latency Tolerance

Necrachilles · **Posted:** Tue Nov 16, 2010 1:23 pm

Someone care to explain the full dynamics of this to me or even simplify it? Right now I have it set at 80 and the ability queue system seems gone (thank god) but I wanna know what would happen if I set it to 0.

Weena · **Posted:** Tue Nov 16, 2010 3:39 pm

I don't know what seven of those words mean.

gersh · **Posted:** Tue Nov 16, 2010 3:40 pm

Necrachilles wrote:

Someone care to explain the full dynamics of this to me or even simplify it? Right now I have it set at 80 and the ability queue system seems gone (thank god) but I wanna know what would happen if I set it to 0.

That's implying you have 0 ping correct? So the 80 you have it set at now is implying your average ping is 80. This is just blizz's way of eliminating lag threshold casting bars I assume.

Necrachilles · **Posted:** Tue Nov 16, 2010 4:09 pm

Well my average ping is 80ish if not lower but I'm just curious what will happen if I set it to 0.

Azelma · **Posted:** Tue Nov 16, 2010 4:10 pm

So my average latency is around 100-200, so should I set it to 150? Would that make me more leet?

Battletard · **Posted:** Tue Nov 16, 2010 4:53 pm

Azelma wrote:

So my average latency is around 100-200, so should I set it to 150? Would that make me more leet?

Set it to 1337

Meowth · **Posted:** Tue Nov 16, 2010 6:39 pm

http://forums.worldofwarcraft.com/threa ... eNo=12#226

Necrachilles · **Posted:** Thu Nov 18, 2010 2:49 pm

Meowth wrote:

http://forums.worldofwarcraft.com/thread.html?topicId=26859116137&sid=2000&pageNo=12#226

I read this forever ago and this does not answer my question.

Laelia · **Posted:** Thu Nov 18, 2010 6:54 pm

I think it works roughly like this: if you set tolerance to 0, you won't be able to do a new action until the GCD has ended on the server, which means there is a gap equal to your latency between when the GCD appears to end on your client and when you can use another ability. If you set it equal to your latency, you can issue another command as the GCD ends on your client, eliminating the gap, which feels most natural. If you set it too high, your command gets queued up too early, and you can't react to procs etc.

Necrachilles · **Posted:** Thu Nov 18, 2010 7:39 pm

Laelia wrote:

I think it works roughly like this: if you set tolerance to 0, you won't be able to do a new action until the GCD has ended on the server, which means there is a gap equal to your latency between when the GCD appears to end on your client and when you can use another ability. If you set it equal to your latency, you can issue another command as the GCD ends on your client, eliminating the gap, which feels most natural. If you set it too high, your command gets queued up too early, and you can't react to procs etc.

That makes sense to me and this is kinda what I suspected. Thanks a ton.

dek · **Posted:** Thu Nov 18, 2010 8:05 pm

Laelia wrote:

I think it works roughly like this: if you set tolerance to 0, you won't be able to do a new action until the GCD has ended on the server, which means there is a gap equal to your latency between when the GCD appears to end on your client and when you can use another ability. If you set it equal to your latency, you can issue another command as the GCD ends on your client, eliminating the gap, which feels most natural. If you set it too high, your command gets queued up too early, and you can't react to procs etc.

That makes perfect sense. Just curious, do you have any idea what would replicate what the functionality was pre-4.0.1?

Necrachilles · **Posted:** Thu Nov 18, 2010 8:12 pm

dek wrote:

Laelia wrote:

I think it works roughly like this: if you set tolerance to 0, you won't be able to do a new action until the GCD has ended on the server, which means there is a gap equal to your latency between when the GCD appears to end on your client and when you can use another ability. If you set it equal to your latency, you can issue another command as the GCD ends on your client, eliminating the gap, which feels most natural. If you set it too high, your command gets queued up too early, and you can't react to procs etc.

That makes perfect sense. Just curious, do you have any idea what would replicate what the functionality was pre-4.0.1?

I think it all depends on your latency, if you want maximum reaction time, set it kinda low. My ping is normally between 70-90ish so I have it set to 80. If you set it close to your ping, you can queue the ability up a split second before the server tells you that you can. If you wanna do it the hard way I'm sure you can set it to 0 at which case it won't let you hit the button till the server has finished the GCD and relayed it back to your comp. With mine at 80 the Ability Queue System is gone.

Short answer: Probabaly just set it to 0.

Laelia · **Posted:** Thu Nov 18, 2010 9:35 pm

dek wrote:

That makes perfect sense. Just curious, do you have any idea what would replicate what the functionality was pre-4.0.1?

I think setting the tolerance to just above your latency will feel like the previous behaviour. The problem with 4.0.1 as I understand it is that the tolerance was set too high, so you got locked into your abilities before you expected it.

Necrachilles · **Posted:** Thu Nov 18, 2010 10:09 pm

Laelia wrote:

The problem with 4.0.1 as I understand it is that the tolerance was set too high, so you got locked into your abilities before you expected it.

^

Spacehunter · **Posted:** Thu Nov 18, 2010 10:31 pm

My regular latency is higher than the upper limit of this feature.

hi5

Bucket Guild | FUBU BH Forums

Custom Latency Tolerance

Who is online