So what was the point of the server upgrades when I can't continue the MSQ?

It will not let me enter an instanced solo MSQ mission because too many people. Wasn't the upgrade made to handle this stuff better? So we got no upgrade and larger ping?

Quote:

---

Originally Posted by Hamada

It will not let me enter an instanced solo MSQ mission because too many people. Wasn't the upgrade made to handle this stuff better? So we got no upgrade and larger ping?

---

It's allow you to create your own topic to complain!

yeah what a glorious server upgrade this ended up being, 9 hours in and i still cant do this MSQ, why the hell did i even bother logging on for this nonsense, server issues i get, bugs i get, but this? this colossal god damn oversight that SE seems to thing is entirely acceptable? on what planet is this acceptable?

Quote:

---

Originally Posted by Driavna

It's allow you to create your own topic to complain!

---

I think everyone is justified to complain in this case.

Suggestions.

Make a new Duty Finder options, even if it's temporary, "MSQ Duty" -queues you for the current solo instance you are up to in the MSQ- or have the NPC comment when you proceed that the server is facing heavy traffic atm and you need to reserve a spot for the instance.

Since the solo instances are lacking that, a lot of data is being wasted just sending information to see if a spot is open only to be denied entry because it isn't. You could reduce the stress of the servers in that manner if people could just reserve a spot at least, since it is a bit misguided to suggest players should wait until someone gets out because. . . how will we know when someone is out? Without an indiication all people can do is wait a minute try, spam a few seconds, wait, try again. I do hope they are working on a means to remedy the situation so that the server can take more stress, time will tell though.

Another though I had was turning these instances into solo FATEs. Much like how there are solo instances which we can enter like an inn or The Rising Stones, you just create a diorama of where the fight is going to take place. Send off player to that solo instance, have the story take place there with the Cutscene taking place that then moves into the fight. My logic is that this could be another way of doing solo instances that doesn't rely on having to create a seperate area for it but rather work it like Squadron barracks, inn and the Rising Stone.

a video game is having performance issues immediately following a giant patch during early access of that patch that incidentally brought a giant wave activity so much so I've seen people who weren't around for almost a year? say it isn't so!

Now that I crashed there "this world is currently full players in queue 745"

I ask again what did the server upgrade really do for us? What was the point of the cost and 48 hour downtime when the servers STILL can't handle the game?

You can give SE all the server resources on the planet; it still won't help them anticipate basic problems like this. This dev team is tremendously boneheaded when it comes to matters of game balance, content abuse, and server stress accommodations.

Quote:

---

Originally Posted by Jeibird

a video game is having performance issues immediately following a giant patch during early access of that patch that incidentally brought a giant wave activity so much so I've seen people who weren't around for almost a year? say it isn't so!

---

I'm sorry but NO. SE shouldn't get a free pass for this. Any idiot could have told them there would be issues with the instance servers near launch time. The obvious solution to this is to not make such an early f*cking storyline quest gated by an Instance, especially a solo one.

You put more distance between the launch and the storyline so that the flow is lessened; you make the initial instances group-based so that there are fewer instances created; and you allocate temporary extra resources.

SE did none of these things. They walked face-first into an obvious problem like complete amateurs. This is a company with as much MMO experience as any company in the industry. It is not wrong to expect them to foresee things like this and prepare accordingly.

While you can say it was an oversight, it's a really bad one. They used this mechanic in 3.55 with no problems because not everybody hit it at the same time. This time, it's at the beginning of the MSQ and everybody hit it at once. 300,000 players hitting the same instance solo.... well, you do the math.

Quote:

---

Originally Posted by Vhailor

SE did none of these things. They walked face-first into an obvious problem like complete amateurs. This is a company with as much MMO experience as any company in the industry. It is not wrong to expect them to foresee things like this and prepare accordingly.

---

Well, they got rid of foresight.

http://www.reactiongifs.us/wp-conten...of_misfits.gif

I have been playing MMOs since 1999 - The original EQ. I don't recall ever experiencing an expansion release without major problems - from any company.

Quote:

---

Originally Posted by Jeibird

a video game is having performance issues immediately following a giant patch during early access of that patch that incidentally brought a giant wave activity so much so I've seen people who weren't around for almost a year? say it isn't so!

---

SE knew ahead of time on how many players to anticipate logging in. All they had to do was look at the number of pre-orders and assume all of them would attempt to log in sometime today. If they knew they couldn't handle it then they should have restricted the number of early access. Of course you know it will only get worse with GA on the 20th.

I think the miscalculation was having this instance be before the first 60+ dungeon. That would have slowed people down a bit, as they farmed out that dungeon's gear. And people are more willing to take a break after a dungeon or a MSQ instance. Prior to this quest, it was all really easy. This was going to be the first serious challenge of the expansion.

