To be fair that was for a very specific internet service provider and not everyone, likely these people couldn't even play.
Not that they can play more than we can, but y'know.
Printable View
To be fair that was for a very specific internet service provider and not everyone, likely these people couldn't even play.
Not that they can play more than we can, but y'know.
I dc out of ANY solo instance now
It's only going to get worse, you know that, right? It's the weekend, and launch is tuesday, when even more people will come to the bottleneck. This is terrible design, something WoW did much better with Legion, letting you go to different zones. Funneling all players to one point like this is just bad design now, especially with a limited instance situation.
A better plan would have put a dungeon before this, so at least there would be that to do, but you can't even go to other zones, because they are all locked behind the MSQ.
I don't know, man. Stormbloods going to be around for a very long time, and this is the very first day of *early access*. If you expected perfection, you set yourself up to be depressed today.
GOING ON 22 HOURS NOW, COOL FIXES SQUARE
I expected to be able to play a nice chunk of the content because I don't get much free time after this weekend. That was the point of Early Access.
You can't deny that locking 95% of the content of your expansion behind this one instance that can't support more than 20 players at the same time and having the instance happen 1 hr into the expansion is good design. It's quite the contrary.
People are being entitled.
And they have every right to be.
We are entitled to content that we were promised. We are entitled to play a game that we are paying for. To asspat SE and say that they've done nothing wrong and somehow the paying customers are the ones that are 'bad people' is the most disgusting thing I've seen prevail on these forums.
Yes, it's Early Access, but as far as I can tell they haven't shown any sign of actually working on a fix. AFAIK their "fix" is to wait until people slowly trickle through their manufactured bottleneck. That is not a fix and it will still be borked on official release, when there really will be no excuse. (there isn't one NOW if you ask me)
The other concerning thing is, this incident is starting to teach a lot of people about how the game is actually programmed. And that should be a really frightening thing for any dev team, especially if people are figuring it out through something like this.
Right now, there's an implication that the game actually treats most instances as equal priority in the server coding. After all, SE apparently limited 'Best Served with Cold Steel' instances so that Duty Finder and the rest of the server wouldn't crash horribly. But the thing is, no SE employee in their right mind would specifically choose THAT instance to limit. And judging from how players are having trouble getting into ANY solo instance, it would appear that perhaps all of the solo instances are sharing the same space.
So think about it a bit further. One would think that with SB release, the servers are getting hammered by bots now too. It's observed that their programming has evolved to the point where, while I was in Leviathan a few months ago, I observed bots doing the MSQ in Central Coerthas. Now, just think of how much of the solo instance space is getting taken up by bots...
On a side note, the revelation that SOLO instances are actually based on the entire DATA CENTER is quite frankly, a potential deal breaker for players looking to transfer off of the overpopulated servers into a lower populated one. What point is there to, say, transfer off of Balmung to Coeurl if Coeurl players are now being DIRECTLY affected by Balmung's overcrowdiness due to how solo instances are programmed? If a Coeurl player manages to get through this duty, everything afterwards would probably one massive ghost town. Their friends, or anyone else in that server for that matter, have little chance of making it through and joining the lucky player.
And another thing: If SE is so concerned about duty finder crashes, let's have a temporary bandaid before this snowballs into ruining EVERYONE'S weekend more than it already has - shut down Palace of the Dead for a week or two, for PoTD isn't necessary to progress in anything else in the game. People will just have to level the old fashioned way via FATE grind.
Palace of the Dead uses resources on the server for its instances, the same as the solo instances. Shutting it down would allow for those resources to be repurposed for the solo instances, increasing the number of solo instances and number of people that would be able to progress through the main story. Palace of the Dead is likely the most popular instance due to how fast it allows DPS players, whom make up the majority of the player base, to level.
A way to see it is to imagine the instance server being a table, with each instance taking up space on the table. Unless there is enough space, an instance can't be placed on the table. By shutting down palace of the dead, you make more space for the solo instances.
That's a price you have to pay, when you are in an overpopulated server. You really may want to reconsider the free transfer option, I realize it isn't what everyone wants but it's there for a reason.
Edit: At least with me, moving to Omega completely cleared all my issues with single instances. I believe other servers in the EU data center like Phoenix had queues too, but I didn't have those issues. Therefore, I think it's safe to assume single instances aren't dealt by the data-center but rather the actual server you're on.
From the last census, I believe it was shown that EU has a smaller population than NA. Instance servers are definitely based on the datacenter as that is how it allows for cross world play. So someone would have to transfer to a less populated datacenter, that includes smaller worlds in the aether datacenter.
Soooo, I did as SE suggested, wait till later and try again. Its 6:09am and i still cant get into this quest, i have been trying since 9am yesterday. SE hes stated "players have become able to transition to instanced areas faster than originally estimated, but at the same time, players are now gathering at certain areas in large numbers, and this is causing the servers go down on some Worlds as a result". Well Goblin is neither crashing nor letting people in. By my count, and i may be wrong, you have issued 3 statements regarding this problem. Why wont you say more? engage with the players? at least put a message in game?. This is baffling beyond belief.
I'm honestly surprised the german forums aren't complaining. It's the one thing we german speaking people are good at. And being a stickler for the rules. :D
Well, I spent 4 hours waiting in a line that, as it turned out, didn't really do anything. Was it a waste of time? Maybe. But it also was fun, being part of the community. And it's something everyone participating will remember and laugh about in a few days.
But why shut down anything when you can just globally flag the quest as completed and be done?
The issue here is that everyone and their mother is funneled into the MSQ because the MSQ gates everything. You shouldn't shut down parts of the rest of the game (Whether PotD, PvP, Treasure maps or whatever other instances you can think of) to accommodate that, you should realize it was a dumb idea in the first place, remove the temporary roadblock and learn for the future.
I mean, they won't, because they can sell jump potions off that design. They'll just wait until the issue resolves itself. But that's what they "should" do.
Because then the next solo instance becomes the next road block. Shutting down part of the game allows for a larger gate to deal with the congestion which is the underlining issue. Auto completing it for people just makes a new gate as it wouldn't address the problem at its roots.