Best served with cold steel.

Quote:

---

Originally Posted by Theodric

Likewise.

That the situation has - apparently been resolved on the JP and EU datacentres is great. Now, hopefully it can be resolved over on the NA datacentres very soon as well.

I suspect that a large part of the problem is the sheer player bloat on Gilgamesh and Balmung where Aether is concerned.

---

How about they shut down either primal or aether for a while, let them advance for a few hours then do the other? Having both running simultaneously isn't solving anything.

Quote:

---

Originally Posted by LunarEmerald

How about they shut down either primal or aether for a while, let them advance for a few hours then do the other? Having both running simultaneously isn't solving anything.

---

Or shut down instances that don't need to be running. Again: PvP, guildhests, novice hall, Palace of the Dead. Shutting down a datacenter is just going to make things worse (even more people angry). Primal and aether do not even use the same instancing.

Quote:

---

Originally Posted by JunseiKei

Or shut down instances that don't need to be running. Again: PvP, guildhests, novice hall, Palace of the Dead. Shutting down a datacenter is just going to make things worse (even more people angry).

---

I think solo instances are handled differently than duty finder. DF stuff is running fine. It's the solo ones having problems.

Quote:

---

Originally Posted by LunarEmerald

I think solo instances are handled differently than duty finder. DF stuff is running fine. It's the solo ones having problems.

---

It does not make sense that individual instancing would be shared across region rather than datacenter. Pretty sure they use the same server space, at least to some degree. DF and POTD were having tons of disconnects before the temporary uncapping.

Quote:

---

Originally Posted by LunarEmerald

Apparently the problem is gone on JP and EU datacenters so why are NA still fucked?

---

I'm curious about this. Any EU or JP player can confirm?

IMO, For when things get this congested, they should just implement a Duty Finder-like queue so you can just queue up, then wait your turn, like the DF, even if it breaks the immersion a bit, this would just be a measure that would only be implemented during periods of super-high congestion, like this.

Quote:

---

Originally Posted by gothikka

IMO, For when things get this congested, they should just implement a Duty Finder-like queue so you can just queue up, then wait your turn, like the DF, even if it breaks the immersion a bit, this would just be a measure that would only be implemented during periods of super-high congestion, like this.

---

This, it's what WoW basically does for solo scenarios. This design here is 1.0 bad. Whoever is in charge of it should be ashamed, even if that's Yoshi.

At this point, who cares about the immersion...
This completely ruined the MSQ for me... :(

Now Raubahn doesn't even trigger the dialog anymore. Way to go SE, fantastic early access!! Get your early access with level cap to 62, some MSQ and 2 new area maps! Please look forward to it.
You've learned clearly with two past launches. What's left to do? Oh yeah, level sam and rdm... no wait... eternal queues on DF with the sporadic 90k... So solo PotD? Yeah... time to play something else.
I've been here sine v1 early access, I've not played sometimes maybe for two weeks, I love this game. But everything has a limit. Not worth it anymore.

Quote:

---

Originally Posted by lakukisu

The second update from Yoshida. It can also be found here.

---

These post do nothing but tell us they don't care enough to properly design quest and apply system resources to prevent this from happening.