Is this a lag issue or a game fault...

Tonestar34

There is a geyser boss that 1 shots me every time by a wave of water that crashes over me... But I'm actually dead before this ever happens.

The game signals that the boss is about to do the aoe move by turning the ground red. Instantly I die. Couple of seconds later the wave of death floods over my lifeless corpse...

Lag, sounds like it... Except my timming only ever seems out with this particular geyser boss.

MrGarlic

That wave kills many players. It hits hard. Ensure you have max health at all times when it appears.

It's not easy. It's not meant to be.

But as for being indicated dead before being hit. Yep, that's lag. The dead bit isn't.

That particular boss you either need to kite from range or have enough health/resistance to avoid the one-shot.

Mr_Walker

Tidewrack?

I get one shotted by that all the time too. I'm in Australia, so lag generally means by the time I see it, it's too late.

There's a couple of things like that in the game

Ackwalan

If you look close, there is a red ring that appears before the red circle. It is a very large AOE and the red ring is also large, so many melee attackers never see it. Seeing the red ring gives you time to get out of range or block, not the red circle itself.

Mystrius_Archaion

MrGarlic wrote: »

That wave kills many players. It hits hard. Ensure you have max health at all times when it appears.

No, just hold block.
You don't need max health as block makes the hit really small.

Tonestar34

You guess correctly Tidewrack... I have tried to guess when to block... Sometimes I get it right and survive... Now the reason why I query if this was lag... I've had a similar experience in Wardenfell. You know those big bugs that jump at you after you shoot them with an arrow?

Well I used to have an issue where the bug would jump, I'd hit block and it didn't matter. My charchter would get stunned... But that appears fixed... I see the bug jump... I can even cheekily wait half a second and boom... I successfully block.

Now I used to think that was lag related but now it appears fixed.