I find it fun :DQuote:
Originally Posted by Mlem
Not sure if it's possible for them to improve the netcode like people seem to desire. Though if it did, it may also end up messing up a lot of players that are used to how aoes and getting hit or not hit works atm. Like 10 years of being used to how it works suddenly getting changed. Not sure if that's worth doing, if it's even possible.
Feedback: FIX YOUR NETCODE!
Printable View
-
07-21-2024, 01:37 PMChyro
-
07-21-2024, 02:24 PMHemlockEvergreenIt is possible. Using the same solution the third-party tools use, which is subtracting your latency from animation locks, is very within the realm of possibilities. A bit more difficult to implement in the case of server side stuff, I imagine, but very much possible.Quote:
Originally Posted by Chyro
As for "people being used to it", it's not an argument. Get used to the new stuff. If you move to a place with different latency, you need to get used to it. If your job gets reworked and you get a different rotation, you need to get used to it. People's inability to adapt should not be an argument to not make improvements to the game. -
07-21-2024, 09:08 PMNebamHonestly, 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.Quote:
Originally Posted by Arohk
-
07-22-2024, 03:26 AMShurrikhanI 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.Quote:
Originally Posted by TDawnstar
...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.Quote:
Also, I like how you left out WoW, which has a much more reactive netcode despite being 10 years older than ARR. :)
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.
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).Quote:
Of course, it's important, no one is arguing about that.
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).Quote:
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.
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).