You said the problem isn't DC travel, but it is. I don't think they should get rid of DC travel. A cross-DC PF or some other solution, such as blocking off the public High-End category in PF when traveling, would help. However, SE said it will take a long time (years) to do something like cross-DC PF so will have to find another solution meanwhile. And yes, they are aware of the issue.

The issue is that it's not a cloud server. They use physical machines so there are technical hardware challenges with them communicating with eachother. This is evident when, for example, you enter a dungeon or another world and lose access to retainers, saddlebags or mail, or your CWLS and FC on another data center. They've obviously designed their hardware structure to where it's needlessly complicated for them to do things.

It's not about spaghetti code at all. I'm sure they could make a new cross-DC PF UI easily. They could probably even request a list of cross-DC PFs from a central server. But what about cross-DC parties and cross-DC party chat? This would probably be needed unless you were auto-traveled to the same DC immediately.

Then decisions have to be made such as "whose data center do we travel to for this content?" I think they could decide that this is the party leader's, but then the travel would need to happen immediately prior to entering the duty.

Then there is the fact we currently logout for DC travel and it takes a while. It's not fast enough to be seamless. And when we logout to the main menu, it often boots us if we were logged in for 2 days. They would need to make that travel happen without even logging out somehow or it would defeat the point.

So it's not really about spaghetti code. It's about technical challenges, and difficult design decisions, which understandably will take time to do.

By the way, it's in Japanese but the estimated active characters on Spriggan as of the end of August is 15,736 of which 9,860 have reached level 100 https://livedoor.blogimg.jp/luckyban...b/ebb814be.png