It's apparent SE doesn't care that non-JP servers are encountering 2002 issues

[Rinhi]

This doesn't necessarily follow but I can see how some people would get the idea. If you're running a service and a small amount of people on the forums complain about something that only happens in a rare condition (server queues being full for days on end) and your techs say that it's because their net connections are bad (this isn't the sole reason but it DOES contribute and is likely what the team was told) you probably aren't going to react that strongly to it. I don't believe anyone has ever looked as deep as they have in this case, they just went "we hate 2002 errors" to which SE replied "your connection might be/is the problem" and the subject wasn't pursued further because soon after queues would lessen and nobody would care again.

but that's kinda the issue and also happens to other parts of the game; just look at the ping/latency/animation lock topics, how certain jobs are impossible to play for some people due to their high ping - from what I've seen, people have been mentioning this for years and yet, only during this live letter yoship seemed to have been told of this issue, despite people begging for years for a 'fix', so to speak
it feels there's sometimes a massive communication problem between the departments and I don't blame people for thinking that their problems are being ignored because japanese players obviously don't have the same problems
or with a more recent example; the sage icon getting changed just because japanese players don't like it - I'd argue that it wouldn't have happened if NA would've been the ones to make that topic, even with double the likes, though I'd love to be proven wrong at one point in the future about this!

Technically if everyone's connection was perfect there would be no 2002 problem. As far as I can tell from everything everyone has revealed, SE and the users combined, is that every 15 minutes there is a very sensitive reconnect that happens. If your connection drops any part of that connection, the game considers you disconnected. The REACTION to that and followup protocol sucks and is poor coding it seems. However what I can assume happened, was the techs on SE's side all saw the server shooting back "this guys connection is dead, drop him" and assumed the cause was the users (something that's pretty common everywhere: nobody wants it to be their thing breaking). THIS finding was relayed to the "mouthpieces" of the FFXIV team and is what was announced. They were as transparent as they could have been, though maybe not as diligent. It's fair to say it was something that could have been fixed a long time ago, but it also has to be understood that until the perfect storm of problem happens, it wouldn't have been a priority in any company.

fair and I don't necessarily disagree about the communication, but I don't think it was handled as well as it could, though I do think it is not the end users problem if it's the only game that has this issue, as any other kind of queue I've experienced doesn't kick you out if you lose a packet or two, which is a natural occurence

I think any further umbrage thrown their way is just salting wounds and sowing discord.

true, which is why I will refrain from further making comments like that, but I just couldn't not say it considering the sheer amount of people that scream about shortages being the cause when it has nothing to do with it, all because they feel like they have to defend SE at all times, it seems

I think acknowledging that the company is doing the "right" thing with the information it has now and how they made a choice to act on user given information instead of ignoring it and continuing to blame throw is far more important than further shade.

agree

[kejakalope]

To anyone who feels insulted by the free play time, I'll be willing to take your 21 days if you don't want them.

[kejakalope]

or with a more recent example; the sage icon getting changed just because japanese players don't like it - I'd argue that it wouldn't have happened if NA would've been the ones to make that topic, even with double the likes, though I'd love to be proven wrong at one point in the future about this!

You've been proven wrong at various points in the past already. For example, during Stormblood they reverted a bunch of changes to Eureka intended to discourage FATE train style play (because JP didn't play that way and it hadn't been Square's intention) after the NA playerbase rioted and demanded the return of the FATE train.

[Shuuli]

The thing is, if people want change, they need to keep opening actual formal tickets instead of posting on the forum. This is not an official complaint site, this is a forum where people can discuss whatever they want with each other. Which includes complaining. However, this will not change anything. I see posts dating back years on issues, but surely people understand that those are only read by other players here.

I do wonder how many of those people who complain actually opened a real ticket that would help accelerating the solution to their specific problem.

I do like to read drama, so please, keep going on tho

[SnowVix]

soo, it was a software issue and a redditor did a better job than the entire ffxiv team


"kek"

a software issue that was a holdover from before Yoshi-P was even attached to the game, so slow your roll on patting yourself on the back for getting it right

[LittleImp]

a software issue that was a holdover from before Yoshi-P was even attached to the game, so slow your roll on patting yourself on the back for getting it right

Do you genuinely think that inheriting a codebase somehow absolves the dev team of the responsibility of understanding what they've inherited?

Transferring 'ownership' of code like this is an extremely common occurrence, and accomplishing this kind of knowledge-transfer successfully is part of what it means to be a professional developer. What a joke.

[Rinhi]

You've been proven wrong at various points in the past already. For example, during Stormblood they reverted a bunch of changes to Eureka intended to discourage FATE train style play (because JP didn't play that way and it hadn't been Square's intention) after the NA playerbase rioted and demanded the return of the FATE train.

that's great, then! I wasn't playing the game back then so I didn't know about that, so I concede that point

[TwizzlyTwist]

at this point im pretty damn sure yoshi-p has a roulette where the only 2 options are "covid happened" and "legacy code" that he uses when they need to answer for something that should have been fixed 5 years ago

your entire post history looks like a troll account at this point.

[Tanis_Ebonhart]

Do you genuinely think that inheriting a codebase somehow absolves the dev team of the responsibility of understanding what they've inherited?

Transferring 'ownership' of code like this is an extremely common occurrence, and accomplishing this kind of knowledge-transfer successfully is part of what it means to be a professional developer. What a joke.

Thanks for pointing out that you know nothing of coding.

[LittleImp]

Thanks for pointing out that you know nothing of coding.

You'll get better reactions trolling whiteknights friend.