input delay kills the game

[NephthysVasudan]

LOL

That's what I call a glitch/bug...not lag.

I've seen that since day one. I abuse it...frequently.
Now what really gets me torn up is when I get a telegraph....and I move....and I still get hit even though im clearly outside the telegrahed area.

My mentor explained to me that If I start casting and I wait until the 0.7-0.3 seconds and start moving - the game will ignore the fact I moved and hit me with the damage.
There are days it wont hit me.

Honestly I wouldn't call this lag....I'd call it game mechanics not quite being in synch with you or some other thing.

The lag I speak of is when the timer starts skipping/glitching out/delaying very long/jittering (hard to describe) - log messages stack upwards of 2 to 3 minutes and dump on you like a avalanche.

Damage not catching up to you or vice versa...etc..etc..

And yes its all things you can adapt too...its call exaggerated moving. You move further...you do things sooner rather than later...etc.

not sure if all of the above made sense. - Is it game breaking? Hell no....its just the nature of the game is what I call it (the 0.7 thing)
In truth - and lets be honest - the spell should "fail/interrupt" if you move any time before ~0 seconds (obviously ignoring insta-casts)...end of discussion. So for anyone to complain about this? should just shut up and play the game ^_^ - For it to be a "thing" at 0.7 is a mixed blessing/curse.