Best served with cold steel.

Adelaide3 you forgot to add the your message was sponsor by FINAL FANTASY XIV STORMBLOOD OUT ON JUNE 20 PREODER YOUR COPY AT GAMESTOP !

can you please just make a queue... that way pplz dont have to spam it and they can get in.. in order when they get there. be better than just keep geting kicked out

It has been 24 hour and this is HUGE content block. I'm disappointed it was adressed or fixed, to say the least.

At this rate I honestly wouldn't be surprised if this isn't fixed till monday.

Honestly at this point, I'd take outright skipping the instance. Like, just get rid of it entirely until SE can fix the issues.

just let us skip the quests

They are willingly letting us bang our heads on their instance servers for disgusting lengths of time, while in that time I have not seen a single person leave, no one with Duty status; all while posting nothing but vague messages that they "Are trying their hardest" to resolve issues while I don't even think the effort im puting in has any chance of bearing fruit.... The only that that is resonating from SE right now is that they don't care.

The best thing they can do is take the servers down till all these issues get fixed. This has already been a botched early release. Cut your losses, take your time to make the game playable before every single person who skipped through the whole expansion gets to 70 before 95% of the player base makes it past their first duty.

Funny point: I am now having the game auto switch-off when I TP to this area. Great...

"wait and try again at a later time", how long exactly should we wait? How many times should we try again? Be real with us Yoshi

My point exactly... try when then???

It is incredible that SE doesn't care about customers that are paying a monthly fee... that bought a new product.
The answer shouldn't be "Go do something else", I did that yesterday and today I still can't get past this quest.
The answer shouldn't be "Go do other things in game" because the reason I bought this expansion was to play it not stand like a zombie in front of an NPC trying to complete a quest.
There must be ways to claim this, my money back perhaps, this is an expansion I can't play at the moment and I keep paying monthly for this?

If the game is having this much trouble on Early Access, I don't wanna think about when it's officially released.

