Parties
Grouping up, the three party gamemodes, and the permission that decides how big a party can get.
A party is a group of players who move through the plugin together. It exists only in memory — a restart dissolves every party.
Commands
| Command | What it does |
|---|---|
/party, /p | Open the party hub |
/party create | Start one, with you as leader |
/party invite <player> | Invite somebody |
/party join <leader> | Join, by the leader's name |
/party decline <leader> | Turn an invitation down |
/party leave | Leave |
/party disband | Close the party — leader only |
/party kick <player> | Remove a member — leader only |
/party transfer <player> | Hand leadership over — leader only |
/party open | Toggle open/closed — leader only |
/party announce | Broadcast the party to the server — leader only |
/party chat | Toggle party-only chat for yourself |
/party game | Open the game menu — leader only |
/party cancelgame | Cancel the running party match |
/party invitations | Your pending invitations |
/party members | The member list |
/party hub | The hub, same as /party |
Invitations
An invitation is valid for 60 seconds and is refused if the target has party invitations off
in /settings, is already in a party, or the party is full.
An open party can be joined by anybody who knows the leader's name, without an invitation. Closed is the default.
/party announce broadcasts the party to the whole server. It needs
exyliapractice.party.announce, the party must be open, and it is rate-limited by
party.announce-cooldown-seconds — 60 by default.
Size
The maximum starts at whatever the leader's permission allows and can be adjusted down and up from
the hub, between party.min-size and the leader's own ceiling.
exyliapractice.party.max_slots.<n>
exyliapractice.party.max_slots.*The highest numbered node the leader has wins, capped by party.max-size. The wildcard gives
party.max-size outright. With no node at all the leader gets party.default-max-size — 10 by
default.
| Setting | Default |
|---|---|
party.min-size | 2 |
party.default-max-size | 10 |
party.max-size | 100 |
Size is checked against whoever is leader at the time it is changed. Transferring leadership to somebody with a smaller ceiling does not shrink an already-large party; it only stops them raising it further.
The three party gamemodes
/party game — leader only — offers whichever of these the chosen kit allows:
Everybody against everybody, spawned in a ring around the arena's party FFA spawn within
party.ffa-spawn-radius blocks.
The party is shuffled and cut in half into team A and team B. An odd party puts the extra player on team B.
The whole party queues against another party on the same kit. First two parties waiting are paired.
Every gamemode needs all members available — nobody queued, in a match, editing a kit or held by another plugin — and at least two online members. All of them are claimed together or none of them are.
A kit with points-to-win above 1 is refused for an FFA with a message. Points are per-player and an
FFA has no opposing side to score against.
Party duel queue
/party game → Party duel puts the party in a per-kit queue of parties. The first two parties
waiting on the same kit are paired immediately; until then the party waits and the leader can leave
with the same button. Team A is one party, team B is the other, whatever their sizes.
Party chat
/party chat toggles it per member, not per party. With it on, everything you type goes to the party
instead of to global chat.
When somebody leaves
Leaving, being kicked or disconnecting removes the member. If the leader goes, leadership passes to the first remaining member. If the last member goes, the party is disbanded, which also takes it out of the party-duel queue.
Party membership is what the plugin reads to decide whether a player in the lobby is AVAILABLE or
IN_PARTY, so it changes their hotbar and their sidebar immediately.
Something missing on this page? Tell us on Discord