Feedback: FIX YOUR NETCODE!

[TDawnstar]

They don't, though. There are differences, for instance, between how BDO, Aion, B&S, Tera, and the like handled these verifications and the uptime costs, errors, or other artifacts that might come from it.

Re-read YoshiP's answer. He was comparing a single-player game where everything goes on your device vs an MMO where the information travels to the server and back and is checked.
Also, I like how you left out WoW, which has a much more reactive netcode despite being 10 years older than ARR.

Having to verify the feasibility of an action that the client requests is pretty much universally important

Of course, it's important, no one is arguing about that. The problem is that SE's specific netcode introduces visible latency in the exchange between the client and the server, and therefore, when an attack lands, you may see yourself as outside of it and still inside of it server-side. And when you move, you are still standing still and casting for the server, hence slidecasting. That is a problem that is unique to FFXIV and most other MMOs handle it just fine.

Just like various multiplayer shooter games have their different ways of handling such things, so do MMOs.

Shooters are a different beast, you cannot afford full server authority in an FPS because the generated latency would be too great. Which is why the client is given quite a bit of leeway, and that's how we get all the "wonderful" stuff that hackers and cheaters abuse.

[Shurrikhan]

Re-read YoshiP's answer. He was comparing a single-player game where everything goes on your device vs an MMO where the information travels to the server and back and is checked.

I wasn't referring to Yoshida's answer, but to XIV's handling of a common issue -- per the context in which and intent for which the quote was mentioned. That every MMO has the same fundamental problem does not mean that, as you put it, "all MMORPGs work the same way". They don't, and those differences have different compromises and net losses. XIV's way of handling server checks is especially poor.

Also, I like how you left out WoW, which has a much more reactive netcode despite being 10 years older than ARR.

...Because my interest was in obvious differences in handling and types of artifacts/errors. They're a whole lot more noticeable in games with far shorter minimum internal cooldowns.

I'm not sure why you're trying to make my response out as a cherrypicked defense of XIV; I merely pointed out that the HOW by which MMOs handle this shared problem is important, and that XIV's way of handling it is sub-standard in how it impacts the player experience.

Of course, it's important, no one is arguing about that.

Nor did I. You literally cut the quote before "yes" (my agreeing with you) and its main point (that despite this, games handle things in different ways).

Shooters are a different beast, you cannot afford full server authority in an FPS because the generated latency would be too great. Which is why the client is given quite a bit of leeway, and that's how we get all the "wonderful" stuff that hackers and cheaters abuse.

Neither can you in a PvP-centric action MMO with ICDs as short as, say, 60 ms, tbf. And despite XIV's uptime-crunching way of handling action verification, it's still had cases whereby it could obviously be hacked (see early Wolf's Den / Feast matches, with people moving and casting at triple speed and shooting through cover).

As it relates to shooters, moreover, XIV's case of projectile hitboxes not being where they appear, moreover, is similarly mostly a matter of (lacking) client-side predictive animation (too much, and corrections are jarring; too little, and the constant disconnect is likewise jarring).