And well, basically Yoshida said "our servers can't handle this". If they can't handle, it's pointless to say "we're working around the clock", because you're probably not. Structure-wise, you can't do anything unless limiting access (which you've already done).

And by doing that, the struggle to deal with those issues was passed along to the players, whom you know for sure they will keep spamming the @$%& of Raubahn for a chance to get in. You did that because you know some of us are grateful for Stormblood and we wanted to play so bad we'll do anything. :)

Filling up players with hope like that is cruel. We help FFXIV to be a great game, so have more respect for us. Just take down the servers, make it a que or whatever, but figure this out. Letting us bash into a wall like that ... is just shameful.

This is a major content roadblock - most people will not be able to access the new areas without getting past this instance, and we should not have to either sit around hoping we'll get lucky on Raubahn Clicker 2017 or go level SAM/RDM/main classes just because we literally cannot proceed into new MSQ and zones.

SE, if you managed to fix this on JP servers - which I'm 90% sure have at least one or two "big" servers a la Gilga/Balmung - then why can't you fix it on NA yet? This is actually hindering a lot of people's gameplay during Early Access, and it's really not acceptable whatsoever.

Do a /sea in The Fringes right now -- I promise you will not see a single person with an "In Duty" icon no matter what server you're on.

There is no point camping this quest right now. The bottleneck is way too tight for the amount of people to make it through, and even if/when they do, the duty is 10-20mins long. Calculate the possible instance capacity * the amount of players hammering, then factor in all the other duties like dungeons, PVP, trials, job quests, raids, and then the people who actually get in and fail and come back to retry.... these are disgustingly unbeatable odds...

Quote:

---

Originally Posted by Nekodar

Just shut down the servers, change the battles into fates, start up again and let people actually do the content.

---

That's... not a bad idea actually. But I don't know how difficult it would be to recode this as a fate

Honestly at this point I agree the solo instances need to be queue based. I'm a patient person when it comes to launch days and the days that follow. I've been through most of the WoW expansion launches and they were by far a million times worse than this.

Over 24 hours of being gated out. My patience has gone out the window. I have done exactly what was recommended.....leave and come back. Still nothing. Remove these blasted instances and let us go on!!!!!

Make the solo duties queue based or something.

They knew how many people signed up for early access yet they couldn't preview this? It's a MAJOR content block. And saying to be patient and keep clicking, clicking, click, skip cutscene, and do again is not an acceptable answer

Diablos was down to this in all 3 instances earlier
http://i.imgur.com/P1qa3J7.jpg
And there was still nobody getting in

yeah i have been trying to do this content since 10 am yesterday and i still cant do it shut the server down and add more Relief servers to handle the load.

This is so fusterating

I see another update on the lodestone that talks about the server congestion, yet says nothing about this instance battle block.
How about you update us on what's going on, on at least an hourly basis?

I dont normally complain, but this is just absolute garbage. I have been through server crashes, broken fates, broken instances, etc but this is trash. The game has been up for 30.5 hours now. I have been gated since hour 2. I had so much fun in those 2 hours going out and questing with my fiance, seeing the new zones and then stuck. I took Friday and Monday off to have fun and play the game, I cleared my schedule. Yoshi says to take a break and try again later and we are working on it. So I did. I tried again a couple of hours later, and a couple of hours after that. Saw the post about letting more people through and thought YAY ITS TIME! Nope, still completely blocked out. I havent even gotten to Pip yet. And if I do it wont matter because i will have to wait on my fiance to get through.I highly suspect that it was entirely intentional because they didnt want people to clear any time soon to stretch out content. Either way something needs to be done.

Servers are up, but we are locked out of the majority of the new content... was here at moment of launch, still unable to progress past that one point -_-

This blows, what am I suppose to do? Get to lvl 70 before I even finish a lvl 61 MSQ, this is crap.

Just shut down the servers and implement a Duty Queue for the quest.

It's all you need to do. Then you can funnel us in as quickly or slowly as you want because then we don't have to stress and beat against the instance server to try and get in.

SE, there is no point to Early Access if no one can even progress without spending hours upon hours spam clicking Raubahn/Pippin/what have you. It'd be a far better idea to shut the entire thing down until you can fix this problem across all data centers. Not just EU and JP.

Shut. It. Down.

Amazingly, it is still broken and no real measure taken by Square.

Never forget Raubahn's Line (Savage)

https://www.youtube.com/watch?v=h1x7UPkB338

Well... If JP has been fixed, nothing more needs to be done in the eyes of SE.
As long as JP works, screw the rest.

Quote:

---

Originally Posted by Nekodar

Well... If JP has been fixed, nothing more needs to be done in the eyes of SE.
As long as JP works, screw the rest.

---

normally I would shoot that down but I am feeling pretty negative by this point =/

What's the latest official update on the situation?

Quote:

---

Originally Posted by Theodric

What's the latest official update on the situation?

---

There hasn't been anything new since last night about twelve hours ago. Link.

Quote:

---

Originally Posted by Theodric

What's the latest official update on the situation?

---

No update since morning (counting as EU morning).

The current plan remains the same as yesterday:

http://i.imgur.com/T8zIIMx.jpg

Hahahahaha. That's awesome.

Quote:

---

Originally Posted by Naria

There hasn't been anything new since last night about twelve hours ago. Link.

---

Quote:

---

Originally Posted by Nekodar

No update since morning (counting as EU morning).

---

Ah, thanks. That's disappointing. I guess I'll just continue leveling SAM. I intended to get PLD to 70 first but if I end up getting SAM to 60 before I'm able to advance in the MSQ's then I might as well just continue from there...in which case there will be one less tank queueing up for duties when I get past the bottleneck.

:p

At least there's no Error 1017, 2002, 90000 this year. Login seems to work just fine, so you can at least go do something else. In HW you couldn't even login sometimes.

Sometimes the queue suddenly decides to get stuck on a number for a while, but it works.

Quote:

---

Originally Posted by Nekodar

Well... If JP has been fixed, nothing more needs to be done in the eyes of SE.
As long as JP works, screw the rest.

---

JP servers are fixed of this problem?

Quote:

---

Originally Posted by Theodric

Ah, thanks. That's disappointing. I guess I'll just continue leveling SAM. I intended to get PLD to 70 first but if I end up getting SAM to 60 before I'm able to advance in the MSQ's then I might as well just continue from there...in which case there will be one less tank queueing up for duties when I get past the bottleneck.

:p

---

Same. I was actually joking about this with my fiance earlier that at this rate I'd end up taking SAM though the MSQ instead of AST.

Quote:

---

Originally Posted by MiruWest

JP servers are fixed of this problem?

---

nope even JP servers are still effected