This project is read-only.

Network Latency formulation

Topics: Rawr.Base, Rawr.Mage
Apr 2, 2011 at 12:24 PM
Edited Apr 2, 2011 at 12:26 PM

Is it included? I noticed 'Cast Latency' but I suppose that's merely 'human lag'. Hrm, would it be clever to include it there? But I'm worried that's wrong since there is a casting queue (unless one disables it). Though I don't know if that queue reduces lag impact or how it does it.

edit: Also I don't know if network latency is an impact at all nowadays. I recall though distinctly that in 80 there was a simulator for Death Knights that had it simulated. Or at least attempted to, I guess.

Apr 2, 2011 at 11:44 PM

Spell queue should mitigate most of network latency. What 'Cast Latency' represents is effective latency, that is kind of network latency + human latency - spell queue reduction. Basically whatever number you would get if you tried chaincasting, looked at total time it took you to cast a number of spells, computing what it should took you based on your haste and whatever it took extra per spell is your 'Cast Latency'.

Apr 3, 2011 at 1:06 AM
Edited Apr 3, 2011 at 9:31 AM

How can one determine reliably that real total latency?

Apr 3, 2011 at 9:38 PM

Usually you'd do that on combat dummies. Enable combat log, do some chain casting and then do the math. It's easiest to do if you only cast one spell that has constant cast time. So if you cast it n times, just look at time between first and last damage done event in combat log and compute (combat log time difference) / (n - 1) - cast time based on haste.