surely the LIVE letter will give us hope
surely the LIVE letter will give us hope
Player
OP was wondering, dunno if it's been brought up by now (it likely has since it's been a few days), but reasons for DDOS can be as simple as "it's there".
Think of the most angry, cantankerous Internet troll you've ever come across. Now, with all their pointless spite, give them a tool they can use to massively inconvenience people everywhere. Now, introduce a giant target like online game servers that huge amounts of people congregate their traffic at. It's just a matter of time.
That's reason enough. It's sometimes no deeper than that, and that's just the reality of the internet we have.
Security is always the opposite of convenience, and striking a balance is what we have to do.
I'm not saying anyone's wrong in complaining about this, by the way. But, our inconvenience is often the only trolls are after.
What makes you think they haven't? Means of exploiting vulnerabilities in security evolve in the same way that security mitigations do. Square could have the best security money could buy, and there'd still be someone out there trying to figure out how to break through just for the simple joy of doing it. That's even assuming a direct confrontation between SE and their hacker, not even accounting for 3rd party infrastructure which SE has no control over. I'm here with a Cybersecurity degree to tell you that's simple the nature of the beast that is internet security. They can only "resolve" the attack in a more permanent fashion once they figure out exactly how the attack is occurring, in the same way doctors can only cure a disease once they figure out exactly how it's making you sick.
People should be a little more reasonable about this. It's not Square's fault, yet there are a few too many people in this thread trying to blame them as if they aren't doing enough. I understand it's inconvenient and frustrating as a player but trust me, y'all, this is something that's affecting their bottom line. They are absolutely doing something about it as quickly as they can.
Last edited by littlehobbit13; 05-14-2024 at 05:32 AM.
Almost one week of dc here and there isn’t really enough for me to be concerned.. if this was happening before expansion maybe but at the moment I’m sort of glad it’s happening but it will then make future attacks less effective if they can find and plug what vulnerabilities are causing this. Like you said doesn’t matter how good your security is… people will get through if they try hard enough… also when you have companies like Amazon and google who have far greater spending and server infrastructure crumble to these it really puts into light how arm chair dev some users are… also probably read your ToS I doubt they have to compensate anyone for this sort of scenario cause it’s not something cause by them it’s an outside issue lol. I do hope it gets resolved soon but for now plenty of games to play lolWhat makes you think they haven't? Means of exploiting vulnerabilities in security evolve in the same way that security mitigations do. Square could have the best security money could buy, and there'd still be someone out there trying to figure out how to break through just for the simple joy of doing it. That's even assuming a direct confrontation between SE and their hacker, not even accounting for 3rd party infrastructure which SE has no control over. I'm here with a Cybersecurity degree to tell you that's simple the nature of the beast that is internet security. They can only "resolve" the attack in a more permanent fashion once they figure out exactly how the attack is occurring, in the same way doctors can only cure a disease once they figure out exactly how it's making you sick.
People should be a little more reasonable about this. It's not Square's fault, yet there are a few too many people in this thread trying to blame them as if they aren't doing enough. I understand it's inconvenient and frustrating as a player but trust me, y'all, this is something that's affecting their bottom line. They are absolutely doing something about it as quickly as they can.
Back in 2021 when EW launched and when the players basically unintentionally DDOS the server without any outside attacker just by too many people liked to play the game at the same time. We also saw many of the same error numbers we see now.
We got a detailed opinion after some days from SE, even if the Devs shrugged their shoulders back then for finding reasons for some of the errors, e.g. for 90002.
https://eu.finalfantasyxiv.com/lodes...273777b15e8ec/
We never heard again from the Devs regarding those errors, so it can be assumed they never found the underlying issue (either something in their Server-Hardware or bad implemented network protocol in their game) and what ever it was, was still slumber inside and maybe the attackers now just found a way to exploit that latent issue.
I just hope they found the underlying issue and then give us then some more detailed information like they did in 2021.
And another point, since it seams that NA and OCE experiences less issues as EU and JP, that could be related that NA got in 2023 new upgraded server hardware. All regions had a full day of maintenance back then just for NA.
https://na.finalfantasyxiv.com/lodes...b07b3650f15d24
I never heard something similar happen for EU or JP (but OCE was already new datacenter from 2022). So EU and JP seems to use still older hardware and this makes them maybe more vulnerable then NA or OCE to current DDOS attacks.
Error 90002 occurs when your system closes the connection to the game, because it assumes it's dead. This is the most common disconnection error because usually your system calls it quits before the server does.Back in 2021 when EW launched and when the players basically unintentionally DDOS the server without any outside attacker just by too many people liked to play the game at the same time. We also saw many of the same error numbers we see now.
We got a detailed opinion after some days from SE, even if the Devs shrugged their shoulders back then for finding reasons for some of the errors, e.g. for 90002.
90006 happens when the server closes the connection because it's given up trying to communicate with you, usually due to excessive packet loss.
2002 happens when you are trying to connect to the lobby server but the lobby does not respond in time.
Those error codes are nothing special, they are just generic HTTP/TCP etc. status codes and flags that SE has chosen to obfuscate with a numerical code.
Last edited by Sove92; 05-15-2024 at 02:01 AM.
This.Error 90002 occurs when your system closes the connection to the game, because it assumes it's dead. This is the most common disconnection error because usually your system calls it quits before the server does.
90006 happens when the server closes the connection because it's given up trying to communicate with you, usually due to excessive packet loss.
2002 happens when you are trying to connect to the lobby server but the lobby does not respond in time.
Those error codes are nothing special, they are just generic HTTP/TCP etc. status codes and flags that SE has chosen to obfuscate with a numerical code.
People are acting like the devs are just brushing it off and not taking it seriously but we legit know the answers to all these error codes. On top of that, the devs don't OWE any player information about their daily operations and what specifically they're doing to address any problems. It's cool that they try to keep us informed, but we need to not let the frustration over this inconvenience transform into some kind of entitlement to their business operations information.
Oh 100%. We're gonna be our own unintentional DDoS when DT drops, we don't need a malicious one happening on top of that. More than happy to have this be happening now so they can find the holes and plug them up during a content lull with nothing major at stake. I'm sorry you missed a rare fish, I'm sorry it interrupted an craft and you lost mats, but better that than millions of players not being able to do major content like MSQ.
Last edited by littlehobbit13; 05-15-2024 at 03:21 AM.
This both correct and incorrect. As paying Customers we do have the right to know what is going on when the service are paying for do not work and the company do have to go out and inform on what is going on and what they are doing to combat the issue (In broad strokes and nothing that would tip they hand to the other side of cause) We are entitled to know a few things. likeOn top of that, the devs don't OWE any player information about their daily operations and what specifically they're doing to address any problems. It's cool that they try to keep us informed, but we need to not let the frustration over this inconvenience transform into some kind of entitlement to their business operations information.
1, Was the attack aimed at Square Enix's servers or were it against the ISP.
2, Were they able to fight it down (again in broad terms) or did the attack stop on the end of the attacker.
3, Are they going to offer compensation (as required by Directive (EU) 2019/770 Digital contract rules and yes THIS law do count for those of us whom live in the EU even if SQ is not based in the EU)
Now I am not going to jump on the band wagon and rave and rant at SQ but I do think they communication during this have been beyond horrendous because if you go and look at ALL the news posts you will see it's the same one each time just copy pasted with the date edited we as paying costumers are entitled to know what is going one as stated above.
Last edited by Valoria3; 05-15-2024 at 04:54 AM.
|
![]() |
![]() |
![]() |
|
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.