Please fix when someone leaves Party Finder.

[Rongway]

No, the problem arises when someone leaves a party AFTER IT HAS BEEN FILLED UP. Because when putting said party BACK in party finder, instead of REMEMBERING WHICH SETUP THE FINDER WAS WHEN THE PARTY WAS CREATED IN THE FIRST PLACE, it ASSUMES A PARTY CREATED WITH ALL SLOTS LOCKED TO THE CURRENT JOBS

this is WRONG behavior

The system should NOT behave like that
The system should remember how the party was FIRST created, and retain THAT composition. It's not a NEW party, it's still the SAME party that was created before. Only it was filled up, wiped a couple of times and then some prick quitted, so you need to find a replacement. It should NOT lock the party to the current jobs in this situation, it should REMEMBER THE ORIGINAL SETUP FROM WHEN IT WAS FIRST CREATED

What you are doing here is describing how the system works and WHY the problem happens. And you are correct, the behavior you describe is precisely the reason why the problem happens.
And the behavior you describe is what is WRONG, and it's what SHOULD BE CHANGED.

The IDEA and the DESIGN behind how the party finder works and the hows and whys of it locking jobs to slots - this should be CHANGED. The solution should NOT need extra input from us, the users. At our side, it should work EXACTLY AS IT IS NOW, but WITHOUT the behavior you described, and ALWAYS remembering the ORIGINAL composition of the party, regardless if it was taken down and put back, or if it was filled and then reposted after someone left. IT SHOULD ALWAYS AND FOREVER REMEMBER THE ORIGINAL FORMATION UNTIL THE PARTY DISBANDS COMPLETELY OR THE LEADER MANUALLY CHANGES A SLOT (and that change should also stay in the slots FOREVER UNTIL THE PARTY DISBANDS).

Did you even read anything I said.

Of course the current behavior is wrong. I said as much.

The thing is you're misidentifying where the behavior is wrong. I don't know how many other ways I can word this.

The problem is not when people leave. Slots that were set to specific jobs when the partyfinder went up should stay set to those specific slots because those are the slots the PF leader specified when they put the listing up.

The problem is when the PF leader is setting up a listing, slots that are already filled are automatically set to one-job-only and the PF leader isn't allowed to set a range of jobs for those slots. The fix would be to allow PF leaders to set ranges of jobs for slots even when they are already filled.

If you put up a PF listing once and don't touch it, people can join and leave as they please without affecting each slot's job range unless they were already in the party at the time you put up your PF listing. Therefore, the problem is not with people joining and leaving; it is with the party setup functions before you put your listing up. That is what needs to be fixed. Not the part where people join and leave.