Content generated with AI — it may contain mistakes.

Getting started

Introduction

What ExyliaSandBox is: generated PvP worlds, a random-teleport entry, a 1v1 queue, saved kits and a kit room.

ExyliaSandBox turns a Paper or Folia server into a set of disposable PvP worlds. The plugin generates the terrain itself, drops players into it with /rtp, dresses them in a kit they saved beforehand, and throws them back to the lobby the moment they die. Nothing in a sandbox world is meant to last: chunks are not saved, death cancels the vanilla death entirely, and the world can be deleted and rebuilt from the admin panel.

It ships five worlds, five terrain presets, seven database tables, nineteen menus and eighteen commands. Everything an admin configures lives behind one /sandbox menu tree — there is no world list to edit by hand.

What it does

The shape of a session

A kit first

/kitcreator opens the player's slots. They enter one, take gear from the kit room, and /kitsave stores the whole inventory — storage, armour and offhand. How many slots they get is a permission.

In

/rtp picks a world, /rtpqueue waits for an opponent, or they stand on a teleport pad and let the countdown do it. Their inventory is snapshotted and cleared, the kit goes on, and a safe location is searched inside the border.

Fighting

PvP is forced on in every sandbox world, the sidebar shows kills, deaths, KDR, playtime and the border, and the command whitelist keeps them from running anything that is not on the list.

Out

Death, /leavesandbox or a disconnect all end the same way: back to the lobby, inventory restored, the claim released. The death itself is cancelled, so there is no respawn screen and nothing drops.

At a glance

Version documented1.0.3
Minecraft1.21+
PlatformsSpigot, Paper and Folia
RequiredExyliaLib, Chunky, packetevents
OptionalPlaceholderAPI, ExyliaPracticeCore, the Worlds plugin on Folia
DatabaseH2 by default; MySQL, MariaDB, PostgreSQL and MongoDB through ExyliaLib

How this documentation is organised

Getting started installs the plugin and builds the first world and the first kit. Configuring has one page per thing an admin owns: worlds, kits, the kit room and the teleport pads. Systems covers what a player actually does: the RTP and its queue, the teleport commands, and the admin panel screen by screen. Reference is the flat lists — commands, permissions, placeholders, the generated config files, the menus, the tables, the API and the questions that come up.

Where the numbers come from

Every default, message, node and rule on these pages was read from the plugin's source at version 1.0.3. Where a page says a value is not configurable, that is because no key exists for it.

Something missing on this page? Tell us on Discord