Quote:

---

Originally Posted by _Babble_

I have been playing MMOs since 1999 - The original EQ. I don't recall ever experiencing an expansion release without major problems - from any company.

---

WoW Legion, GW2 HoT.

Quote:

---

Originally Posted by Genaxx

Quote:

---

Originally Posted by Vhailor

SE did none of these things. They walked face-first into an obvious problem like complete amateurs. This is a company with as much MMO experience as any company in the industry. It is not wrong to expect them to foresee things like this and prepare accordingly.

---

Well, they got rid of foresight.

http://www.reactiongifs.us/wp-conten...of_misfits.gif

---

+1
that was funny

I've wasted half my day-off spam-clicking Raubahn... GG SE.

Quote:

---

Originally Posted by Vhailor

...

---

This problem is common to any MMO. Devs tweak their servers around the average traffic the game has most of the time, current numbers are something extraordinary that won't last and from a business perspective is a waste of money/resources to build server only needed during the first few weeks. This won't change and players have three options:

- Don't support this.

- Wait a month or so to join the game.

- Deal with it.

Quote:

---

Originally Posted by alimdia

WoW Legion, GW2 HoT.

---

At least for EU login server did crash and long ques for popular servers. No idea about GW2 expansion but the hype for that game really died so is no wonder.

"I have a great idea! What if everyone could do the story whenever they wanted?"
"That's stupid. Why don't we put an instance at the very beginning, but then give that instance limited slots?"
"But we know everyone is going to be logging on at the same time...so why would we do this?"
"Because like...these instanced fights are always so much fun. This time they get to a slightly different looking magitek thing!"
"Oh, well that changes everything! Why didn't you say so sooner!"

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

Quote:

---

Originally Posted by Driavna

This problem is common to any MMO. Devs tweak their servers around the average traffic the game has most of the time, current numbers are something extraordinary that won't last and from a business perspective is a waste of money/resources to build server only needed during the first few weeks. This won't change and players have three options:

- Don't support this.

- Wait a month or so to join the game.

- Deal with it.

---

This is only partly a server resource problem. It's also a design problem. When the first real 'fight' of the storyline is a solo instance a handful of missions in, you're guaranteeing the worst possible bottleneck. If they'd thrown in a dungeon (or preferably two) first, it would have gone over a lot better, even with the same server resources. They knew this, and ignored it.

And people just letting it slide as "eh, always happens" aren't helping the problem at all. Companies need to face the wrath of their customers for incompetent launches, or things will never improve.

d/ced again now a 3115 queue, What did the server upgrade do now??? did it really do anything ???

Quote:

---

Originally Posted by alimdia

WoW Legion, GW2 HoT.

---

That's one thing I will say about WoW, I played Legion for most of 3 days from the minute the servers went up without much of any issues other than some bugged mobs. Gotta give Blizzard credit that launch was as close to flawless as I've seen.

I mean yea this is kind of a silly and big oversight but I was surprised how well things were running up to that point - granted peak hours haven't hit yet.

Quote:

---

Originally Posted by alimdia

WoW Legion, GW2 HoT.

---

Didn't play GW2 but Legion was the first and only wow expansion I know of that was able to go smoothly. Other WoW launches were disasters. I remember in Wrath, I got stuck on a boat over to northrend and had to call a gm to get me unstuck it was that bad.

This is XIV's second expansion, I'm sure they'll figure it out sooner or later, but look how long it took even WoW

Quote:

---

Originally Posted by _Babble_

I have been playing MMOs since 1999 - The original EQ. I don't recall ever experiencing an expansion release without major problems - from any company.

---

I have played many as well: EQ1, WoW, Rift, Wildstar, this one, etc and I agree having major issues is pretty common. It doesn't mean it has to be acceptable though especially one that has affected people all day, we are going on 11 hours of servers being up.

What server did you play on in EQ1?

When are you people going to learn that "Early Access" is corporate marketing speak for "Stress Test"?

Quote:

---

Originally Posted by Jeibird

a video game is having performance issues immediately following a giant patch during early access of that patch that incidentally brought a giant wave activity so much so I've seen people who weren't around for almost a year? say it isn't so!

---

Is this an excuse for a poor implementation of game play? If it is I hope you are ashamed of yourself. If you design with gates (14 the most gated MMO of all time) you have to take into account the resources you have. They would have been better off with kill 5 butterflies.

Quote:

---

Originally Posted by Sylentmana

When are you people going to learn that "Early Access" is corporate marketing speak for "Stress Test"?

---

