PSA - Don't try to do RDM instanced quest.

[Ransu]

Tried 3 times and it booted me every time. Was happening to others as well on Gilga. May be better when the servers quiet down, but just kind of a heads up for those willing to risk getting thrown into a 4,000 player queue.

[galbsadi]

This seems to be ANY instanced quest. Somebody tripped on a power cord....

[Add1kt]

I'm getting booted from the game with 90006 error codes every time I try to do an instanced quest.

[KisaiTenshi]

Here is what is happening (with some speculation in italics):

1. Attempting to do any solo-instanced combat specific to Version 4 (RDM, "Cold Steel") results in being dropped after about 30-60 seconds
2. Your first one or two attempts to log back in after the "World is full" queue message will say you are still in and wait
3. The next 4-10 attempts will just give you a 90002 error (connection was lost), which means the instance-world timeout hasn't ticked down.
4. After that times out (may take about 30 minutes in total) you will be back where you were.

I had no problem doing V3.x solo content, because my guess is that nobody was trying to do the solo content, having finished it. So if you have yet to finish the V3.x content, go do that and then try this again later.

On the other hand, earlier today the duty finder was throwing people out after 20 seconds, or if you managed to get into it, it wouldn't progress. That was likely what they fixed earlier today, and thus far have only had people randomly disappear from those instances.

[Bridgeburner]

any solo-instanced combat specific to Version 4

Not so much; My fresh lv47 is stuck behind "Fool Me Twice", a lv 46 solo instance in Mor Dhona. Same symptoms otherwise;

1) black screen when I try to zone into the instance
2) Dropped from the game with a 90006
3) Log back in to a "world is full queue"
4) Repeated drops with the 90002 error, as noted

My timeout's shorter than 30 minutes - more like 10 - but perhaps that depends on the instance in question.

You might have gotten lucky with your 3.x solo content. I was able to do some solo instanced content in 2.x earlier today, too, but as prime time started to kick in that's been a no-go. The random server lag and disconnects are already rough, but at least they don't keep me out as long as the instance problem.

[Newbcake]

Not so much; My fresh lv47 is stuck behind "Fool Me Twice", a lv 46 solo instance in Mor Dhona. Same symptoms otherwise;

1) black screen when I try to zone into the instance
2) Dropped from the game with a 90006
3) Log back in to a "world is full queue"
4) Repeated drops with the 90002 error, as noted

My timeout's shorter than 30 minutes - more like 10 - but perhaps that depends on the instance in question.

You might have gotten lucky with your 3.x solo content. I was able to do some solo instanced content in 2.x earlier today, too, but as prime time started to kick in that's been a no-go. The random server lag and disconnects are already rough, but at least they don't keep me out as long as the instance problem.

My only character, lvl19 is stuck on "Violators will be shot" and "To Guard a Guardian", level 14 & 15 class/story quests. When I try to launch either of these, I get a black screen for roughly 15 seconds then kicked out to another black screen with a 9006 error. Instance servers are toast regardless of what is being said.

[Vallhallix]

SAM instanced quest is the same.

[ZeroOps]

Confirming what I have been reading. New player as of today and trying to do lvl 9 instanced quest in the Grotto on Coeurl server. I am solo and it attempts to connect for 30 seconds then boots me with error 90006. I am then able to log back in immediately. Looks like everyone is having an issue no matter which instance they are trying to enter. Hopefully this gets fixed soon. This is a main scenario quest for me so I can't progress for now. There is my 2 cents. Thanks everyone.

[Newbcake]

Confirming what I have been reading. New player as of today and trying to do lvl 9 instanced quest in the Grotto on Coeurl server. I am solo and it attempts to connect for 30 seconds then boots me with error 90006. I am then able to log back in immediately. Looks like everyone is having an issue no matter which instance they are trying to enter. Hopefully this gets fixed soon. This is a main scenario quest for me so I can't progress for now. There is my 2 cents. Thanks everyone.

Yes it seems even the main scenario quests are busted

[JarinArenos]

Anyone still playing is out fate-grinding the new jobs, as far as I can tell. Even with the player congestion gone down, instances are still broken.