I have been playing MMOs since 1999 - The original EQ. I don't recall ever experiencing an expansion release without major problems - from any company.
I have been playing MMOs since 1999 - The original EQ. I don't recall ever experiencing an expansion release without major problems - from any company.
SE knew ahead of time on how many players to anticipate logging in. All they had to do was look at the number of pre-orders and assume all of them would attempt to log in sometime today. If they knew they couldn't handle it then they should have restricted the number of early access. Of course you know it will only get worse with GA on the 20th.
I think the miscalculation was having this instance be before the first 60+ dungeon. That would have slowed people down a bit, as they farmed out that dungeon's gear. And people are more willing to take a break after a dungeon or a MSQ instance. Prior to this quest, it was all really easy. This was going to be the first serious challenge of the expansion.
+1Well, they got rid of foresight.
that was funny
I've wasted half my day-off spam-clicking Raubahn... GG SE.
This problem is common to any MMO. Devs tweak their servers around the average traffic the game has most of the time, current numbers are something extraordinary that won't last and from a business perspective is a waste of money/resources to build server only needed during the first few weeks. This won't change and players have three options:
- Don't support this.
- Wait a month or so to join the game.
- Deal with it.
At least for EU login server did crash and long ques for popular servers. No idea about GW2 expansion but the hype for that game really died so is no wonder.
Last edited by Driavna; 06-17-2017 at 03:38 AM.
"I have a great idea! What if everyone could do the story whenever they wanted?"
"That's stupid. Why don't we put an instance at the very beginning, but then give that instance limited slots?"
"But we know everyone is going to be logging on at the same time...so why would we do this?"
"Because like...these instanced fights are always so much fun. This time they get to a slightly different looking magitek thing!"
"Oh, well that changes everything! Why didn't you say so sooner!"
![]()
This is only partly a server resource problem. It's also a design problem. When the first real 'fight' of the storyline is a solo instance a handful of missions in, you're guaranteeing the worst possible bottleneck. If they'd thrown in a dungeon (or preferably two) first, it would have gone over a lot better, even with the same server resources. They knew this, and ignored it.This problem is common to any MMO. Devs tweak their servers around the average traffic the game has most of the time, current numbers are something extraordinary that won't last and from a business perspective is a waste of money/resources to build server only needed during the first few weeks. This won't change and players have three options:
- Don't support this.
- Wait a month or so to join the game.
- Deal with it.
And people just letting it slide as "eh, always happens" aren't helping the problem at all. Companies need to face the wrath of their customers for incompetent launches, or things will never improve.
d/ced again now a 3115 queue, What did the server upgrade do now??? did it really do anything ???
|
![]() |
![]() |
![]() |
|
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.