What's with the AOE indicators?

[CyrilLucifer]

This happens all the time to me, still, to be honest, and my connection is above-average.

It's better than it was before the changes, but last night I still got hit with an AOE I was 5 steps away from. There's no excuse for that.

[Reuskon]

This is wrong. To test I have moved out of the circle and then moved back in while the circle was still red and do not get hit sometimes. There seems to be something very wrong with the way this works on some encounters/enemies.

There was a gif on the beta forums I saw that demonstrated exactly what you're saying.

To me I feel like this is the worst aspect of the combat system in ARR. What's worse is that it's designed this way intentionally. If I see a telegraph of a skill, and react properly and get out of the way in time (via my screen, as in what the game is programmed to show me), I should not be hit by a skill that should have missed. All they really need to do is sync the skill progress bar with the aoe display, instead of having one offset from the other.

[Menubrea]

Server checks your position every .3 seconds, so basically if it updates at an unfortunate time (say, like right before you're about to exit the area), you're pretty much bound to be hit and there's nothing you can do about it. Some telegraphs are more lenient than others by having a longer cast time, and for those this is a none issue. On the other hand you have some telegraphs that happen so quickly that you sometimes even get hit even if you're moving as it targets you, and that's honestly beyond silly as in this example both reaction and response times is a none factor.

[Evilized]

it's normally about a half second for me. if i make it out by the mid-point of the tell being put on the ground i am safe.

it's a pain though when the entire raid is getting hit by things that they should not be, like on hydra and terrifying gaze or whatever his fear/ae/paralyze/dot/dd is called. we had the entire raid standing on him for a good 5 seconds before it went off last night in a couple runs and we still all got hit.

[TrystWildkey]

In my experience, it's not a lag issue. It's that the AOE indicator is a separate indicator from the actual casting bar. They are related, but not the same thing.

The AOE indicator shows you Where the attack will be.

The casting bar of the enemy shows you When the attack will hit.

The casting bar is the more important of the 2 indicators since that's what determines whether or not you get hit. As soon as you see the AOE indicator, move. Often, the casting bar finishes well before the indicator disappears.

[Ladon]

In my experience, it's not a lag issue. It's that the AOE indicator is a separate indicator from the actual casting bar. They are related, but not the same thing.

The AOE indicator shows you Where the attack will be.

The casting bar of the enemy shows you When the attack will hit.

The casting bar is the more important of the 2 indicators since that's what determines whether or not you get hit. As soon as you see the AOE indicator, move. Often, the casting bar finishes well before the indicator disappears.

This has been my experience as well. The line indicators often do not match up with the cast times and they seem to be more of an indication of where an attack is going to be, NOT when.

[Lovescake]

Its not an AoE circle...

its more of a lock-on circle. if youre in it and it vanishes, youre gonna get hit.

same with plumes and everything else. Even if you run out of it a second too late its classed as an executed attack and it will damage you.