Feedback: FIX YOUR NETCODE!

[Kiurt]

No. The FF14 devs only listen to the forums. The forums are inhabited by and large by some of the most entitled and awful players in this game. I don't use reddit, I'm just tired of my voice, of the voice of basically the entire damn playerbase being overshadowed by the loudest and whiniest voices. If this is where I have to go to be heard then I go here. The healer strike was bad enough, but I didn't make an account for that because I genuinely didn't see that going anywhere. This topic on the other hand is extremely important to me.

I've had to deal with absolutely brainmelting trivial content when doing non-endgame stuff for two expansions. I've seen jobs gradually have identity and complexity eroded from them. I've seen the fruits of this forum's complaints manifest in the degradation of this game for multiple expansions. I've had friends quit because they just can't deal with another expansion of falling asleep while playing. These aren't toxic turbo hardcore players either. These are players who play for the MSQ and normal raids and alliance raids and that's it.

We FINALLY have a step in the right direction and we have the forums complaining and demanding SE backpedal. So I'm finally speaking up. You aren't being raided. Your expansions worth of monopoly over getting to say how the game goes is ending.

I mean, in this case, they're not talking about boss fights design. Just that they should improve their overall netcode.

Just to take the Fall Guys event : People thinking they're first and losing to someone that was behind them on their screen.

Also the bullet-hell mechanic, in itself isn't a problem if you're focusing on only dodging. If you're also focusing on uptime, and want to dodge when it gets nearby, well, sometimes it works, sometimes you get hit from 2 meters away and sometimes you can nearly hug the moving projectile. Is it gamebreaking ? Can be depending on how Savage will be. Is it annoying ? Yes. It was already an issue with the red balls in the Nier raid.

But nothing in OP post was about the "new" fights design and how impossible it is to do them.

[Kiurt]

I do agree that they need to make the netcode better.

I don't think you should post this in the "Dungeon Section"

Also "skill" (wasting time) ? Since when ? Or maybe I misunderstood what you mean there.

[Arohk]

Don't stone me on the accuracy about this, but when you see orbs flying around it is something like this

[Valcarde]

Don't stone me on the accuracy about this, but when you see orbs flying around it is something like this

This is how it feels in Strayborough, yeah. Those goddamn poppets.

[NaoEthelia]

Don't stone me on the accuracy about this, but when you see orbs flying around it is something like this

This is actually correct. In any bullet hell mechanics in this game assume that the actual hitbox is one pace in front of it. This is because of a combination of ping and snapshot, but it is always consistently in front of the actual bullet itself. You can even assume you can run through bullets from sideways to dodge it.

[NightHour]

Don't stone me on the accuracy about this, but when you see orbs flying around it is something like this

I think it's more like this -

[Nebam]

Don't stone me on the accuracy about this, but when you see orbs flying around it is something like this

Honestly, that's basically it. It's surprising that people are figuring out how jank mechanics like that are despite it being the case since ARR with things like the clouds in WoD. It's funny too, because they even brought back those same exact clouds in e9(s) and they worked the exactly same way where you'd stand like 2 or 3 ft in front of them to slow them. They were even overly used in the Nier raids with all of the orbs that Yoko Taro loves in his games. It's also probably why so many people eat dirt in those raids, because they don't understand just how far out the hitbox actually extends compared to how it appears visually.

[Raraka]

I play with 150-200 ms roughly from south america, so any improvement to the Netcode is a win

Untill the SA data center comes I will stick to using the network... of cousin Alex

[HemlockEvergreen]

I play with 150-200 ms roughly from south america, so any improvement to the Netcode is a win

Seconding that. While it is perfectly possible to complete every piece of content in the game, the netcode issues force you to adjust in ways that are less than intuitive.

Some examples:

Mechanics that require you to touch another player to pass a debuff, the popularly called "rots", require you to purposefully stay with the player for at least a whole GCD, to ensure that debuff has been passed. Examples of this are the Nisi passes in TEA, Hello World debuff passes in TOP, and rot passes in P4S.

Mechanics that require you to be in a specific position in relation to another player + be moving can fail simply because the difference between the position you see in your screen is completely different than what your server registers. Examples of this are the Limit Cut in TEA and Grand Octet in UCOB.

Mechanics that rely heavily on timing cues to register the position of an AoE also suffer from having a significant difference between what you see on your screen. For example, Thordan's Earthquakes in DSR.

All of these mechanics are perfectly doable. However, you have to consciously adapt to the server-client communication issues. In some cases, the solution is ignoring visual and sound cues and using your own GCDs to measure when you have to move, for example, which is somewhat less intuitive.

If you play PVP, these issues compound, since PVP is not as predictable as PVE encounters. I think anyone who played with long enough has been through a situation where you put your guard up, your ability is spent, but you get hit anyway because the server registered your adversary's input before yours.

[Mooserocka33]

Some people have NEVER played on ps3 and it shows. Please never complain unless you played this game on ps3 where you had to leave every aoe 3 seconds before to not be hit. Ever since nothing has been a problem.