Small QoL Improvements

[Rongway]

While running for PFs today, I learned that a really nice but small QoL thing would be for the PF to not keep the roles of the players that leave your PF. For example, if I have unrestricted roles, but a SAM leaves my PF, the empty roles will still be unrestricted except for that slot the SAM occupied. Every time that happens, I have to edit the PF then select then deselect the box to remove class restrictions. This happens for both when the roles are role-specific and unrestricted.

Thread: Please fix when someone leaves Party Finder

No, the behavior has always been that neither joining a party nor leaving a party affect what jobs are allowed for each slot.

The problem arises when people take down their party listings after people have joined so that they can update the remaining slots to be more or less restrictive. At that time, when they put the updated party listing up, all filled slots lock to the current party members' jobs as if it was a brand new party listing with the new number of people already in party, because that's what it is every time you take down and put your party listing back up, as far as the system is concerned. To fix the problem, we need to be allowed to set a range of jobs for each slot even when there's already someone in that slot, before putting up a party listing. That way, if someone leaves the party, the slot they left would show a range of acceptable replacement jobs.

[Infren]

That doesn't change that it would still be a nice qol change if we didn't have to update the party listing. It would be more convenient for the pf poster to just have the slots remain the leader's role preference without having to kick out everyone from the pf to empty all the slots or needing to update the slots every time someone leaves.

[OpusNK]

Increase the number of saved waymark slots please. 5 slots seems slightly restrictive, even a few more slots would be helpful.

[Kaedys]

Increase the number of saved waymark slots please. 5 slots seems slightly restrictive, even a few more slots would be helpful.

Or, as an alternative, make the waymark saves local and essentially unlimited (but filtered on the current zone). I get that they can't store an unlimited number of waymark presets server-side, but if they're only stored locally, that's not an issue. And they're already heavily restricted anyway, since you cannot play the waymarks while in combat. So there really isn't much in the way of exploits to be had by having substantially increased waymark slots via local saves. It just means you don't have to go look up and manually place the markers again when you go back and do old extremes or savages for the mount drops.

[Luizgazen]

Differentiate magic and physical incoming damage on the floating numbers, would make much easier to know when pop a Dark Mind rather than flooding the chat window with combat logs

[toramorigan]

Differentiate magic and physical incoming damage on the floating numbers, would make much easier to know when pop a Dark Mind rather than flooding the chat window with combat logs

I seem to recall Yoshi-P actually addressing this in a recent PLL, but I don't remember which one, but if I recall correctly (which I may not), the UI/battle engine teams mentioned some complications from it? That or the various numbers would be informational overload? I wish I could find the one that had it.

[Esmoire]

Shared FATEs and currencies critiques:

1) First and foremost, please put bicolor gemstones in the currency UI.
2) Shared FATEs should default to the expansion you are on. Right now you have to change it every time you log on. This is a minor annoyance that only earned notice with the second expansion using the feature.
3) I really don't need to see deprecated currencies I don't have any of. If I have 0 of an old currency, it should be invisible and not disrupting the flow of the UI. An option can be included to make deprecated currencies visible for those who want it.

[Esmoire]

Another thing: Please show when someone was last online in a CWLS. Even if this was only possible in the web version, this would suffice. Just makes it easier to manage CWLSs when we only have room for up to 64 people.