Getting startedguide

First steps

The nodes a first group needs, a first world, a first kit, and the round trip a player makes.

The nodes a player needs

Nothing is declared in plugin.yml. There is no permissions: block, so no node carries a default: — an operator passes every check because operators pass every check, and everybody else starts with nothing.

A group that can play needs, at least:

exyliasandbox.command.rtp
exyliasandbox.command.rtpqueue
exyliasandbox.command.rtpqueuefast
exyliasandbox.command.leavertpqueue
exyliasandbox.command.leavesandbox
exyliasandbox.command.back
exyliasandbox.command.tpa
exyliasandbox.command.rekit
exyliasandbox.command.kitroom
exyliasandbox.command.kitcreator
exyliasandbox.command.predefinedkits
exyliasandbox.max_kits.3

exyliasandbox.admin is the only node an administrator needs: it covers /sandbox, every button in every admin screen, and every action behind them. The full list is on the Permissions page.

`max_kits` is a tier, and the highest one wins

The plugin walks down from exyliasandbox.max_kits.100 to .1 and takes the first node the player holds. A player with none gets one slot. Grant exactly one node per group; a player holding .3 and .5 gets five.

A first world

Five worlds ship seeded — desert, plains, snowy, mushroom and badlands, all with a 3000-block border. They are created and pre-generated on the first boot, which is what triggers the restart. If that is enough, skip to the next section.

Open the panel

/sandbox → MANAGE WORLDS. Left-click a row to configure it, right-click to teleport into it.

Create one

CREATE WORLD asks for an id and a display name in chat, then opens the world screen. Nothing is written until you press SAVE WORLD.

Pick the terrain

GENERATION cycles the five presets — Plains, Desert, Snowy, Mushroom, Badlands. BIOME takes a biome id. BORDER is the diameter: left-click adds 500, right-click removes 500, shift-left types a number.

Save, and wait for the restart

SAVE WORLD creates the folder and queues the pre-generation. When Chunky finishes the last queued world, the server shuts down. Bring it back up and the world is READY.

Importing an existing world instead is IMPORT WORLD: it asks for the folder name, checks it holds a level.dat, and from then on the plugin never touches its terrain or deletes it.

A first kit

A player with no kit cannot enter a sandbox at all — every entry point refuses with queue.no-kit.

Enter the creator

/kitcreator opens the slot grid, %current_kits%/%max_kits% in its title. + NEW KIT takes the first free slot and teleports the player into the kit-creator room with an empty inventory.

Take the gear

The kit room opens by itself a moment later, or with /kitroom. Click to take a copy — the shelf never empties. Q drops a stack, F puts it in the offhand, shift-click takes a full stack.

Save it

/kitsave stores the whole inventory: storage, armour and offhand. The first kit a player saves becomes their favourite automatically.

Or copy a template

PREDEFINED KITS in the creator, or /predefinedkits, lists what the admins built. Clicking one shows the player's own slots; clicking a slot copies the template into it, overwriting whatever was there.

The favourite is what a teleport pad uses

Standing on a teleport pad requires a favourite kit and nothing else — there is no kit menu in that flow. A player with no favourite is told so and left standing. The star in Kit options toggles it, so clicking the current favourite leaves them with none.

The round trip

In

/rtp opens the world list; the stack size on each row is the number of players inside it. Picking a world with two or more usable kits opens the kit list; with exactly one it goes straight in.

Arriving

Two ticks after the teleport the player is reset — survival, no flight, no potion effects, full health, food and saturation, fall distance cleared — the sidebar appears and the kit goes on.

Out

/leavesandbox, or death, or a disconnect. All three restore the inventory, hide the sidebar, end the playtime session and release the claim. Death is cancelled outright: nothing drops, there is no respawn screen, and the death location becomes the /back point.

What to check afterwards

/sandbox → MANAGE WORLDS shows each world's status and player count live.
The row's right-click teleports you in without claiming a session, which is how an admin watches.
%exyliasandbox_total_players% and %exyliasandbox_queue_total% put both numbers on a lobby board.
The command whitelist in config.yml decides what a player may run while inside a sandbox world or while queued. Everything else is refused with general.command-blocked unless they hold exyliasandbox.bypass.blocked-commands.

Something missing on this page? Tell us on Discord