Quote Originally Posted by Gurgeh View Post
now -> you position is reserved until you are travelled and 'in' the PF.

before -> If you apply to a place, your going to take it when you get there.
Which system are we using? What you said before sounded like:
- character applies for dc travel
- dc travel completes
- character loads into the game
- pf slot is saved
- character can join pf now

or is it:
- character applies for dc travel
- pf slot is saved
- dc travel is completes
- character loads in game and can join pf now

at what exact step is the slot saved, and when does it disappear?

the wording is confusing me.

Semantic response: The reason for semantics is to avoid misleading statements. To say traveling works, implies that it is in an acceptable state and has things that we can use. To say traveling works is the same as saying a car works, while it can only go 30mph instead of 100+, the air conditioning is broke, the brakes are trash, the windows don't roll down, the radio requires a manual button to refresh the signal to keep playing songs properly. Does it serve the purpose of a car? Sure. But that doesn't mean we have a lot that we should we taking from it to create something else since the majority of it is a failure. When it comes to travel, the majority of it is a failure. We don't have messaging across DC's, we don't have updated friend info, we don't have passive buffs, we don't have retainer use, we can't look at plot information, we can't do ranked pvp, while hosting PF you can't tell people on the same data center consistently and can get forced to use /reply instead of direct messaging, There's a stupid amount of jank to where I don't even consider it a finished product.

as for this:
"<TimeLimit><AvItemLevel><Status><J1>..<J24><Filled1>..<Filled24>"

The problem is that the Filled1-24 is information that we don't even know can be sent as of right now because it doesn't exist in the current system. That Filled is a job description (PLD/SGE/RPR etc.) inside of the character data. And we have 0 character data that has shared across data centers other than name, currently world, and offline/online which is as surface level as you can possibly get. We don't even get current job equipped information for people on the same data center and a small single .png that shows on my friend list doesn't sound really hard to do, but it doesn't exist.

"Then on demand only the full PF info can be obtained. However, it is likely to be more efficient to provide this from the get go."
Yes, because you don't want people to have to click a pokeball on every single raid PF every few minutes for updated information to see where they want to join.