Why the netcode issue exists, and why it cannot be fixed.

[Goreth]

What's missing from this discussion is the understanding that it's not a black and white issue.

The bottom line is that SE just has shoddy netcode for this game.

Looks black and white to me.

[Astarica]

This problem absolutely is black and white. If you're standing in a telegraphed area and the boss casts the "YOU DIE" spell, and you're just standing still, you absolutely expect to die the moment the castbar ends in any MMORPG. Unless other MMORPG have manaaged to figure out how to teleport data, the client absolutely is the one making the call here. Hacking is way overblown as a concern. If you get hit by the 'YOU DIE" spell, there's very little the client can lie to survive that. You can claim you didn't get hit by it, but the client still sends your current position and the server can see you're lying. You can change your position too but that's teleporting which is very easily caught. You can lie about the damage you took from but the server knows you're supposed to take a million damage from YOU DIE too. You can lie about what CDs you used to survive it, but the server also knows when those CDS are up.

The best case scenario is you might be able to lie about using a CD you forgot to use (but is still available), but you could just learn to use your CDS too.

[Sybreed]

Bump for great justice.

[Sunarie]

Bump cause this thread, of any of them.. really needs to stay on the first page. Lots of beneficial discussions that maybe SE could take note of.

[Alcyon_Densetsu]

Bump cause this thread, of any of them.. really needs to stay on the first page. Lots of beneficial discussions that maybe SE could take note of.

Yep!
Especially as we close in on the next LIVE Letter with a pile of questions about the netcode/lag issues.

[Wildsprite]

atleast 1 person mentioned this was client side polling. the issue with that is Yoshi-P confirmed it was server side polling

Yep!
Especially as we close in on the next LIVE Letter with a pile of questions about the netcode/lag issues.

most of which said questions were ignored, they did say something about changing the polling in wolves den, great for PvP. but they really need to fix the polling issues in DF bosses like the primals, 3ms polling in those fights makes them difficult even though they are predictable. you only have to be 1ms off with their predictability to end up with the fight going completely down hill. factor in 3ms server side polling and any possible lag nomatter how small and that predictability goes to hell

[Sunarie]

most of which said questions were ignored, they did say something about changing the polling in wolves den, great for PvP. but they really need to fix the polling issues in DF bosses like the primals, 3ms polling in those fights makes them difficult even though they are predictable. you only have to be 1ms off with their predictability to end up with the fight going completely down hill. factor in 3ms server side polling and any possible lag nomatter how small and that predictability goes to hell

Actually, they addressed the question that many players were being hit by AOEs they were out of directly. Here's a full translation of their response, "Q2: You have said that in FFXIV: ARR, the character's position is checked by the server once every 0.3 seconds. However there are times where the character receives AoE damage even though the character on the screen is outside of the range. Seems like the information on character's position is not up to date. Is there any plan to make an adjustment to this?

A2: If we apply faster response times in all areas, the load on the servers will be too much. Therefore, while it will only be for certain areas (for example high-level content and the Wolves' Den), you will be able to notice the faster response times. Please stay tuned!"

What's that mean? High-level content is basically end-game (I don't really see how it could be interpreted another way), and Wolves' Den is PvP. So they are adjusting it for both. The bigger win though, is that they realize it's a problem and are now trying to work to fix it. Even if they start with something that's small, they still recognize it's there.

Please don't go say they're only working to fix it for PvP though, that's just not true.

[Sybreed]

Actually, they addressed the question that many players were being hit by AOEs they were out of directly. Here's a full translation of their response, "Q2: You have said that in FFXIV: ARR, the character's position is checked by the server once every 0.3 seconds. However there are times where the character receives AoE damage even though the character on the screen is outside of the range. Seems like the information on character's position is not up to date. Is there any plan to make an adjustment to this?

A2: If we apply faster response times in all areas, the load on the servers will be too much. Therefore, while it will only be for certain areas (for example high-level content and the Wolves' Den), you will be able to notice the faster response times. Please stay tuned!"

What's that mean? High-level content is basically end-game (I don't really see how it could be interpreted another way), and Wolves' Den is PvP. So they are adjusting it for both. The bigger win though, is that they realize it's a problem and are now trying to work to fix it. Even if they start with something that's small, they still recognize it's there.

Please don't go say they're only working to fix it for PvP though, that's just not true.

Exactly, problem recognition combined with an immediate remedy to the two most dire areas of the problem = we should be happy and stay positive.

[Wildsprite]

It is not 3ms. It is 300ms...

I stand corrected, you are right it is 300ms

Therefore, while it will only be for certain areas (for example high-level content and the Wolves' Den), you will be able to notice the faster response times. Please stay tuned!"

What's that mean? High-level content is basically end-game (I don't really see how it could be interpreted another way), and Wolves' Den is PvP. So they are adjusting it for both. The bigger win though, is that they realize it's a problem and are now trying to work to fix it. Even if they start with something that's small, they still recognize it's there.

Please don't go say they're only working to fix it for PvP though, that's just not true.

this should be fixed for all instanced battles, not just high level content and PvP. that is the point. fixing content that only high level players will see is bad. especially if you want to get new players into the game

[HumsterMKX]

It is not 3ms. It is 300ms...