ELI5: How are the current dungeons hard?

[Jinglypockets]

Compare the speed of resolution of, for example, the final boss of Malikah's well (the "5 cercles or crosses" part) with the X/O phase on the first boss of Alexandria. Now tell me they are the same.

They both give you around 7 seconds to react to the telegraph.

Alexandria's mechanic resolves much more quickly once it starts, but reaction time is completely irrelevant at that point.

[TDawnstar]

Alexandria's mechanic resolves much more quickly once it starts, but reaction time is completely irrelevant at that point.

No it's not, because that's when the netcode limits starts to show. Which was exactly my initial point

[Caitamm]

No it's not, because that's when the netcode limits starts to show. Which was exactly my initial point

I don't see how reaction time is factored in here. You know the exact pattern of X/Os well before the first one even goes off, you know the order they are going off in. Additionally, you know the pacing of when the damage comes out unless it's your very first time seeing the boss.

[EiraWoqiso]

No it's not, because that's when the netcode limits starts to show. Which was exactly my initial point

If you're having netcode issues that bad, I really think that's a problem with you, not the game. I'm almost as far away from the NA DC as possible in the US (AND on one of the worst network circuits to the server) and I don't have any issues with the netcode during that dungeon at all. Maybe if I'm a few milliseconds late in getting into a safe spot, but that's *my* latency.

[TDawnstar]

I don't see how reaction time is factored in here. You know the exact pattern of X/Os well before the first one even goes off, you know the order they are going off in. Additionally, you know the pacing of when the damage comes out unless it's your very first time seeing the boss.

Yes, and then you eat a vuln stack because for the server you are not in the same spot. Is it doable? Yes. But it's annoying as hell, and it stems not from the fight design but from how the client and server interact. A lot of other MMORPGs don't have that issue.

[Jinglypockets]

No it's not, because that's when the netcode limits starts to show. Which was exactly my initial point

Which still has nothing to do with reaction times?

Also, I have enough time on that mechanic to stop and cast Broil between a lot of the moves on Scholar. My ping may or may not be better than yours, but it's certainly not enough better for a gap the size of a Broil castbar to fit through, and it's probably not better than my friend who plays on NA servers from Chile and has never had a problem with it.

It sounds like the problem has less to do with their netcode and more to do with people trying to move reactively instead of proactively.

[Jinglypockets]

Actually, now I'm wondering if people are waiting for the cast animation to finish before moving instead of moving as soon as the telegraph disappears. That would explain a lot.

With 99% of mechanics -- including this one -- you're safe to move the moment the yellow telegraph goes away.

[EiraWoqiso]

Actually, now I'm wondering if people are waiting for the cast animation to finish before moving instead of moving as soon as the telegraph disappears. That would explain a lot.

With 99% of mechanics -- including this one -- you're safe to move the moment the yellow telegraph goes away.

That's a good point, it would definitely explain a chunk of the complaints I've seen.

[TDawnstar]

With 99% of mechanics -- including this one -- you're safe to move the moment the yellow telegraph goes away.

Yes, and it's totally counterintuitive and amounts - once more - to how FF netcode works. It was okay-ish until DT, but in some places it starts to show.

[jdtuggey]

Compare the speed of resolution of, for example, the final boss of Malikah's well (the "5 cercles or crosses" part) with the X/O phase on the first boss of Alexandria. Now tell me they are the same.

I still don't get how people find this mechanic problematic, people see it as this clump of 6 rapidly firing mechanics, and I see it as just one mechanic.
I think ahead of time where I need to go, and I clear it in one fluid motion, I don't really stop, unless immune reaction gets in the way.
Like, maybe that could explain why some people struggle with a lot of new mechanics, yeah, if I felt I have to compute 6 mechanics successively in about 3 seconds, I'd panic too, so I switch to easy mode and see it as one large chunk.
I seem to see a lot of people that don't understand that it's safe to walk in a VFX too. If you're in the telegraph when it disappears, you're gonna get hit 2.5 secs about later, no matter where you are.
If you're not in the telegraph but you walk where it was right after it disappears, a nuke might fall in your face and you're still not gonna take damage.
The telegraphs for antivirus are on screen barely a second, you don't have to stop moving, and you should already have computed where you're heading next, you had 10 seconds to do that prior to it starting to resolve.
Continuing moving will place you where you need to be everytime without really paying attention ? Maybe it's just me ? lol
Again, this isn't 6 rapidly firing mechanic, this is one single mechanic that lasts like, 20 secs total. :P
Also it might seem random, but it's not. It's always setup so you can get away from immune responses, to the point where you can almost ignore these cast.
You'll always be very close to where you gotta be to avoid it if you follow the XO pattern correctly.
Also I live in northern Canada, my latency is -always- at the very least 100ms, oscillates between that and 150 abouts ?
Like, we all experience the same netcode, and many are fine with it and can clear content without leaning on this to explain poor performance or demand change.
I'm not sure netcode will change, cause it would change the feeling of the game and how it plays, and all the content is made with this netcode in mind. ;o