FEEDBACK: I don't even want to play anymore (RE your bad launch)

[Freyar]

I am disgusted to the extreme by your treatment of your playerbase and your complete lack of response yesterday. If you cared at all about your player base you would have provided updates and encouragement, not silence.

Sounds like you're the one being inconsiderate.

[Mikhaill]

I like how they are so downright disgusted and not wantin' to play anymore, yet they move
to a new server.

[Moonlite]

you absolutely did not play any mmorpgs if you cannot think of a single mmo who had these issues at the beginning of any launch so i'm going to call you out on that

I am not sure any MMO has ever had this particular problem. This is not a server stability issue. This is a design gate issue. Most MMOs are not gated the way this game is. Even in 11 you could explore 3/4s of an expansion except for the worse one ever CoP. Co-op game might have had this issue though because you are just lobby and instance. So basically 14 is an open world lobby and instance with out the planning.

[ToasterMan]

It's a crying shame that there are so many people on this forum that refuse to put a company like SE to a higher standard, especially after what they've done before.

[Novastarone]

The login queues I get, what i dont get is the absolute idiocy of whoever decided to limit instances in game...so that people got blocked from progression for nearly 3 days. that is not cool and people have a right to be bothered by it. Just as you boot lickers come here and praise the game endlessly, those ragey salt lickers have the same right to come here and give their opinion.

[JMadFour]

People can have any opinion they want, just because you don't like it doesn't mean you need to troll their topics. If you don't like it, shut up and don't post.

no.

people can have any opinion they want, and I can disagree with it. this freedom thing goes both ways, contrary to popular belief.

"trolling" doesn't mean "having the nerve to disagree with my entitled whiny opinion."

don't like it? too bad. my opinion is just as valid as anyone else's.

[Novastarone]

no.

people can have any opinion they want, and I can disagree with it. this freedom thing goes both ways, contrary to popular belief.

"trolling" doesn't mean "having the nerve to disagree with my entitled whiny opinion."

don't like it? too bad. my opinion is just as valid as anyone else's.

Calling someone else a whiny little shite isn't contributing anything. It is in fact rude, harassment and trolling someone elses topic. Please learn etiquette.

[KisaiTenshi]

I am disgusted to the extreme by your treatment of your playerbase and your complete lack of response yesterday. If you cared at all about your player base you would have provided updates and encouragement, not silence.

I'm more disgusted by the playerbase who felt so entitled that they keep spamming the forum with new threads on the same topic. What is the point of this? You're not going to see a forum moderator respond to everyone, no they will either ignore all but the stickied one (the one with the crown icon) or merge the rest.

Customer service is often not permitted to speak or take shots in the dark about what is wrong, hence they have to wait for an actual definitive answer. If they start speculating about what is wrong, and then turn out to be wrong, then people get it into their mind that the company representatives are flat out lying to them all the time.

Take notice of how many toxic people started blaming Yoshi-P for this, even though Yoshi-P likely did not have a hand in the actual coding. No if you actually watch the credits to the game you will notice that Square-Enix outsources various parts of the game development. It's very likely that any issue with the game has more to do with the number of people it has to go through to find the source of a problem. You can not simply go "oh well the duty finder was borked, so let's fire the duty finder team and get new people" because that isn't how it works. Chances are everything was working correctly at launch but the actual cleanup phase was not, so only X many instances could be spawned and they failed to time out when people failed them or exited them, or disconnected from them. Many times bugs related to stress load show up only when put live, that will not be noticed during tests.

The evidence of such is how the error varied depending on what you did. The Raubhan "cold steel" quest would just go "system error" but not disconnect you. Doing the level 50 job quests for RDM or SAM would disconnect you and you would have to wait 15 minutes, if your server queue was longer than 15, you never got thrown back out, if it was just under 15, you got back to queues again. On Excalibur, I was seeing 500 long queues every time I was dropped trying to access those job quests, and I tried them multiple times over the initial day. The Duty finder at 2am just wasn't having it, and you either got a DF queue or you sat in the queue with 1/1 1/1 2/2 for an hour before it reset, or it reset after 20 seconds. I lucked out and had most of the V3 end game stuff work without a hitch while people were getting stuck at Raubhan.

