What is the context of this complaint?
Why does the user submitting this complaint consider this a problem?
Continue reading...
- In Patch 5.30, the Party Finder interface was updated to allow for the specification of "One Player per Job".
- If "One Player per Job" is selected, and a player attempts to join a Party Finder party listing that already contains the job that the player is currently using, then the error message: "Unable to join. Only one player per job permitted." will display, and the player will be automatically rejected from joining the party listing.
- However, a Party Leader that selects "One Player per Job", can still leave that Job open in the individual Role listings within the "Recruitment Criteria" menu.
- Example to clarify:
- Party Leader selects "Recruit Members" from Party Finder menu.
- Party Leader selects "One Player per Job" in the "Roles" subsection.
- Party Leader changes no other specifications in the "Roles" subsection.
- Now, each Role will still list the same Jobs in every slot. For example, all "Healer" slots will list "WHM, SCH, AST".
- This interacts in an "unclean" way with another Party Finder feature, "Advanced Search".
- If a player selects Party Finder → "Advanced Search" → "Assign current class/job as sought role", usually the Party Finder search results will automatically filter out any parties that do not have room for the player's current Job.
- However, if a party has "One Player per Job" enabled, but has not otherwise-restricted the role slots that Job corresponds to, then the party will not be filtered from Advanced Search results.
- Example to clarify:
- Party Leader is a White Mage (randomly-chosen example).
- Player Two (who is looking for a party) is a Red Mage (randomly-chosen example).
- Party Leader selects "Recruit Members" from Party Finder menu.
- Party Leader selects "One Player per Job" in the "Roles" subsection.
- Party Leader changes no other specifications in the "Roles" subsection.
- Party Leader lists their party in Party Finder, and Player Three, a different Red Mage, joins the party.
- The Party Listing will now show: WHM | (blue tank slot 1) | (blue tank slot 2) | (green healer slot 2) | RDM | (red dps slot 2) | (red dps slot 3) | (red dps slot 4)
- Because Party Leader left all other settings on default under "Roles" when making their party listing, hovering over each "red dps slot" will show: "MNK, DRG, NIN, SAM, BRD, MCH, DNC, BLM, SMN, RDM, PGL, LNC, ROG, ARC, THM, ACN". Note that "RDM" is still listed in each slot, despite the party already having a RDM.
- Now, Player Two uses "Advanced Search" and selects "Assign current class/job as sought role", intending to filter out any parties that do not have room for a Red Mage.
- Player Two sees that a party matches their search criteria — success!
- However, they cannot actually join the party, because even though "Advanced Search" sees three "red" slots still have "RDM" listed in them, the "One Player per Job" rule overrides this and blocks Player Two with an error message.
- Therefore, Player Two now has to manually sift through each "One Player per Job" party, and make sure they actually have room for a Red Mage. This effectively defeats a large part of the benefit of using the "Advanced Search" filter.
Continue reading...