I know, this doesn't need new threads but I feel this would be such a simple and great solution it should be posted in the best way for SE to see it.
I know, this doesn't need new threads but I feel this would be such a simple and great solution it should be posted in the best way for SE to see it.
And honestly, the whole quest isn't even that special..
Does Yoshi believe this will blow over in a day or something?
Wish it was that easy. They would have been able to fix it within the first hour. When is the next solo instance? If they'd just let everyone through, then the problem would return at the next solo instance.
Just disable those instance quests and autocomplete them at the moment. There's too many people and no solution outside of "you're sol, deal with it."
Honestly, I hope they do away with these solo instances in the MSQ. They're fine in the job quests, but this caused a serious cluster f***. Now idk programming and I understand that these things happen during MMO expansions, but I really wish SE was a bit more vocal rather than simply saying "Try again later." As entitled as it sounds, I didn't pay money to wait over a day to get further than 5 quests into the MSQ. At this point, early access should have just been implementing SAM and RDM. That's basically what most people are doing anyway.
This would be the cleanest and quickest solution to the problem, and honestly they should have had a fix pushed onto the live servers within 6-8 hours of Early Access beginning, considering that this has been a problem since literally the first 30-40 minutes.
It's very simple to do: Just change the quest that comes after 'Cold Steel' (and the other Pipin quest that comes afterward) to become available at the same point that 'Cold Steel' does. That's not a complicated change, and it shouldn't take hours (let alone days) to code and implement in-game. That solves the problem of people getting stuck behind the instance quests. without taking those quests away from players who want to do them (that is, 'Cold Steel' would stay active in your quest log until you go back and do it, even if it meant doing the quests out of order).
That's really all that it would take. The servers don't seem to have trouble handling regular group instances, or the overworld zones, or any retainer/marketboard stuff, or anything else. It's just the solo instances that are causing problems. And after those first two instances, the next one doesn't happen until A) you've gone quite a bit farther in the story, and B) is preceded by the first dungeon. A takes care of most of the congestion issues, because players will naturally disperse the farther into the MSQ you get, as they play at different rates (the problem we're facing is that these instances are only a few minutes into the game, so everyone has been hitting them at the same time), and B is a back-up plan that gives players some actual meaty Stormblood MSQ content to play, if they do happen to run into congestion issues.
There's really no excuse for SE to not have responded to an issue of this magnitude with a definitive solution - not some vague "we've adjusted the servers on the back end and now more players should be let in" BS - in the first 24 hours, even if that solution is a temporary one that they have to revert in a week or two. There's no reason to just throw their hands up and go "Welp, we've got a lot of players, what are you gonna do" when the problem is so easily identified and so crippling to the overall play experience.
Solo instances just seem like bad design as a whole. It's bad enough they force people to sit in queue for potentially an hour for a trial.
I agree they need to implement a skip feature/auto complete for the whole quest if say it fails to load 5 times in a row. Talking to a few ppl who did get past it... there are numerous quest just like the first one so unless a fix is done soon it will happen to each of the quest as ppl get through the first/second quest.
The whole expansion is locked out to the majority of players right now, this is 100% unacceptable especially since this is day 2 now and the problem is not even close to being resolved.
I don't see how this problem will sort itself out. Maybe if already half of people made it through and were still stuck. That would mean only half remaining need to get in and it'll just be another day, but the thing is... very few have gotten in after 24 hours. So if things stay like this until everyone makes it through... how long will that approximately take? Don't even want to think about it.
Pretty much. The situation is even more dire if you consider Tuesday is launch and you'll have a whole new set of people to get stuck at the exact same point. I tried at 10pm, 1am, and 4:15am my time yesterday, not counting the rest of the times throughout the day and never could push through. Going by the talk around the quest, almost no one was or those that had may have been there for hours.
PLEASE give us a ETA of when this issue is going to be fixed.
at this point im ready to just pay 20 bucks for a stormblood story skip potion. can grind my way through all the dungeons without getting bottlenecked every 5 quests by some solo duty i don't care about
That would just get everyone Tarupin'ed
This is stupid we had these since ever and never encounter a problem like this before. So come on raise that cap limit and get over with it even if has to make an emergency maintenance, which should had happen already because you don't purposely keep your players stuck at something this necessary to keep going with the quest. This is no a Side quest.
If I recall correctly, this happened in the 2.0 Beta as well. With the very first solo instance too...
Servers were going down at the time as well, so I think most people tend to remember that. There was a large FC on Ultros dedicated to one of the disconnect errors for a time.
Find new story very boring. heavensward main story was much better. They should just get rid of it till they can fix it and let ones get past that part.