[Feedback] Data Center Travel Changes

[xanatosdc]

Stay mad they aren't opening Aether.

You and your assumption again. I'm not trying to move to Aether and give up my house and FC. Maybe stop making assumptions about strangers.

[VoidsentStatus]

You and your assumption again. I'm not trying to move to Aether and give up my house and FC. Maybe stop making assumptions about strangers.

I have friends both on my own DC and Aether, and ... it hasn't been an issue at all to play with either or both. Until the current dumpster fire, that is.

[xanatosdc]

I will spell it out one last time for you, and then you're going on my ignore list, because clearly, you can't comprehend the written word.

1) Read my sentence carefully. Again. How would moving to Aether solve an issue with DC travel when I have friends on more than one DC? Right. It wouldn't. Apart from the fact that I'd lose all my stuff that I paid for.

2) I am "mad", because SE screwed over the one community that keeps paying their subscription during content draughts - the RP community. To not even fix the problem that they tried to fix, which only exists in the first place, because they're too incompetent to implement cross-DC PF.

And now I'll enjoy the precious peace that will follow by no longer having to read your posts.

[GiR_Zippo]

I am on Seraph and even on primetime you are waiting more than 5 minutes to get a group for a duty and I'm a healer. On other DCs you'll get an instant join.
Not to mention M1-4.


To the Cross DC PF

This thing will suffer from the same issues we have with the DC travel.

It seems the Physical DCs are running separately, or in other words: they don't know each other.

Just in case SE implements a cross DC PF and the DCs now know the realtime data from each other (player count, occupation, s.o.) they have to include an occupated slot for every possible player in this PF for the world of the pf-rooster (just to get the party at one place).
Perfect, but now theres a catch:
We have a player hardcap and a softcap for the world.
The hardcap is the max. what a world could handle.
The softcap is the reserved slot limit for resident players.
The diff. between hard and softcap are the free slots for visitors and travelers, if the softcap is reached.
Of course world and internal DC residents will be higher prioritized when logging in than everyone else.

Now you have your cross DC PF, you'll occupy X slots for your possible members. Perfect, the playercount on this world raises and all free slots are gone, no DC travel and new cross DC PF are possible anymore.
Why you might ask, I only had a group of 8.
Yeah, but 25 other ppl on your world did the same.

To overcome this problem, SE could to implement a function to occupy the slot on an less populated world on an other DC. This will help, your party is able to meet and greet, do what every you like to do, but not on the world of the PF-rooster.
If this is what you like to have, it'll be fine.
It's basically doing the same what you can do manually, meet on Dynamis and create a pf. ¯\_(ツ)_/¯

There is an other catch: It will use the same travel function as we are currently have.
SE should be able to disonect the client from the current DC, do the travel without throwing you to the login screen and reconnect you to the new DC, but at least you'll have a long loading screen and a cute messagebox or mogry.

(sorry too lazy to explain, why you currently need to be on the same DC. It's how the dungeon servers are connected to the DC and your char datas are handled)

[VoidsentStatus]

I am on Seraph and even on primetime you are waiting more than 5 minutes to get a group for a duty and I'm a healer. On other DCs you'll get an instant join.
Not to mention M1-4.

It seems the Physical DCs are running separately, or in other words: they don't know each other.

1) From what someone explained on reddit a few years ago, essentially your home data center holds your character data and they have to cut and paste your character to another data center's database. That is the process of the DC Travel and why we don't have the ability to send tells etc. across DC's yet. From a simple standpoint, even just making a clone of your character across every DC that you'd want to communicate with, would be a ridiculous stresser to the database as you'd be looking at storing 4x the load just for the same region, assuming cloning is even possible and cut and paste isn't the only method. That is likely the reason why fixing the issue for cross DC communication would take 3 years as Yoshi P said because they'd have to make significant hardware changes and or uproot that foundational system of communication entirely.

2) I'm going to ignore the complaint about a 5 min wait since that seems like a bait.

[PassinLay]

Balmung congested 24 7 basically except on off times
-> SE opens transfer there



I love when things make sense

[VoidsentStatus]

Balmung congested 24 7 basically except on off times
-> SE opens transfer there



I love when things make sense

Oh, I busted out laughing seeing Balmung open. The fact Balmung opened before ANY world on Aether shows how much SE hates the idea of even giving Aether hope xD

[xanatosdc]

Balmung congested 24 7 basically except on off times
-> SE opens transfer there

They stopped making sense since 7.05.

[PassinLay]

They stopped making sense since 7.05.

The same defenders of this whole "congestion" from this thread will tell you that it clearly makes sense and that only people going on aether are the big bad guys, but going to balm is okay

[Rueby]

The same defenders of this whole "congestion" from this thread will tell you that it clearly makes sense and that only people going on aether are the big bad guys, but going to balm is okay

Feel free to gaslight each other and fantasize about what you think people have said. It's honestly weird to see and it honestly isn't a good look at all.

Edit:
Literally no one said anything to defend that decision but you're already putting words into people's mouths because you want to mald about it. Kinda yikes.