True enough but doesn't make it a good practice or the issues anymore acceptable. Especially since several of them that seem to be causing the most strife could have been easily avoided by a little critical thinking. HW I recall having a few issues. Things like getting DC'd from that first dungeon a few times mid run, a few server errors here and there but nothing like this. Since 11:30 I've played for 20 mins and spent the rest of the time waiting in huge queues.

Join 6 million other players....

Please, you can't even handle 1% of that number.

Quote:

---

Originally Posted by Driavna

At least for EU login server did crash and long ques for popular servers. No idea about GW2 expansion but the hype for that game really died so is no wonder.

---

Except for those few mega popular servers the rest went fine.

The way blizzard solved this was to essentially borrow a technique from mega server, thee realms are basically mega servers now.

When you move into a zone and it's too busy a new instance is created therefore reducing the burden on the servers. This worked flawlessly for people on Legion release.

The problem with FF14 is that it uses very poor server organisation.

Edit, turns out they use instances now!

SE really need to get their act together and write proper server code. Sadly the Achilles Heal of this game (2.x+) has always been it's poor, limited server code.

Quote:

---

Originally Posted by Titor

Didn't play GW2 but Legion was the first and only wow expansion I know of that was able to go smoothly. Other WoW launches were disasters. I remember in Wrath, I got stuck on a boat over to northrend and had to call a gm to get me unstuck it was that bad.

This is XIV's second expansion, I'm sure they'll figure it out sooner or later, but look how long it took even WoW

---

Thats interesting. I guess SE should have hired some former WoW employees to learn about the hiccups of previous launches so they could prevent something like this from happening. Heavensward was such a smooth launch that SE might have taken SB launch for granted.

Quote:

---

Originally Posted by Vhailor

Quote:

---

Originally Posted by Driavna

Devs tweak their servers around the average traffic the game has most of the time, current numbers are something extraordinary that won't last and from a business perspective is a waste of money/resources to build server only needed during the first few weeks.

---

This is only partly a server resource problem. It's also a design problem. When the first real 'fight' of the storyline is a solo instance a handful of missions in, you're guaranteeing the worst possible bottleneck. If they'd thrown in a dungeon (or preferably two) first, it would have gone over a lot better, even with the same server resources. They knew this, and ignored it.

---

But it's still an issue about it being the first day. Just as they have to balance their hardware around a more normal level of traffic, they also design their storyline and quest scenarios around having normal traffic. Saying they should have designed the whole progress of the game's main scenario around an issue that'll only be true for a few days is nonsense.

Yes, it sucks the first day. If you can't handle that, then wait a few days to do the MSQ and it won't be an issue.

Quote:

---

Originally Posted by Niwashi

But it's still an issue about it being the first day. Just as they have to balance their hardware around a more normal level of traffic, they also design their storyline and quest scenarios around having normal traffic. Saying they should have designed the whole progress of the game's main scenario around an issue that'll only be true for a few days is nonsense.

---

Really? They should not do the math about what they have and just keep going on like this in the future? I swear the SE apologists are the reason they ended up the way they had over the last 10 years. "Fanbois don't care how we screw up we are SE." How do you explain the other design choices that are resource based like the choice to refresh inventory ever X second and housing being open world. This is a team that doesn't plan for what they have and people like you give them a pass. Sad just sad.

Putting the insurance so early gave no one time to separate and spread out. An incredibly bad oversight and they will do nothing to fix. Have not seen a launch handled this bad since age of Conan. This was 100 percent avoidable.

I'm still gonna wait for the full launch before doing story mode. Till then, PotD and leveling for me~

the thing is this is design, not a bug, theres no excuse for this kind of quest being this early on in the msq if they knew the servers wouldn't be able to handle it

MSQ? I would like to be logged in for more than 5 min without being dc. Oh and maybe to get back in fast instead of getting auto booted mid dungeon then staring at 2500 queue because the game will not let you resume your session.

The problem is that SE had/has no intention of adding enough servers to handle everyone trying to get in today. Many will play out this patch then leave again so it makes no sense to them to waste the money on more servers. Anyone who was around when arr went out of beta knows how this goes.

from a 3k queue
http://i.imgur.com/qaP09q4.png?1
End my suffering.

Quote:

---

Originally Posted by Hamada

It will not let me enter an instanced solo MSQ mission because too many people. Wasn't the upgrade made to handle this stuff better? So we got no upgrade and larger ping?

---

Eh it was an upgrade. All numbers went up. Queue times went up, pings went up, frustration went up. It's an upgrade.

I lost my perfect ping for servers that are just as bad.

Whats the point of early access if we cant play at all due to the instance limit blocking the MSQ at the very start? Steps of Faith part 2... or would that be part 3?