Skip to main content

Party System

EliteMobs parties let up to five online players enter dungeons together, share nearby kill-objective credit, roll on Elite gear, and see each other's status. Parties are session-only: membership is never saved, and a player is removed immediately when they leave the party or log out.

The system is enabled by default in Party.yml and all party commands use the elitemobs.party permission (default true).

Creating and joining a party

CommandDescription
/em party createCreates a party with you as its leader
/em party invite <player>Invites an online player; any current party member can invite
/em party acceptAccepts your most recent unexpired invitation
/em party leaveLeaves your current party
/em party menuOpens the inventory-based party controls
/em party hideinteractionhintPermanently hides right-click party hints for you

A party has one leader and at most four additional members (MAX_MEMBERS is 5). If the leader leaves, leadership passes to the next member. Invitations expire after 60 seconds by default. The party is dissolved when its last member leaves.

Right-click invitation hints

Right-clicking another player shows a one-line chat hint with clickable [INVITE] and [Don't show again] buttons. The hint is skipped when the target is an NPC, lacks elitemobs.party, already has a pending invitation, is already in a party, or when your own party is full. Each player has a personal cooldown of playerInteractionHintCooldownSeconds (300 by default), and /em party hideinteractionhint disables the hint permanently for that player (stored on the player's persistent data).

Inventory party menu

Bedrock players, servers with onlyUseBedrockMenus enabled, and players who turned off book menus get an inventory version of the party controls instead of chat buttons. The same menu handles invitations, the invite player picker (45 heads per page), the right-click hint, and the dungeon ready check. /em party menu opens it for anyone; if you have a pending ready check or invitation, that prompt opens first.

Entering dungeons together

Instanced and dynamic dungeons

When any party member chooses an instanced dungeon, EliteMobs snapshots the entire current roster and starts a clickable ready check. The initiating member is ready automatically and receives a CANCEL button in case they selected the wrong dungeon. Every other member receives READY and DECLINE buttons for a token tied to that exact launch.

The prompt identifies the dungeon and difficulty; dynamic-dungeon prompts also include the selected level. The ready check lasts 30 seconds by default. Only one ready check or in-progress launch can exist for a party at a time.

Before anybody moves, EliteMobs validates the whole group:

  • every member is online and still belongs to the same party
  • the dungeon has enough free player slots
  • every member has the package's permission, when one is configured
  • nobody is already in another instance
  • the instance and world can be prepared successfully
  • the cancellable MagmaCore MatchJoinEvent preflight accepts every member

A decline, timeout, roster change, or failed validation cancels the group entry. EliteMobs does not deliberately admit only part of the party. If cloning an instanced world has already been queued, the party keeps its launch reservation until that operation succeeds, fails, or is cancelled.

EliteMobs' similarly named PlayerJoinDungeonEvent is not part of that preflight. It is a non-cancellable notification fired only after a player has been admitted.

The ready and decline commands shown in chat are /em party ready <token> and /em party decline <token>. The generated token prevents an old button from accepting a different launch.

Personal enchantment challenges stay solo

Item-enchantment challenge dungeons do not bring the party because the challenge temporarily owns the initiating player's item.

Open-world dungeons

Choosing an open-world dungeon starts the normal safe-teleport countdown for every available party member after validating the full roster and package permission. Each member can still cancel their own countdown by moving, so open-world teleports are not an all-or-nothing arrival guarantee.

Shared quest progress

When a party member earns kill credit, nearby party members receive credit for any matching active kill objective, including objectives tied to a specific custom boss. The other members must be online, in the same world, and within sharedProgressRange of the kill (128 blocks by default).

Quest ownership remains personal. Parties do not accept quests, turn quests in, collect another member's reward, or share fetch items, NPC dialogue, or arena participation. A player inside an unrelated active instance is also excluded from outside shared credit.

Party loot

When at least two party members are nearby, normal Elite equipment, special Elite gear, and eligible custom items enter a shared Need / Greed vote. Nearby party members do not have to land the killing hit to participate. Coins and Elite Scrolls remain personal.

Each item tracks the members who were eligible when it was added. Dungeon boss lockouts are applied before a player enters a vote. The normal voting window ends after 60 seconds without a new drop; new party drops refresh that inactivity window, but lootVoteMaximumLifetimeSeconds caps one party vote at 120 seconds by default.

Party sidebar

While a player belongs to a party, the combined sidebar shows:

  • the leader and members in stable display order
  • five-segment health indicators and a downed marker
  • remaining lives for members participating in the same instanced dungeon
  • the viewer's tracked quest when space permits
  • alternating /em party invite <player> and /em party leave hints

sidebarEnabled: false disables only this combined sidebar; parties continue to work and the normal EliteMobs quest scoreboard is used instead. Health colors, glyphs, line formats, and the action rotation interval are all configurable in Party.yml.

Main settings

KeyDefaultPurpose
enabledtrueEnables session parties
sharedProgressRange128.0Same-world range for shared kill credit and party loot eligibility
inviteTimeoutSeconds60Invitation lifetime (minimum 5)
dungeonReadyCheckTimeoutSeconds30Ready-check lifetime (minimum 5)
lootVoteMaximumLifetimeSeconds120Hard party-vote lifetime (minimum 60)
sidebarEnabledtrueEnables the combined party/quest sidebar
sidebarRotationSeconds10Seconds between invite and leave hints (minimum 3)
playerInteractionHintsEnabledtrueShows the party hint when right-clicking another player
playerInteractionHintCooldownSeconds300Minimum time before the same player gets another right-click hint (minimum 1)

See EliteMobs Config Settings for the current message and sidebar keys.