Originally Posted by
NadEFurY
A lot of higher-level players use AHK for spamming abilities.
The best setting for them(and me) is 0. Now I don't know if it actually disables the queueing function itself at 0 though. Would love it if it did, but alas probably not, just with a detrimental parameter set at 0, effectively negating it, but still eating cpu cycles.
I personally wouldn't reccomend other than 0 to anyone serious about the game. World latency(the non-instanced content) is so bad, and has been bad for over 4 years at least now as far as I can remember. You will get a spell running at (RTT IIRC)130ms, next at 80ms, another 60ms, then 48, 49, 152, etc. The worst kind of lag, the random varying kind. Queuing for the single pressers is prob. preferable because of that exact reason, you press once and forget and don't even care about it but...
Any reactionary play is quite terrible though, and it's also why wpvp is utter shite for another reason, IMO. Idk what they are doing, but likely some anti-cheat service running on the background or some shit on their servers, QoS doing it's fair share of holding packet delivery.
Instanced content though, solid ~39-42 +- 5-10ms, stable. No dips of +50ms(which is noticable), again, don't know why, better servers? No shitty second-guessing services running or something I guess, I mean it's hard to find a reason to fly-hack in a raid I suppose.
But yeah... it's a controversial topic and the best solution is often to not use said feature for people who actually want any sort of reactionary play. A middle ground is possible for people who don't use certain *cough* programs to enhance their play but outside of that, heh, meh, whatever. It's pretty bad in most cases though, especially out in the world if the setting is relatively high...
I do wonder why they removed the other 2, unless they actually improved on it, but hearing "input lag", and "delay" from you guys, tells enough that it's still probably worthless.
The old CVARs were:
reducedLagTolerance - the toggle on/off
MaxSpellStartRecoveryoffset - the actual parameter in ms on how far off the queuing starts.
My latency to my target server, is 26-28ms. Tat is the visible ping when you hover over the computer icon on the lower screen.
My 2cents.