Exactly. This is a problem that will sort itself out in due time. Trying to fix it by fuddling around with the code would just be a waste of resources.Blah. I tried to reply and accidentally lost what I had typed in the clipboard because of that stupid 1000 character limit. *sigh*
But seriously, do you guys think it is THAT easy to modify server hardware, or code new cutscenes? *sigh*
And I'm not white knighting as much as I'm calling people out for reacting entirely unreasonably. And I've not been doing so for "hours". Maybe one hour, max.
You can buy server space online. I believe Amazon sells some - you buy a certain amount, you pay for it while you're using it, and when it's empty you can cancel it. A couple thousand dollars and this could have been avoided completely.
Early access is only three days, and the Complete Edition is selling well. Of COURSE people are going to be upset at now having lost 1/3 of their time before the extra people get added.
Since the particular problem is affecting every world equally and the DF, it's pretty obvious that it is cross realm, so nothing to fix there. The shear number of people repeatedly clicking to get in an instance is most likely acting like a DDoS attack not allowing the machine to respond properly. Do you know what MMOs do to fix DDoS attacks? They apologize and wait for them to stop.They clearly have the ability to already allocate instances. The expected server strain should have been anticipated. Getting into the EA period required a preorder. It isn't like people just randomly bought the game and logged in. They had figures and they had time too. You mean to imply they didn't believe the people who preordered wouldn't play the game?
They could have even just made the instance battle skippable, mark the quest as cleared upon viewing the cutscenes. Plenty of options. You're going about beta testing, but this certainly doesn't feel like it was beta tested in any real regard.
Right, the players are at fault for a low capacity server and shoddy instance handling.Since the particular problem is affecting every world equally and the DF, it's pretty obvious that it is cross realm, so nothing to fix there. The shear number of people repeatedly clicking to get in an instance is most likely acting like a DDoS attack not allowing the machine to respond properly. Do you know what MMOs do to fix DDoS attacks? They apologize and wait for them to stop.
Whether or not people bought the Complete Edition is a non issue. Early access is a bonus to all pre-ordered versions of the game, no matter the edition. Had people needed to pay extra, I could understand it, and if the issues continue into the official release, I'll be voicing my concerns right along with everyone else. But as it stands, for now, this is a universal bonus with no guarantee of full functionality.You can buy server space online. I believe Amazon sells some - you buy a certain amount, you pay for it while you're using it, and when it's empty you can cancel it. A couple thousand dollars and this could have been avoided completely.
Early access is only three days, and the Complete Edition is selling well. Of COURSE people are going to be upset at now having lost 1/3 of their time before the extra people get added.
That works only if your server setup is designed for it from the start. Which is not the case here.
You don't work at SE, or for the people responsible for our servers. How do you know that?
Cross-posted from that other thread; a simple, temporary fix that would allow players to get past the current bottlenecks, disperse the userbase across a wider segment of the servers instead of putting all the stress on one particular point, and should not require an extensive amount of work produced from nothing (as it would take to code a 'queue for solo instances' function) or cost a bunch of money (as expanding raw server power would):
Temporarily flag "Let Fill Your Hearts With Pride" (the quest that follows "Best Served with Cold Steel") to be available as soon as you've completed "Signed, Sealed, and to Be Delivered" (the quest that precedes 'Cold Steel'), so that players can bypass the quest with the instance, and go back to complete 'Cold Steel' later.
Do the same thing with the quest that follows "In Crimson It Began" (the Pipin-triggered instance) so that you can begin it as soon as you complete the quest that precedes 'In Crimson', so that players can bypass 'In Crimson' and move on with the story, and come back to complete the instance later on, once things have calmed down.
Continue to do that with any other early-Stormblood quests that involve solo duties, so that none of them will roadblock the entire player base for no good reason. It's a simple enough solution that it could have been implemented already, and could simply be rolled back as early as the official launch on Tuesday, if the congestion issues at that one particular point in the game have been alleviated by then.
Congestion issues are congestion issues, and although you can make the argument that SE should have seen this particular one coming, nobody is expecting them to have perfect foresight. But there's no justification for being this slow to roll out a temporary fix, when the problems the game is experiencing are so laser-focused onto such a small, easily-bypassed portion of the game.
tomorrow won't be better since so many people need it. The gated 90% of the expansion behind this. Saying "oh well, I'll just wait a month to do this" isn't acceptable.I think the biggest thing they failed to foresee is ridiculous reaction of the playerbase at large. Instead of going "oh well, I'll try again tomorrow", everybody's throwing themselves at the brick wall expecting things to be different the next time. If people'd be more reasonable, more people would get through and this wouldn't be such a huge issue.
Emergency Maintenance'd do one thing. Kick everyone off.
Isn't that what everyone has been arguing they should do?
|
![]() |
![]() |
![]() |
|
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.