
--------------------------------------------------------------------------
Proposal: Party matchmaking system
Purpose
Making the task of finding party members easier, eliminating long waits and unnecessary shouting zonewide.
Feature overview
* Automatching
* Waiting lists for individuals
* Party start "wizard"
* Party position lists and filter functionality for best match
* Improved invitation functionality
Use-case overview
1. Start and fill new party
2. Register as seeking party
3. Automatch applicant with party
System overview
The system is a two part solution to the matchmaking problem in congested zones of the game, or where otherwise setting up a group by using the local chat channel is impractical. The primary component is the system for registering "player wanted" ads on a group basis. The ads can then be viewed by players seeking a group. The secondary component, meant as a more player centered variant of the same thinking, is a "group wanted" ad put in by an individual player.
One very appealing way of implementing the system is to make it accessible from a "Recruiter" NPC, present in all cities (and mission points) - Preferrably the group lising should span all districts with the same language, warping a player that joins a group in a different district to the one the group leader is in.
Main GUI components
"Open party positions" - A window displaying parties and the positions they want to fill with new players. Each position may be specified as to class, role or level. The mission or quest that the party wants to embark on is also listed here.
An example, using a "Recruiter" NPC as the entry to the system:
"Looking for party" - A window displaying players that are looking for a group. Here is listed class, level and the mission or quest that the player wants to embark upon. Players seeking a party may also choose to register their interest in this window, and thus list themselves for others to see.
"Party composition window" - A window accessible to the party leader. It lists the current members of the party, as well as the open positions and their criteria. The applicants for the positions are also visible here, and the party leader may accept or reject the applicants from this window.
Use-case elaboration
1. Start and fill new party
Purpose: Enables a party to be set up and positions to be set out for enterprising players to get. It is the bootstrapping process of embarking on a quest or mission, and imagined in this proposal to be the main recruitment process.
Actors: Party leader, Applicant(s)
Main sequence:
1. The party leader brings up the "Party composition window", specifying the purpose (quest he has active or mission starting from the current zone), the group charter, and any open positions.
2. When the party leader is satisfied with the defined criteria for the positions (which may of course include "anything goes") he publishes the positions on the "Open party positions" list.
3. An applicant that fills the criteria selects one of the posted positions.
4. The party leader may reject or accept the applicant. Iterate over 3-4 until all the positions are filled.
Alternative sequence 1:
1. As 1. in main sequence
2. The party leader brings up the "Looking for party" window, filtered on his posted positions and selected quest/mission.
3. The party leader selects an applicant for an invite
4. The applicant may reject or accept the invitation. Iterate over 3-4 until all the positions are filled.
Result: A full group, ready to set forth on the selected mission or quest has been formed.
2. Register as seeking a new party
Purpose: Enables an individual player to post an ad with certain criteria for party leaders to see. This makes for a more passive process than actively asking for invites to already formed groups, suitable for example for situations where you are engaged in some social activity, yet ready to take up arms should a good opportunity present itself.
Actors: Applicant
Main sequence:
1. The applicant brings up the "Looking for party" window, and selects to be listed.
2. The applicant selects among his active quests or the mission(s) starting from the current zone to form a list of acceptable tasks to solve.
3. The applicant selects to be listed as searching for a party, and is listed for all to see.
Result: The applicant is now easy to find for groups in the processof forming
3. Automatch applicant with party
Purpose: This is a very fast method of getting a group, and a bit like Googles "I'm feeling lucky". It simply applies to the first (oldest) party position around for which the player qualifies.
Actors: Applicant, Party leader
Main sequence:
1. The applicant clicks "Automatch" and a join request is automatically send out for the oldest position for which the player qualifies.
2. The party leader may rejact or accept the player. In the case of a reject, and automatic request goes out to the second oldest position for which the player qalifies. Iterate over 2 until there are no open positions or the player is accepted in a group.
Result: The applicant has quickly aquired a group, and the game may commence
List visualisations
There should be numerous ways to view the information. In the initial implmenetation, fairly crude filters are adequate, but a more elegant solution wil be more impressive

Filter on quest/mission - The person viewing the "Open party positions" may want to filter them on his active quests, as he is most likely looking for a party in order to complete some specific task. Likewise, a party leader viewing the "Looking for party" list will probably want to see only people willing to embark on the same quests as his group.
Filter on participants - Especially in the PvP mission, filtering on the level of the participants, the fame level of the participants and/or party leader, and so on might be interesting for the player viewing the "Open party positions" list. Of course, groups containing a person on ones ignore list should be well marked so one may stay clear of them.
Filter on own abilities - Seeing only the positions that one is eligable for might be an interesting feature. This might be the default, but should not be the only way. Ofttimes one can diplomatize ones way into a group by convincing the group leader that one can fill the task as well as the hypothetical character listed on the position requirements.
Filter on position requirements - For a party leader, filtering the applicants that are listed on the "Looking for party" list according to if they fill the requirements for the group positions might be valuable.
Further filters, such as "Filter on skill" and "Filter on age" and so on might be feasible, but seems impractical to me at this time.
--------
If you managed to read this far and liked this proposal, you might want to take a look at my player trust system suggestion
