Please fix when someone leaves Party Finder.

[AlexionSkyllark]

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.

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).

[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.

[AlexionSkyllark]

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.

When the hell did I say that?
You accuse me of not reading your posts, but you're clearly not reading mine as well

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

Do you disagree with that statement?

EDIT: OK, I'll make this more clear:
WHENEVER A PARTY FINDER IS CREATED, ANY PREVIOUSLY OCCUPIED SLOTS ARE LOCKED TO THE CLASS OF THE PERSON WHO WAS OCCUPYING THE SLOT.
THIS BEHAVIOR IS WRONG AND NEEDS TO BE CHANGED TO LOCK TO THE ROLE OF THE PERSON PREVIOUSLY OCCUPYING THAT SLOT. If that slot was occupied by a Paladin, it should revert to a TANK slot upon that person leaving, as an example. THIS is how the PF should work.

[Mapleine]

How is this not fixed? It's been what, eight years this has been occuring? I know for a fact this bug/awful behavior has been around since ARR. Each year it becomes that much more frustrating with some of the low patience swirling around.

[Rongway]

EDIT: OK, I'll make this more clear:
WHENEVER A PARTY FINDER IS CREATED, ANY PREVIOUSLY OCCUPIED SLOTS ARE LOCKED TO THE CLASS OF THE PERSON WHO WAS OCCUPYING THE SLOT.
THIS BEHAVIOR IS WRONG AND NEEDS TO BE CHANGED TO LOCK TO THE ROLE OF THE PERSON PREVIOUSLY OCCUPYING THAT SLOT. If that slot was occupied by a Paladin, it should revert to a TANK slot upon that person leaving, as an example. THIS is how the PF should work.

That is still wrong.

When a slot is freed, it should absolutely not expand to anything it was not originally set as. If I tell the PF I want a slot to be specifically an AST slot, under no circumstances should it allow anything but an AST in that slot. The moment someone leaves is not the problem.

When you set up the party finder, it should allow you to say "this slot that is occupied by my paladin friend should be a tank slot". It is the moment of setup that is a problem. The game does not let us tell it that the slot occupied by the paladin should be more than just a paladin slot. That is the problem that affects setup and re-setup. The problem has nothing to do with people leaving.

[AlexionSkyllark]

If I tell the PF I want a slot to be specifically an AST slot, under no circumstances should it allow anything but an AST in that slot

The thing is, I DIDN'T tell anything to the PF. Having an AST previously occupying the slot when the PF is formed is NOT equivalent to "telling the PF this is an AST slot". Our problem here is on what you consider should be the DEFAULT BEHAVIOR. For the vast majority of cases, people do not want a specific class in a slot, and therefore falling back to the role SHOULD BE THE DEFAULT BEHAVIOR.

It is the people who want a specific class in the slot (the absolute minority) who should need to manually set the slot everytime the slots of the PF free up. Not the opposite.
And no, we should not be forced to set the slot to a role slot manually for every slot every time we setup a PF with people already in the party. Having an automatic role fallback makes 99% of people happy, so that's what should be the default behavior.

[Canadane]

I tried to articulate this with my last post but Rongway is correct that it seems that you're misinterpreting the issue.
Nobody is saying there isn't a problem, but a fundamental understanding of how the system works is the first step into fixing the issues at hand.

[AlexionSkyllark]

I tried to articulate this with my last post but Rongway is correct that it seems that you're misinterpreting the issue.
Nobody is saying there isn't a problem, but a fundamental understanding of how the system works is the first step into fixing the issues at hand.

I understand how the system currently works. And that is the issue, the system is flawed in a fundamental level. It needs to change its core behavior to the one I describe if it is to fix the issue that the vast majority of players are having, without placing an extra burden on them.

[MellowMink]

When the hell did I say that?
You accuse me of not reading your posts, but you're clearly not reading mine as well

Alexion, with all due respect, please carefully reread what Rongway wrote in their precious replies before yelling at them; I understand your frustration with the current system, but the exact cause and specific code to address is more accurately based on what they wrote.

[AmpelioB]

I will just skip the current drama in the thread and I play this game since heavensward, even before party finder was a thing and currently this party finder error occurs anytime you join with a pre-formed party, regardless you filled the jobs or not, regardless if the person who leaves was on the pre-formed party or not. and please note, that if you put up a pf for a specific duty it will automatically set the roles for whatever duty you are gonna do. I have been experimenting this for a long while.