Which means the 0.3 is not a bug it is working as intended. They just need to up the accuracy.
healing yourself for more than the next hit, then getting confirmation of it and still dieing is proof of a race condition
it is race conditions cause by unsynched threads of execution on the server
moving out of an aoe and having a chance of still being hit by it when the server knows exactly where you are is by definition a race condition
Last edited by TheRac25; 11-10-2013 at 06:01 PM.
The more I progress the more this becomes a problem. I absolutely cannot believe this is intentional.
They REALLY need to look at the clunky game mechanisms and try to fix them. No amount of content is going to make up for a clunky game.
Since nothing has really been done so far, this is kind of how I am hoping this issue gets elevated. As more and more people reach the end (because some are, understandably, taking their time), more of them will notice the elephant. With more outcry, maybe SE will then do/say something about it (I hope).
Q20: Will we ever be able to send tells from within an instanced area?
A20: While the feature can be implemented, it’s currently masked. It’s currently masked because we would like to prevent players from harassing each other just because they know they would never party together in the future. We will continue to monitor the situation carefully as we move forward.
Licks priyas earsSince nothing has really been done so far, this is kind of how I am hoping this issue gets elevated. As more and more people reach the end (because some are, understandably, taking their time), more of them will notice the elephant. With more outcry, maybe SE will then do/say something about it (I hope).
If it's intentional, this game is done. If it isn't intentional, and they turn a blind eye to it for a few weeks as more and more people experience the absurdity, this game is done. If Square Enix wants this game to have long term success, they'll either change their mind about what they're doing intentionally, or they'll make an effort to fix something that happened accidentally. Hopefully this thread stays front and center until Square Enix addresses it.
This issue is going to be a make-or-break thing for me too. I'll grudgingly stick with it for the rest of the month's subscription, but if SE still haven't at least acknowledged the problem and promised fixes by then, that'll be it for both this title and any future online games from Square-Enix.
It's a real shame to see such a solid game hobbled by such basic technical issues, and the lack of communication only helps to further undermine my confidence in the management and future potential of this title.
It might just be a pet peeve but I wish people wouldn't use terms that they don't fully understand. Race conditions is when A and B both try to do something simultaneously, and sometimes A wins and sometime B wins and that's a problem because you don't know what to expect. FF14 does not have this problem. The server always wins. The end. The time you think you won is because the server took mercy on you, not because of anything you did. Note that in every other MMORPG, the client is the one that always wins. It has to because the server can never have the most recent info on player position, so if the server could win, you will always have the 'but I dodged that' issue.
No need to argue semantics here. Not a single one of us knows 100% for sure what's going on behind the scenes, so arguing saying it's absolutely one thing over another is rather silly, and may end up taking away from the issue. I don't think the issue is truly intentional at this point. I do honestly think they don't know how else to code it, or don't want to spend the resources to fix it.
If the issue is merely caused by coding incompetence or just being cheap, other MMORPG should suffer the same problem because there are a lot of bad MMORPGs out there that have no budget to work with.No need to argue semantics here. Not a single one of us knows 100% for sure what's going on behind the scenes, so arguing saying it's absolutely one thing over another is rather silly, and may end up taking away from the issue. I don't think the issue is truly intentional at this point. I do honestly think they don't know how else to code it, or don't want to spend the resources to fix it.
FF14 1.0 didn't have jump as a basic feature. It's basically the same kind of issue here. There's a serious disconnect between the development team of this game and versus the standard of the industry. This is the only possible way why this game have problems that literally no other MMORPG have.
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.