[Data Center USA] Ping increased. Report your changes here.

[Zojha]

So yeah, they can claim that the game is "designed" for 200ms, but it's not.

Or they might just do what they often do and just do stupid calculations.

If you go solely by math, one OGCD will only take around 0,250-0,750 MS animation time. That means 2 would at most take 1,5 seconds, which leaves 500 MS for latency -> Up to 250 you're fine.

I mean, if the team designs savage fights under the premise that a tank only uses his aggro combo throughout the fight, then the team likely also calculates everything else in a somewhat odd manner.

[Hamada]

Or they might just do what they often do and just do stupid calculations.If you go solely by math, one OGCD will only take around 0,250-0,750 MS animation time. That means 2 would at most take 1,5 seconds, which leaves 500 MS for latency -> Up to 250 you're fine.

I mean, if the team designs savage fights under the premise that a tank only uses his aggro combo throughout the fight, then the team likely also calculates everything else in a somewhat odd manner.

That is not correct, you are not accountinig the clipping the game does. Once you use a GCD > it clips into the ocgds and that is where ping matters, then to the next ogcd, then if this is not done fast enough it will clip into the next GCD.

OCD>delay>ocgd>delay>ocgd>delay> OCD used after OCD reset= dps loss.
vs
OCD> no delay>ocgd>delay>ocgd>OCD used right when OCD timer reset
.
The delays are programed in the game as is, but with ping being high enough 100-120? you will run into what I bold, that kind of clipping. You may also run into ability use errors time to time, like how SWIFTCAST> summon = hardcast summon with the swiftcast buff on my buff bar. The game is badly coded, there is no way people can defend that it is not.

[Zojha]

That is not correct [...]

That's the entire point >_>

The calculation is supposed to be unrealistic and incorrect.

[Hamada]

That's the entire point >_>

The calculation is supposed to be unrealistic and incorrect.

OHHH you are trying to figure out where they get the idea 200 ms = no impact on your play? yeah if that is the way they do it then it is way off, they seriously need real field testing by people with high reaction times, even some of the posters here can't see those delays.

I spent 30 minutes last night fiddling around with my no-warrior ninja opener to get aeolian edge back inside trick attack. I'm not the best ninja around so I imagine better players would notice it more than I did. Mudras always clip and feel slow to me and it doesn't really seem any different I just noticed my last attack wasn't inside trick attack anymore.

Before they also mentioned how AoE telegraphs were fine and there was no issue with landslide and such and obviously there was and they changed the behaviour because of it. (same with jump, etc.)

Just because something was mentioned before one time does not mean it is a) always true and b) applies to everything and c) things change so maybe 200ms was fine at lvl 50. That means nothing at lvl 60 our rotations are totally different with a lot more abilities and tighter timing for skills!

agreed, 200 ms is different then 100 ms and different then 30 ms as far as impact on your rotations. If you know how to super tight your rotations it really does matter and it is noticeable, MCH openers fit in this as well. "I can double weave at 100 ms fine" to me translates "I do not see the small clipping in my next ocd so I feel it is fine. (its not, SE needs to code the game better)