Best served with cold steel.

It's not surprising to find bugs and errors during early access. You'd be kind of crazy to assume that something wouldn't go wrong because issues happen even on normal patch releases.

A lot frustration comes from the fact something so "game breaking" has happened so early into the main quest and it feels like little is being done about it. Regardless of server congestion, players (paying customers) at least want an illusion that something is being done. Pretty much SE's "fix" is to have you constantly try to get into the instance because things are technically working on their end.

I'd be ok with the servers temporarily being unavailable and then reopening data centers on a schedule since it's a physical limitation causing the problem. I understand that it would suck for anyone who isn't apart of early access, but this problem is only going to get worse throughout the weekend and let's face it...Hell will break lose on Tuesday if this problem still exists.

Can confirm still busted on Brynhildir. Are they even trying to do something about it?

Or... wait, does it work in the Japan servers? I have a mind to say that they gonna take the problem nice and slow for us in NA and maybe EU if Japan is working fine. Yep, I said it, I think they don't very much care for us if their Japan audience is doing fine.

If its also not working on the Japan side then what the heck are you doing, SE?! Get to fixing this!

SE DO SOMETHING
SAY SOMETHING
DON'T JUST SIT AT YOUR COMPUTERS
SHRUG YOUR SHOULDERS
AND GO ON A SMOKE BREAK

Quote:

---

Originally Posted by Erudito

Can confirm still busted on Brynhildir. Are they even trying to do something about it?

Or... wait, does it work in the Japan servers? I have a mind to say that they gonna take the problem nice and slow for us in NA and maybe EU if Japan is working fine. Yep, I said it, I think they don't very much care for us if their Japan audience is doing fine.

If its also not working on the Japan side then what the heck are you doing, SE?! Get to fixing this!

---

No it doesn't work on Japanese servers either.

This has been happening since FFXIV 1.0

About time they at least introduced a queue system so you eventually get in even though you have to wait. Been on this for 7 hours.


And they are launching new servers in EU because of congestion. Why oh why wait until now to action them ? They could have launched them a couple weeks ago and eased the problem for many people.

Quote:

---

Originally Posted by Fenlnir

Yep. Legion and Heart of Thorns launched really well. Really makes me wonder if SE wants people to just not sub anymore.

---

Legion was literally the first time in the life of a thirteen year old MMO run by one of the biggest dev teams with one of the biggest budgets that an expac of WoW didn't have launch issues.

Every. Single. Expac. Before. Legion. Had. Issues. At. Launch. All of them. Without fail. And they weren't minor ones - they were legitimate "game breaking" / player inconvenience issues. The entire Horde storyline in WoD was totally busted from the start and it took them over twelve hours to sort it out completely. So you either had to play Alliance or sit on your hands and wait.

Using Legion as a comparison is ridiculous. Using Heart of Thorns as a comparison is equally so because GW2 isn't nearly as popular as FFXIV or WoW.

Also - nothing SE said on their post was "Deal with it, we're not fixing it." It was literally "We're working as fast as we can - we know this is a problem but until we can get it resolved, this is your best option. We're sorry." That's IT.

Been trying all morning. It's still happening.

Edit:

Hey SE how about getting rid of these stupid solo instances entirely? Turn them all in to those purple circles that spawn monsters.

-Or-

Let us form parties for it.

The jump potions were a mistake. They should of waited til after Early Access to sell those. By selling them on Friday they just created a huge bottleneck for the servers. The reason why HW didn't have these issues and yes I looked back and realized that both paths during the HW MSQ split had solo duties but there weren't any issues like this. However, the reason we may be seeing this bottlneck is from old, new, and current players rushing towards it.

had it just been current players the servers would of handled it, but old players who are returning can just jump and be in SB, new players can do the same, by doing that, the estimates of people in SB become skewed. Which is a shame.

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

It's ARR all over again.

Quote:

---

Originally Posted by Claviusnex

Makes you wonder just what SE paid for with the data center move and server upgrades.

---

The more I think about it, the more I suspect this is a programming error and not a hardware error. Something about the MSQ instance in particular must have a memory leak or poor garbage collection, causing it to consume far more resources than it ought to.