Set up the lobby
Set the lobby hotbars, double jump, player visibility, jump pads, portals and the PvP zones players warm up in.
You will end with a lobby that has a spawn, a hotbar that sends players to the queue, a party and their settings, and optionally jump pads, portals and a PvP warm-up zone. Everything outside a match is the lobby's business: what a player is holding, who they can see, and what they can walk into.
Before you start#
- ExyliaPracticeCore is installed: see Installation.
- You have
exyliapractice.admin(operators do). - If you run ExyliaLobby as well, read that section first: it can take over several of these features.
Steps#
Set the lobby spawn
Stand where players should appear and run /epc, then click Set lobby spawn. Players return there after every match and when they join the server. Without a spawn the plugin does not teleport anybody to the lobby.
Choose the hotbar
Players carry a different hotbar in each state: lang/<language>/items/lobby.yml in the lobby, items/party.yml in a party and items/queue.yml in a queue. The right one is applied whenever their state changes. Each entry is a slot, an item and a list of commands:
queue:
slot: 0
material: MACE
name: "<gradient:#FF8C00:#FF4500>⚔ Queues</gradient>"
lore:
- "<#888888>Browse available queues"
commands:
- "any: player: queue"The shipped lobby hotbar links out to /ffa, /events and /rtp, which belong to other plugins. Remove the entries you do not run, then reload from /epc → Reload.
Pick the lobby features
Run /epc, click Settings, then Lobby. Each button flips one setting and shows the current value and the default:
| Button | What it does |
|---|---|
| Defer to Lobby | Let ExyliaLobby run jump pads, regions and visibility |
| Double jump | Players double jump in the lobby |
| Show VIPs / Show party / Show others | What new players see before touching their own settings |
| Sneak toggle | Sneak twice quickly to show or hide other players |
| Join message / Quit message | The join and quit announcements |
| Command whitelist | Block non-whitelisted commands in matches, queues and PvP zones |
Check that it works#
- Join the server with a normal account. You should appear at the lobby spawn holding the lobby hotbar.
- Press jump twice in the air: you should double jump.
- Click the queue item: the
/queuemenu opens. - Join a queue: the hotbar switches to the queue one, with Leave Queue in the last slot.
Hotbars are not reapplied to somebody standing in a PvP region: they are holding that zone's kit, and overwriting it mid-fight would be worse than the wrong compass.
Going further#
ExyliaLobby#
With ExyliaLobby installed and defer-to-exylia-lobby: true (the default), the lobby jump pads, portal and PvP regions, double jump and the show/hide-players toggle are left to it. Queues, parties and matches are untouched. Set it to false to keep this plugin's own lobby features.
places-scope (default default) says which servers share the arenas, jump pads and the portal and PvP regions: default follows the network group in ExyliaLib's config.yml (no group means every server shares), server gives each server its own, global shares with all.
Hotbar commands#
The prefix before the first colon names the click kinds the line answers to (left, right, shift_left, and so on, comma-separated). any or no prefix means every click. The rest is a command line as the library reads one, so console: works as well as player:. Items, names and lore follow the rules in Colours and Messages and languages.
Double jump#
| Setting | Default |
|---|---|
lobby.double-jump-enabled | true |
lobby.double-jump-vertical-power | 0.9 |
lobby.double-jump-forward-power | 0.6 |
lobby.double-jump-cooldown-ms | 500 |
lobby.double-jump-sound | ENTITY_BAT_TAKEOFF|0.5|1.4 |
It needs exyliapractice.lobby.doublejump, which everybody holds by default. It is off for anybody with exyliapractice.lobby.fly, since they are flying instead, and each player can turn it off for themselves in /settings (Double jump).
lobby.effects is a list of potion effects applied in the lobby, written as NAME|LEVEL; SPEED|2 by default.
Visibility#
Every player decides who they see in the lobby, from /settings:
| Setting | Default | Shows |
|---|---|---|
| Show VIP | on | Players with exyliapractice.lobby.vip |
| Show party | on | Your own party members |
| Show others | off | Everybody else |
The defaults for players who have not changed anything are lobby-visibility.show-vip-default, show-party-default and show-others-default; players who already chose keep their own choice.
Sneaking twice quickly in the lobby flips Show others without opening the menu. It is on by default; lobby-visibility.double-sneak-toggle: false turns it off, and lobby-visibility.double-sneak-window-ms (400) is how close together the two sneaks must be.
Anybody with exyliapractice.lobby.bypass is always visible regardless. A player who is not in the lobby (in a match, in a queue-loading state, held by another mode) is handled separately: the lobby hides them from you and hides you from them.
Jump pads#
A jump pad is a set of block locations that launch whoever steps on them.
Run /epc → Jumpads → Create. Chat asks for an id and a display name, then the setup screen opens:
- Name: the display name.
- Launch direction: aim where the pad should throw people, then click, without sneaking. The direction is where you were looking when you confirmed.
- Horizontal power and Vertical power: left click adds 0.1, right click removes 0.1, and Shift-click moves 0.5.
- Enabled: switch it off without deleting it.
- Trigger locations: Add location, then click a block; right click a listed location to remove it. Any number of locations share the pad's direction and power.
- Delete.
| Setting | Default | Meaning |
|---|---|---|
jumpad.launch-cooldown-ms | 500 | Per-player, so one pad cannot be spammed |
jumpad.only-lobby-area | true | Pads only fire for players in a lobby state |
jumpad.launch-sound | ENTITY_SLIME_JUMP|1.0|1.2 |
Portals#
A portal is a region that runs a command, teleports, or both, the moment a player walks into it.
Run /epc → Portals → Create. Each portal has:
- Portal region: a selection wizard for the area.
- Command: typed in chat without the leading slash and run as the player.
- Teleport: left click sets the destination where you stand, right click clears it.
If both a command and a teleport are set, the command runs first. Portals only fire for players in a lobby state, so somebody being carried through by a match is not teleported out of it.
PvP zones#
A PvP zone is a warm-up arena inside the lobby: walk in, get handed a kit, fight, walk out.
Run /epc → PvP regions → Create. Each zone carries:
| Button | What it does |
|---|---|
| Name | The display name |
| Kit | Left click saves the loadout handed out on entry from your own inventory; right click clears it |
| PvP region | Where it is (selection wizard) |
| Enabled | A disabled zone tells whoever enters and does nothing else |
| Combat tag | How long after being hit a player counts as in combat. Left click +1 second, right click −1, Shift-click ±5; never below 1. |
| Flag: build / Flag: break | Whether blocks may be placed or broken inside |
| Flag: drop items | Whether items may be dropped |
| Flag: natural regen | Whether health regenerates |
| Flag: hunger | Whether food drains |
Entering saves the player's previous state, claims them as IN_PVP_ZONE, and hands them the zone's kit. Leaving restores what they were doing and clears the combat tag.
Being hit inside a zone shows a combat-tag boss bar, configured under effects.combat-tag-bossbar in the language's messages.yml with %time% for the seconds left. While the tag lasts the zone's edge is also drawn as a world border for that player (see world-border.enabled).
IN_PVP_ZONE is treated as a lobby-adjacent state throughout: they can join a queue, they see the queue sidebar, and they see the teaser bar. Finding a match pulls them out of the zone.
Command whitelist and join messages
command-whitelist.enabled (default true) blocks commands for players in a match, in a queue or inside a PvP zone, except the ones in command-whitelist.commands (messaging, /leave, /leavequeue, /epc and a few more; namespace:command forms match too). /party cancelgame is always allowed. Players with exyliapractice.bypass.command-whitelist (operators by default) run anything. The lobby itself is not restricted.
join-quit.join-enabled and join-quit.quit-enabled (both true) replace the vanilla join and quit lines with the join-quit.join and join-quit.quit messages in messages.yml (%player_name%).
Something missing on this page? Tell us on Discord