Build and manage kits
Build a kit, give ranks more kit slots, set a favourite, and publish predefined kits players can copy.
A kit is a whole inventory a player saved: storage, armour and offhand. It sits in a numbered slot per player and dresses them the moment they enter a sandbox world. This page covers building one, how many slots a player gets, and the templates an admin publishes for them to copy.
Before you start#
- The lobby and the kit creator room are set. See Your first sandbox.
- The player is standing in the lobby world: the creator refuses to open from anywhere else, or while the player is already in a sandbox.
Steps#
Open the kit creator
Run /kitcreator. The title shows <used>/<max>, the slots used and the slots the player may have.
Create a kit
Click Create Kit and type a name in chat. The plugin takes the first free slot, teleports the player to the kit creator room and empties their inventory. The real inventory is held aside and given back on the way out.
Take gear from the kit room
The kit room opens by itself five ticks after arriving; /kitroom opens it again. Click an item to take a copy, and arrange your inventory, armour and offhand as you want them.
Save
Run /kitsave. Everything the player wears and carries is written to the slot, and they go back to the lobby with their own inventory. Nothing is saved until they run it.
Check that it works#
Run /kitcreator again: the kit is listed with its name. Run /rtp; with one usable kit you go straight in wearing it. The first kit a player ever saves becomes their favourite automatically.
While in the kit creator a player cannot /rtp, join a queue, /back, /rekit, use /tpa, be picked up by a teleport pad or /leavesandbox. Disconnecting releases the claim and gives their inventory back.
Going further#
Give a rank more kit slots#
The number of slots is a permission tier. The plugin walks down from exyliasandbox.max_kits.100 to exyliasandbox.max_kits.1 and takes the first node the player holds; with none, they get one. The highest node wins, so grant exactly one per group. The limit applies to the title counter, to Create Kit (it refuses with a "maximum number of kits" message when every slot is taken) and to the copy screen, which draws exactly that many rows. See Permissions.
Edit, rename, favourite or delete a kit#
Click a saved kit in /kitcreator to open its options.
| Button | What it does |
|---|---|
| Edit | Re-enters the creator wearing that kit; /kitsave writes it back |
| Favorite | Toggles the favourite star |
| Rename | Chat prompt |
| Icon | Chat prompt for a material name |
| Delete | Removes the kit after a confirmation. Refused for the kit being edited |
The preview in the middle shows the kit as it will be applied.
Setting a favourite clears the star from every other kit of that player. Clicking the star on the current favourite turns it off and leaves them with none, which is what a teleport pad refuses on.
Which kit is used, when#
| Entry | Kit |
|---|---|
/rtp, /rtpqueue, /rtpqueuefast, /back, /tpa with two or more usable kits | The one they pick from the kit list |
| Any of those with exactly one usable kit | That one, with no menu |
| Any of those with none | Refused with a line telling them to run /kitcreator |
| Any of those from inside a sandbox world | The kit they are already wearing |
| A teleport pad | The favourite, and nothing else |
/rekit | The kit they are already wearing, re-applied |
Only kits with contents are listed. An empty slot is never offered.
Predefined kits#
A predefined kit is an admin-built template stored server-wide with an id, a name, a description and an icon. Players never wear one directly: they copy it into one of their own slots, overwriting what was there.
Publish one#
Open the list
Run /sandboxadmin and click Predefined kits (or run /sandboxadmin predefinedkits).
Create the kit
Click Create Kit and type a name. The id is a slug of that name and never changes on rename. You enter the same kit creator players use.
Build and save
Take gear from the kit room and run /kitsave. You return to the list.
Polish it
Click the kit to open its editor: Edit contents re-enters the creator, Rename, Icon and Description are chat prompts, and Delete asks for a confirmation.
How players copy one#
/predefinedkits (or Predefined kits in /kitcreator) opens the list. Clicking a template shows the player's own slots: green and empty, or amber and glowing with a kit already there ("Click to overwrite it"). Clicking a slot copies the template in. /predefinedkits <kit> <slot> does the same in one line, with no screens.
Linking a PracticeCore kit#
With ExyliaPracticeCore installed, the template editor has a PracticeCore kit button. It lists every enabled PracticeCore kit; clicking one links it, clicking the linked one unlinks it. A linked template shows and copies PracticeCore's items as they are right now, nothing is copied into this plugin, and Edit contents refuses with a line saying to edit it in PracticeCore. Unlinking brings back the template's own items, which were never touched. Without PracticeCore the button says it is not installed, and a linked template resolves to an empty kit that no player can copy.
What is stored
One row per kit in sandbox_player_kits, keyed <uuid>:<slot>, holding the storage contents, the armour, the offhand, the name, the icon and the favourite flag. Predefined kits have the same shape in sandbox_predefined_kits, keyed by their slug; the PracticeCore link is its practice_kit column.
Kits are cached per player and written back when they disconnect. The active slot a player is wearing is not stored: a restart leaves nobody wearing anything.
Something missing on this page? Tell us on Discord