Reference

Menus

The nineteen screens: what opens each one, what its buttons do, and which folder is safe to edit.

Nineteen menu files ship, in two folders that behave differently.

Folder	Behaviour
`menus/user/`	Written once on the first run and never overwritten. Yours to edit
`menus/admin/`	Rewritten from the jar on every start. Each file says so at the top

The player screens

`user/world_selector.yml`

Opened by /rtp and /rtpqueue. A paginated list of every configured world.

Each row's stack size is the number of players in that world, and the glow is on only when it is READY. Clicking a world runs an action the row carries: the RTP branch or the queue branch. A world that is not ready carries an empty action, so the click does nothing at all.

`user/kit_selector.yml`

One file, five uses: picking a kit for /rtp, for a queue, for the fast queue, for /back and for a /tpa. Only kits with contents are listed, sorted by slot. What the click does is decided by whichever flow opened it.

`user/kit_creator.yml`

/kitcreator. The player's slots, with the title showing <used>/<max>. + NEW KIT takes the first free slot; PREDEFINED KITS opens the templates; a saved kit opens its options.

`user/kit_options.yml`

One kit: Edit, Favorite, Rename, Change Icon, Delete, and a preview of the kit itself.

`user/kitroom.yml`

The shelf. Two sections in one screen: the items grid on top and the categories along the bottom. The selected category is drawn glowing and green, the rest grey.

This one has no `actions` in the file

The category buttons and every item are bound to their actions in code rather than in the YAML, so the file carries no actions: key for them. Moving them around is fine; there is nothing to copy.

`user/predefined_kits.yml`

The admin templates that have contents. Clicking one opens the copy screen.

`user/predefined_kit_copy.yml`

One row per slot the player is allowed, drawn from two templates: an empty slot in green, and a taken slot in amber, glowing, showing the kit already there and saying it will be overwritten. Clicking copies.

The admin screens

`admin/admin.yml`

The hub. See The admin panel.

`admin/world_list.yml`

Every world, paginated, with its type, status, player count, biome and border radius. Left-click configures, right-click teleports. CREATE WORLD, IMPORT WORLD and Reset to Defaults sit at the bottom.

`admin/world_config.yml`

One world's draft: icon, name, biome, generation preset, border, gamerules, teleport, players, save and delete. Nothing is written until SAVE WORLD.

`admin/world_settings.yml`

The difficulty cycle and thirteen gamerule toggles, each with its own icon and an ENABLED / DISABLED state.

`admin/world_players.yml`

One head per player in the world, showing game mode, health, level and coordinates. Clicking one teleports you to them.

`admin/tp_region_list.yml`

Every teleport pad, with its world, interval, target and spread. Left-click edits, right-click deletes with no confirmation. CREATE TP REGION at the bottom.

`admin/tp_region_editor.yml`

One pad: name, bounds, target world, interval, spread radius, save, and a delete in the last slot — also without a confirmation.

`admin/predefined_kit_list.yml`

The templates. Clicking one opens its editor; + CREATE KIT starts a new one.

`admin/predefined_kit_editor.yml`

One template: change icon, rename, description, edit contents, and delete through a confirmation.

`admin/kitroom_category_list.yml`

The kit-room categories. Left-click opens the grid, right-click picks an icon, shift-left deletes with no confirmation. + CREATE CATEGORY and Reset to Defaults at the bottom.

`admin/kitroom_category_editor.yml`

A drop-anything grid, forty-five slots, pre-filled with the category's items.

This screen does not save

The grid opens and accepts items, but nothing writes it back. Closing it discards every change. Use Reset to Defaults on the category list to get the shipped catalogue back.

`admin/confirm.yml`

The shared confirmation screen. Four things go through it: resetting the kit room to defaults, resetting the worlds to defaults, deleting a world and deleting a predefined kit. Deleting a teleport pad and deleting a kit-room category do not.

Actions you can use elsewhere

Four actions are registered and used by none of the shipped screens, so they are free for your own menus, hotbar items or NPCs:

Action	What it does
`sandbox:open_world_selector`	Opens the world list in RTP mode
`sandbox:open_kitroom`	Opens the kit room
`sandbox:join_no_kit <world>`	Joins that world's queue with no kit chosen. The player still needs one saved
`sandbox:leave_queue`	Leaves the queue

Something missing on this page? Tell us on Discord