again, servers issues are fine, the issue is the bad design that caused them.
Printable View
I got lucky and done this quest in the morning. Just passed susanoo boss.
Yes, MMO launches are notoriously buggy. There are often disconnects and errors for a few hours.
It's nearing 19 hours of having ONE major issue. They've provided no fixes, no useful advice. I know e3 just happened, I know it's going into the weekend. But they scheduled this, and if there aren't multiple programmers with their asses in the fire right now then SE is failing miserably at being professional.
I can't even get to Cold Steel. I got DC'd on the first MSQ instance ("Fly Free My Pretty", or something to that effect) and have spent the last hour trying to simply log back in. 90002 message every time.
Oh well...about what I expected.
It's time SE admits their mistake, remove the instance fight (Yea it sucks to do this) and let player keep moving forward.
I've been trying to get this stupid MSQ done for almost 19 hours, now. Meh. Tech issues happen. Terrible design flaw to require an instance MSQ quest this early on. But the silent treatment sucks most. They failed to admit that this is a problem and went out of their way to say, not just once but 3 times now, that things are working as intended. And since less than 1% of players have been able to clear this bottleneck, I must conclude that their intention is that this quest is not doable.
I've read Yoshi P's statement, and it reads to me: "We're doing nothing, and your patience will solve this so we don't have to in a week when nobody needs to do this quest any more. In the mean time, please spam click on the one-armed slot machine to see if you win the jackpot of being able to get into the instance long enough to get disconnected half way through your MSQ and have to try again."
A bit of PR would go a long way, even if the tech isn't able to resolve this, Square.
this is really annoying. i really hope they fix this by tomorrow, because if they dont, they should be giving us our money back. This is not early access!!!
They should do what WoW does for their scenarios and have a queue for solo instances.
Not to be contrarian, but the HW issue was different - in HW there were some people (like me!) who couldn't log in AT ALL. Queues just weren't happening. That's why you get people who say HW launched fine and others who say HW was a pile of cactuar droppings.
Here, this issue could have been avoided at the design level (allow access to more areas beyond that quest so that at least there's getting aether currents, etc. while people wait) and when they moved the Data Center, where they could have added additional hardware.
Well I think Goblin crashed...
http://i.imgur.com/qhFjiGI.png
Creeping up on almost 24 hours and it's still broke... :(
Had that one burst of people getting in at 8:00PM EST and then nothing again since. The NPC with another individual instance after this quest is utterly deserted on Cactuar in all three zones. Why isn't this quest prioritized yet? Supposedly, the JP servers already had this issue fixed.
There were two updates from Yoshida last night, who is working around the clock with the development team to address the issues at hand. You can also find the updates here and here on the Lodestone. I'll quote both of the updates in this and the following reply.
Quote:
FFXIV Producer and Director Yoshida here.
I would like to explain the current congestion issue regarding instanced battle content, including the Stormblood main scenario quest “Best Served with Cold Steel,” due to the Duty Finder crashes at the start of early access.
As announced earlier, there are a huge number of players currently playing Stormblood, and as a result, the servers continue to experience a large amount of stress. For this reason, we are currently limiting the number of players that can enter instanced content so that it does not lead to major server crashes.
However, this has caused massive congestion to enter instanced content and I would like to sincerely apologise for this.
If you are unable to enter instanced battle content, we ask you to please wait and try again at a later time. We understand that this unfairly places the burden on our players, but we require more time until the issue can be resolved. We continue to work on measures to address this issue and will follow up once we have an update.
Again, we sincerely apologise for this level of congestion occurring during early access when many of our players are the most excited to play.
Everyone on the team will continue to put in our full effort to ensure an enjoyable gaming experience, and I would like to thank you for your continued support.
The second update from Yoshida. It can also be found here.
Quote:
FFXIV Producer and Director Yoshida here.
This is a follow-up regarding difficulty in accessing certain instanced battle content.
The development team has changed the process for dealing with this issue so that as many players as possible can be moved to instanced areas for certain main quests and instanced battles.
As a result, 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.
Currently, the development team is making detailed adjustments by adjusting the speed at which players are transferred to instances on each World so that areas do not continue to go down and to ensure that all players can continue to play as comfortably as possible.
Although these measures were taken to help alleviate the difficulty in transitioning to instances, we apologise about zones going down as a result.
Congestion in the “Rhalgr's Reach” area is especially intense, so to prevent zones from continuously going down, we are carefully controlling the logins to each World and transitions to the Rhalgr's Reach zone. Due to this, it will take some time to log into any of the Worlds.
Everyone on the team will continue to put in our full effort to ensure everyone can enjoy early access.
Yeah. To be honest, though, this has now hit 24 hours officially. It's into the starting into the second day. It might as well not be up to this scale if all we can ultimately do is tour 3 areas (Fringes, Reach and Peaks), level up two new jobs and test drive the changed combat. At this point, the media tour people have seen more of the game than the players.
EDIT: Meep. D: That ninja post. >_<
EDITEDIT: When I say scale, I mean have ALL roulettes open, PVP, Palace of the Dead, Diadem, etc. ;-; Close something to help divert resources if it'd actually help.
I'm here for the memes
also tfw I decide to sleep a little longer thinking it'll be long fixed by the time I wake up rip
Welp, you've heard it boys. Back to the pile!
Looks like the level cap is 61 am I right guys?
http://68.media.tumblr.com/9529a2288...6hyjo1_250.png
right?
So I waited and came back at a later time like they suggested. I even woke up at 4am to come on during low traffic... Still doesn't work.
This is an unfortunate situation but I can only imagine how the development team and Yoshi feels right now so I will wait as long as it takes.
This game is worth it and waiting a little extra isn't really a problem, even though I was hoping that I could progress that awesome story when I got off my night shift.
Still unable to enter. Now on my server we have two lovely people dragging over the Leshy mob to those of us that are trying to get in to kill us I'm assuming.
You should be a little more humble. Stormblood is going to be one of the best expansion releases for a mmorpg in a really long time and this is coming from someone who opted out of Heavensward for it being a bad expansion. What is a day or two wait going to do to you? Nothing at all and that wait will soon be replaced by countless hours of playing an awesome expansion to a mmorpg.
Well... Since you ask... I have only a few days more that I'll be able to play because I'm going to be away for 3 weeks during which I won't be able to play at all.
I'd like to do as much as I can in that time.
It's not the first time SE screws up like this with FFXIV. And every time they lose players permanently.
I was willing to be patient since it was day 1, but there's no significant change after more than 24 hours? The messages from Yoshi-P don't really help.
That's strange, this morning (so 8 hours go or so) I heard from multiple people on my server that it seemed to be fixed? It took me an hour and 40 minutes to get into Raubahn's, but all solo instances after that were fine except for one I DC'd out of.
I think only naive and inexperienced MMO players expect a new expansion launch to go off without a hitch on day 1. However, we can't tell how "awesome" or "amazing" this expac is supposed to be because of poor design decisions on multiple levels.
I feel bad for the engineers who probably saw this coming, said something about it, and were shut down by management. I have no sympathy for people who write off preventing major issues like this and place the burden of dealing with the fall-out on the same people who wanted to prevent it in the first place.
At this point either give us an auto-clear of the instance (it's not a major part of the story- it's taking out some stupid mechs) or tell us what you're working on. Having so many people unable to move on over 24 hours after launch is unacceptable.
It's a good thing Shirogane housing plots aren't available as this bottleneck seems to be getting worse with more ppl logging in for the weekend. Otherwise, the complaints would likely be ten fold.
I'll say it again it's erly acsess it's basicly a glorified stress test and guess what these things happen it happens in all mmos it hapens in wow guild wars you name it it happens new content like expansions are always like this for the first week or so get over it and let the devs fix the problom
Well I'm stuck in pipin NOW.
U.u