Please fix when someone leaves Party Finder.

[Canadane]

Well you can at least send tells across worlds now.
But this issue has always been the case of pre-existing party members that leave after the PF is formed. This is important in cases where you want a specific setup for some crazy reason.
Anyone who joins a PF but leaves before the PF is taken down and re-created, the spot remains it's original open style spot. While people who existed before hand their spot remains it's original job-specific spot.

[AlexionSkyllark]

Well you can at least send tells across worlds now.
But this issue has always been the case of pre-existing party members that leave after the PF is formed. This is important in cases where you want a specific setup for some crazy reason.
Anyone who joins a PF but leaves before the PF is taken down and re-created, the spot remains it's original open style spot. While people who existed before hand their spot remains it's original job-specific spot.

The thing is, they shouldn't CHANGE the slot to a specific one if YOU YOURSELF didn't set it this way, upon the slot's occupant leaving the party. Actually, to make this the default behavior is 100% senseless, it's so much rarer to actually need that the spot be filled by the exact class that left. Even if that was the original intention, it's such a niche small percentage of cases that it's absurd to make it the default.

[Rongway]

The thing is, they shouldn't CHANGE the slot to a specific one if YOU YOURSELF didn't set it this way, upon the slot's occupant leaving the party.

But, the thing is, you did set the slot to be one specific job only. It's not your fault; you had no say in the matter. When putting together the party finder, you were forced to accept that the already filled slots would be locked to the jobs that they started with.



There is, absolutely, 100%, a problem with the party finder, but the problem is not at the moment someone leaves the party, and the recruitment criteria should definitely not adjust itself when someone leaves, because some slots sometimes need to be filled by the specific job that left.

The problem is at the beginning, when the recruitment listing is created. The way the Recruitment Criteria interface should work is it should treat the filled slots like the unfilled slots, starting them as All / THDD / TTHHDDDD and allowing you to carve out unwanted classes, jobs, or roles from that starting point. Disallow carving out jobs to the point where the recruitment slots can no longer be mapped to the current party members, either by forcing the job that is already in each filled slot to be part of the allowed list for that slot, or by disabling the Recruit Members button if you carve out too many jobs to the point that recruitment slots can no longer be mapped to party members.


tl;dr: Yes, fix this; the problem is not when people leave though.

[AlexionSkyllark]

Bbut the problem is not at the moment someone leaves the party, and the recruitment criteria should definitely not adjust itself when someone leaves, because some slots sometimes need to be filled by the specific job that left.

I challenge you to find anyone here who agrees with that quote.
When someone leaves the party, the slot should rever to back to WHATEVER YOU SET THAT SLOT TO BE WHEN CREATING THE PARTY FINDER ENTRY. If you CREATED that slot as being for a specific job, THEN it should stay that way when that slot becomes vacant. But if the slot was created as a "All DPS" or "Any", or whatever, it should REVERT BACK TO THAT.

[Rongway]

I challenge you to find anyone here who agrees with that quote.
When someone leaves the party, the slot should rever to back to WHATEVER YOU SET THAT SLOT TO BE WHEN CREATING THE PARTY FINDER ENTRY. If you CREATED that slot as being for a specific job, THEN it should stay that way when that slot becomes vacant. But if the slot was created as a "All DPS" or "Any", or whatever, it should REVERT BACK TO THAT.

That's what I said.

If someone leaves and it locks the slot to that person's job, it's because you took the partyfinder listing down after they joined and put up a new party finder listing with them already in that slot. It locks to their job because that was the job that was in the party when the party finder listing went up. If you don't take the listing down after people join, you won't have this problem. If you take the listing down after someone joins so that you can update it, you will need to take it down and update it again if someone leaves.

My point is the problem is not happening when a person leaves. It's at the part where you're setting up your partyfinder listing because the current, incorrect, behavior is that when you're putting together a partyfinder listing all the filled slots get locked to the current members' jobs. The correct behavior would be to allow you to select jobs for each slot even when they are already filled. It is not a problem with the party finder locking a slot's job when someone leaves because you already yourself locked the slot when you posted your partyfinder listing. The behavior when someone leaves is correct: if a slot was set to one specific job when you posted the listing, it should stay set to that one specific job whenever that slot becomes vacant.