Party System

Party System

The Party system allows players to form groups and share quest progress. Party members contribute to shared tasks and can coordinate objectives together, making collaborative gameplay more rewarding.

Overview

Parties enable players to team up and work together on quests and objectives. When party task sync is enabled, all party members share progress on their quests, making it easier to complete challenging tasks together.

Features

• Create and manage parties with up to 10 members
• Share task progress with party members
• Cross-server support - Parties work across your network
• Party invites - Send and accept/decline party invitations
• Party UI - Graphical interface for party management

---

Configuration

Journey Config

Edit config/journey/config.json:

{
  "party_enabled": true,
  "party_max_size": 10,
  "party_task_sync_enabled": true
}

Config Options:

• party_enabled - Enable/disable the party system
• party_max_size - Maximum number of players in a party (default: 10)
• party_task_sync_enabled - Enable/disable shared task progress

---

Commands

/party create <name>

Create a new party.

Permission: journey.party.create

Example:

/party create "Elite Four"

Notes:

• You become the party leader
• Party name supports spaces (use quotes)
• Only one party per player

/party invite <player>

Invite a player to your party.

Permission: journey.party.invite

Example:

/party invite Notch

Notes:

• Must be party leader to invite
• Works cross-server
• Target player receives an invitation they can accept/decline

/party accept

Accept a pending party invitation.

Permission: journey.party.accept

Notes:

• Must have a pending invitation
• Leaves current party if in one
• Joins the party that invited you

/party decline

Decline a pending party invitation.

Permission: journey.party.decline

/party leave

Leave your current party.

Permission: journey.party.leave

Notes:

• If you’re the leader, leadership transfers to the next member
• If you’re the only member, the party is disbanded

/party disband

Disband your party (leader only).

Permission: journey.party.disband

Notes:

• Removes all members
• Deletes the party permanently
• Cannot be undone

/party list

List all members in your party.

Permission: journey.party.list

Output:

===== Party Members =====
Leader: Steve
Members:
  - Alex
  - Notch
  - Herobrine

/party kick <player>

Remove a player from your party (leader only).

Permission: journey.party.kick

Example:

/party kick Herobrine

/party transfer <player>

Transfer party leadership to another member (leader only).

Permission: journey.party.transfer

Example:

/party transfer Alex

Notes:

• Target player must be in your party
• You become a regular member
• Leadership transfer is permanent

---

Party Task Sync

When party_task_sync_enabled is true, party members share progress on tasks.

How It Works

• Only non-global tasks are synced (global tasks are server-wide, not party-specific)
• All party members see progress from any member’s actions
• Progress is synchronized when any party member makes progress
• Works cross-server - Party members on different servers still share progress

Example

1. Player A catches a Pokemon for a task requiring 10 Pokemon caught
2. Players B, C, and D (party members) all receive progress toward the same task
3. All party members see the updated progress in their sidebars
4. When any member completes the task, all members complete it

Task Types That Sync

✅ Personal Tasks - Tasks assigned from task sources

✅ Tracked Tasks - Tasks being tracked with /track

❌ Global Tasks - These are server-wide, not party-specific

---

Cross-Server Parties

Parties work seamlessly across your server network when NATS is configured.

How Cross-Server Works

1. Party data is stored on the server where it was created
2. Party invites are sent via NATS to players on other servers
3. Party updates (member join/leave/kick) sync across all servers
4. Task progress from any party member on any server is shared with all members

Requirements

• NATS messaging configured via Ceremony
• All servers connected to the same NATS cluster
• Matching cluster_name in Ceremony config

See the Ceremony Integration guide for NATS setup.

---

Best Practices

For Server Admins

✅ Encourage use - Parties make gameplay more social and engaging

✅ Monitor size limits - Adjust party_max_size based on your server’s player count

✅ Moderate names - Use chat filters or moderation for party names

✅ Balance rewards - Party task sync can speed up progression, adjust rewards accordingly

✅ Clear permissions - Ensure all players have necessary party permissions

For Players

✅ Coordinate with party members - Use voice chat or Discord for better coordination

✅ Share the workload - Different members can focus on different task types

✅ Stay online together - Progress syncs in real-time when party members are online

✅ Communicate before leaving - Let your party know if you need to leave

---

Permissions

permissions:
  journey.party.create:
    description: Create a new party
    default: true

  journey.party.invite:
    description: Invite players to your party
    default: true

  journey.party.accept:
    description: Accept party invitations
    default: true

  journey.party.decline:
    description: Decline party invitations
    default: true

  journey.party.leave:
    description: Leave your current party
    default: true

  journey.party.disband:
    description: Disband your party (leader only)
    default: true

  journey.party.list:
    description: List party members
    default: true

  journey.party.kick:
    description: Kick members from your party (leader only)
    default: true

  journey.party.transfer:
    description: Transfer party leadership (leader only)
    default: true

---

Troubleshooting

Party Invites Not Working Cross-Server

Check:

1. NATS is configured and connected on all servers
2. party_enabled: true in Journey config
3. Players have correct permissions
4. Target player is actually online on the other server
5. Check server logs for NATS connection errors

Task Progress Not Syncing

Check:

1. party_task_sync_enabled: true in config
2. Players are in the same party
3. Task is not a global task (global tasks don’t use party sync)
4. NATS is properly configured for cross-server sync
5. Both players have the task active/tracked

Party Commands Not Working

Check:

1. party_enabled: true in config
2. Player has the required permission
3. Player meets command requirements (e.g., must be leader for /party kick)
4. Party exists and player is a member

---

Use Cases

Questing Together

Form a party with friends to complete questlines together:

/party create "Quest Squad"
/party invite Friend1
/party invite Friend2

All party members now share progress on quests, making it faster to complete objectives.

Competitive Teams

Create competitive teams for server events:

/party create "Team Red"
/party invite Player1
/party invite Player2

Party members can coordinate to complete global task objectives together while sharing personal task progress.

Guild Integration

Use parties as the foundation for guild/clan systems:

/party create "Shadow Clan"
/party invite Member1
/party invite Member2
...

Parties provide the technical infrastructure for player groups to collaborate effectively.

---

Related Systems

• Global Tasks - Server-wide collaborative tasks
• Task System - Individual player tasks
• Ceremony Integration - NATS setup for cross-server sync