Raubahn Extreme will return? Version 6.0

Quote:

---

Originally Posted by Aldora

Granted using a sentence like "World is full" might give the impression that you cannot log in at all and that is should be used for action like creating a new character on that particular world. If anything they could change it to "There seems to be a disturbance in the Aether, which appeared like as a crowded gate to the World. Souls waiting at the gate: x", but i guess that nobody wants to see a long sentence each time they are placed in a login queue.

---

"Too many people are attempting to log on. Please be patient! Your place in line: x" seems like something people would be able to both understand and also something that wouldnt be too long to read.

Quote:

---

Originally Posted by Moonlite

Not to mention most job quests also used an instance. It was horrible design to lock content behind something like that. They were so puffed up with all the MSQ fanboy's from the end of HW's. When anyone mentioned problems from the fuller servers they got dismissed as it was those players fault and not SE.

---

This. The Raubahn Ex debacle was a combination of 3 things:

1) A mandatory instanced solo fight early in the MSQ (Raubahn)

2) Introducing TWO extremely popular jobs (SAM and RDM) in the same expansion that also used instanced solo fights in their story quests

3) A second mandatory instanced solo fight not much farther into the MSQ (Pipin Ex).

In the above examples, SE literally made the worst decisions they possibly could have by bottle necking players.

Even YoshiP addressed the design issue literally after Stormblood early access, that's why the OP scare tactics are so far off the cliff.

Solo instances require an instance server, it doesn't matter that you are logged into Balmung. The fight took place on another server that's requested when you queue up for those things that require you to queue a party or drop everyone and solo. So you have a solo bottleneck if people are slow or have to repeat it, and you know that happened as well.

With SHb your first instances were dungeons early on for the story, since you can always get a a light party moving through the paces quicker. Plus we got trusts so no one really had to wait to do a dungeon, ever. That was a huge leap forward.

Now you don't even need to wait to do a new expert story dungeon anymore too, because of trusts.

Quote:

---

Originally Posted by MilkieTea

"Too many people are attempting to log on. Please be patient! Your place in line: x" seems like something people would be able to both understand and also something that wouldnt be too long to read.

---

They could always just put it as:

Login server full, your're number X in queue

Quote:

---

Originally Posted by Deceptus

This. The Raubahn Ex debacle was a combination of 3 things:

1) A mandatory instanced solo fight early in the MSQ (Raubahn)

2) Introducing TWO extremely popular jobs (SAM and RDM) in the same expansion that also used instanced solo fights in their story quests

3) A second mandatory instanced solo fight not much farther into the MSQ (Pipin Ex).

In the above examples, SE literally made the worst decisions they possibly could have by bottle necking players.

---

And even if you got past both Raubahn and Pippin, it wasn't much longer until you'd have to run Sirensong Sea to continue. On top of normal roulette traffic from people trying to get a jump on leveling.

Quote:

---

Originally Posted by Avatre

They could always just put it as:

Login server full, your're number X in queue

---

I think that might present a similar misunderstanding to OPs misunderstanding. But i personally like this suggestion a bit more than my own.

Oh look its Dani, doing a Dani thingy :D

Quote:

---

Originally Posted by Xyphon

Oh look its Dani, doing a Dani thingy :D

---

Doing a thing six months ago where it had long sunk into the mud until you bumped it.

Any reason for hauling it up?

Quote:

---

Originally Posted by Daniolaut

Raubahn Extreme

---

Rauban Extreme was caused by full instance servers and the issue that solo instanced content did abort completely, when instance servers were full.

Somewhere before Shadowbringers they silently added a queue system for solo instance content, which solves the issue we had with Rauban in 4.0.