Had similar issues in Fang Lair with the cadaver animal fight and syncing, resulting in deaths to AOEs I wasn't standing in.

Some of the AoEs are badly telegraphed. Another reason I've noticed in that dungeon while tanking it is that some of the monsters seem to ignore block. I've gotten one shotted from full health by some of the Gargoyles in the trash pull before Doylemish while blocking. Also Zaan did the same. I haven't even lifted my finger from RMB. I've actually started to roll dodge instead of blocking some of the heavy attacks due to the fact it's so unreliable.

@ZOS_Finn is the right guy to tag though.

lol, pve tanks crying that theire permablock does not work anymore xD learn too dodge, oneshot mechanics for tanks are so totaly last year.

So the way movement in ESO works is that when you press the movement key, your local game client immediately moves you (to give you the sense that it's being responsive) and then send the movement command to the server.

Contrast this with casting abilities: You issue the command on your local game, it's sent to the server, and only after the server had processed the command and replied to the local game client will you see the ability fire.

The implication of this is that when it comes to character movement, whatever the server "sees" will always be lagging behind whatever you see on your screen, and the degree of that latency will depend on your connection and the server's load.

So, what does this mean? It means if you dodge out of a cone, your client shows you're outside of it, but the server still thinks that you're inside, and you're killed. If you're already outside of the cone, you'll live. The cone isn't actually bigger than what's shown--it just feels like that way because your game client is moving your character out of the cone faster than the server is.

This is also why the laser beam is sometimes hard to get--on your screen, you are right in the middle of the beam, chasing it, but to the server, you are just following the beam from behind, not quite catching it. Similarly, as you try to avoid the beam, it may seem like you are barely avoiding it, but the server might think that you're not quite out of it.

This is why the most reliable way to catch the beam is to crash into it from the "front" rather than chasing it from the "back".

As far as the poison cones go, this is why the most reliable way to avoid them is to always stay near the seam, so that the amount of movement needed is minimal. Also, increasing the poison cone warning from the current 2s to 3s would help tremendously.

Fang_of_Lorkhaj wrote: »

Let me start of by saying in no way am I crying for a nerf or that it's too hard but I feel that something needs to be pointed out.

During the massive aoe poison phase 4 people must attend to their assigned elements to avoid a one shot Insta death, however. The beam doesn't encase half the time when standing in it. The poison waterfall doesn't protect an individual from death even when perfectly timed and lifted in the air to avoid the one shot sometimes.

The AOE abilities are going off when you arent remotely even close to activate them thus wasting an aoe to not Insta die during whole stage poison phase.

Last but not least the worst of it all. During poison phases throughout the fight, when you run out or dodge out of the poison direction it still kills you. There is 0 reason an aoe should be killing someone when they are 1 to 5 feet out of the area of effect. Perhaps the AoE has more area than we can see but this needs to be address. Please take this into consideration.

you're right something is off. I've experienced all of these issues myself but I also saw 1 common factor in all this that explains it: there's a considerable delay between what is happening and what the server thinks is happening. I would say lag but I had perfect ping to the servers when I saw this so it's not frontend lag in any case.

When I'm out of the red cones up to 2 meters (roughly 1 second) the server still thinks I'm in it, as if the server is 1 sec behind.

When I reach the yellow circle in time i'm stil deat, as if the server still thinks i'm running towards it

when I start blocking teh flame beam the person affected still takes a tick (and possibly dies from it) as if the server thinks that I'm still not in place

in short, the server calculates everything happening as 1sec later...


hope that helps the devs

@ZOS_Finn

GlorphNoldorin wrote: »

Some of the AoEs are badly telegraphed. Another reason I've noticed in that dungeon while tanking it is that some of the monsters seem to ignore block. I've gotten one shotted from full health by some of the Gargoyles in the trash pull before Doylemish while blocking. Also Zaan did the same. I haven't even lifted my finger from RMB. I've actually started to roll dodge instead of blocking some of the heavy attacks due to the fact it's so unreliable.
Edited by Asardes on March 2, 2018 6:42PM

Man it is so good to hear this (on the one hand.....not so much that we get instashot)..... I thought ....is it my lag or what? I could have sworn I was blocking.

Playing on Oceanic ping, this is just miserable trying to avoid the poison.

There are definitely bad telegraphs in this fight.

A friend of mine tanking it was getting one shot through block and she discovered that bashing it (even though the indicator was to block or GTFO, gold rays not red bashable) stopped the one shot from happening. Dodging was iffy as sometimes she'd just follow you and one shot you and anyone near you.

A few days later I tanked it and the same thing. She one shot me several times with 75%+ of my stamina available, right through block, and I'll be damned bashing actually stopped the one shot. Maybe the indicator is showing gold and it should be red, or maybe it's just broken, but either way, it is not working as it should.