So that tells me another thing, that the solo duties appear to use the same data-center wide mechanism the regular duty finder uses, and thus any particular duty is full, you still get an unlabeled queue while it waits, and if that queue is full, that is why you get disconnected.

People think it works like this

User - Login gateway - Server (world/field, dungeons, solo content)
when it likely looks more like this
User - Login gateway (data center) - Servers(inventory) - (map server) - Party/Duty Finder - Instance server x
Where the Instance server for the multiplayer content is likely one physical machine that can do 1000 or so connections, and the party/duty finder process on the map server has to delegate which server has that instance. But it's very likely that the V2.x V3.x and V4.x solo content connections in a way that prevents oversubscription to avoid disconnection. Like if anyone forgets, V4.x has several very long solo sequences, which I believe the reason for Raubhan 's "cold steel" quest and Pippin's quest right after that are both extremely long by comparison to the battles you have at the end of 3.x solo.

So they could have just solve this by having the same DF mechanics for solo that they do for parties, sure it ruins the immersion quite a bit if you can just queue for something and then wander off killing FATE's while you wait. But not every occurrence is like that. In the case of "cold steel" there are FATE's that spawn right next to the "cold steel" quest, and it would not be unrealistic to at least stay on the same map for that one.

Another "load" issue shows up later after you do the solo-instance where you're chased around Kugane. Right after this one, you're in the office, but it took about a dozen tries to actually get the next map instance to start, otherwise you'd end up in an empty office, and just have to keep trying.

Bugs like this will happen, and MMO players know this and should expect instability for the first four weeks after a launch or expansion launch. If they are smart and want to plan around it, they would simply not subscribe during that period.

[Moonlite]

I'm more disgusted by the playerbase who felt so entitled that they keep spamming the forum with new threads on the same topic. What is the point of this? You're not going to see a forum moderator respond to everyone, no they will either ignore all but the stickied one (the one with the crown icon) or merge the rest.

Customer service is often not permitted to speak or take shots in the dark about what is wrong, hence they have to wait for an actual definitive answer. If they start speculating about what is wrong, and then turn out to be wrong, then people get it into their mind that the company representatives are flat out lying to them all the time.

Take notice of how many toxic people started blaming Yoshi-P for this, even though Yoshi-P likely did not have a hand in the actual coding. No if you actually watch the credits to the game you will notice that Square-Enix outsources various parts of the game development. It's very likely that any issue with the game has more to do with the number of people it has to go through to find the source of a problem. You can not simply go "oh well the duty finder was borked, so let's fire the duty finder team and get new people" because that isn't how it works. Chances are everything was working correctly at launch but the actual cleanup phase was not, so only X many instances could be spawned and they failed to time out when people failed them or exited them, or disconnected from them. Many times bugs related to stress load show up only when put live, that will not be noticed during tests.

So that tells me another thing, that the solo duties appear to use the same data-center wide mechanism the regular duty finder uses, and thus any particular duty is full, you still get an unlabeled queue while it waits, and if that queue is full, that is why you get disconnected.


Bugs like this will happen, and MMO players know this and should expect instability for the first four weeks after a launch or expansion launch. If they are smart and want to plan around it, they would simply not subscribe during that period.

I just want one answer who makes the decision to create all these solo instances in MSQ that prevent you from exploring 4.0, if they don't have enough. We are talking a choice by someone a gross negligence of what was available. If this had been some lame ass kill 5 grasshoppers and a cut scene would rdm/sam/blm/war had issues with their instances? You people all think we don't know launches have unforeseen issues. This is a design choice. The people who implemented it are fine they just work. But someone has to be responsible.

[JMadFour]

Calling someone else a whiny little shite isn't contributing anything. It is in fact rude, harassment and trolling someone elses topic. Please learn etiquette.

and yet you spending your whole thread insulting anyone who has the nerve to disagree with you.

etiquette indeed.

when someone is being a whiny little shite, I'm going to say they are being a whiny little shite.

this thread in its entirety isn't contributing anything.

it was not constructive from the word go, there was nothing constructive about it at all. it was just a guy whining because his friends leveled higher than he could. and then playing the victim card when people didn't say "oh poor baby." I'll save my constructive comments for constructive threads.

don't like it? report me and I'll eat the forum ban.

end of line.