Content generated with AI — it may contain mistakes.

ExyliaSandBox/ConfiguringguideUpdated in v1.2.0

Create and manage worlds

Create a sandbox world, import an existing one, change its terrain, border and gamerules, and delete it.

Page 4 of 247 min read

A sandbox world is a row the plugin keeps in its database, plus a folder it owns. You create, edit and delete worlds from /sandboxadmin → Worlds; there is no world list in a config file. Five worlds come ready (desert, plains, snowy, mushroom, badlands).

Before you start#

  • ExyliaSandBox and Chunky are installed and the server has started once. See Install ExyliaSandBox.
  • You have exyliasandbox.admin.
  • Creating a managed world pre-generates it, and the server stops when the pre-generation finishes. Do it in a maintenance window.

Steps#

Open the world list

Run /sandboxadmin and click Worlds. Left-click a world to edit it, right-click to teleport into it.

Start a new world

Click Create World. The chat asks for the world ID (lowercase, no spaces; one already in use is refused) and then a display name, which can carry colours. Confirm the summary.

Shape it

The world screen opens with your new world as a draft. Click Biome to type a biome, Generation to cycle through the five terrain presets, Border to set its size, Icon to choose the item that represents it in the lists, and Gamerules for the rules. Nothing is stored yet.

Save

Click Save. The world is created, Chunky starts generating it and the list shows its progress as PREGEN <percent>. When the last pre-generation in the queue ends, the server stops. Start it again.

Check that it works#

After the restart, /sandboxadmin → Worlds shows the world with its glow. Right-click it to teleport in and look around. Then run /rtp as a player and pick it. Only a ready world accepts players; one still generating is shown without its glow and clicking it does nothing.

Going further#

Import a world you already have#

Click Import World in the world list. The chat asks for the exact folder name, which must sit in the server's world folder and contain a level.dat, then an ID and a display name. Click Save on the world screen. Terrain, biome and generation are ignored for an imported world (the screen shows N/A), and the plugin never changes or deletes its terrain.

Change the border#

Border in the world screen is the diameter; the number shown for the world is the radius, half of it. The border is always centred on 0, 0. Left-click adds 500, right-click removes 500 (never below 100), and shift-left-click types a number. Click Save to apply it. Players are placed at least rtp.border-margin blocks inside it (20 by default), so a 3000-block border lands players within a 1480-block radius.

Gamerules and difficulty#

Gamerules in the world screen opens thirteen toggles and the difficulty. They are applied every time the world is loaded. Click one to switch it, then go back and click Save.

Difficulty cycles PEACEFUL → EASY → NORMAL → HARD. Two things are not toggles: PvP is forced on in every sandbox world, and keepInventory is forced off. Death is cancelled before vanilla drops anything, so nothing is lost either way.

Disable powder snow does not survive a restart

The toggle works while the world stays loaded, but it is not written to the world's stored settings, so after a restart it is back to its default. Every other toggle is saved.

See who is inside#

The world screen's Players button lists the players currently in that world. Click one to teleport to them.

Delete a world#

Click Delete at the bottom of the world screen and confirm. A managed world's folder is deleted with it; an imported world keeps its folder and only loses its row. Reset to defaults in the world list removes every world configuration and restores the five default ones, after a confirmation; the confirmation warns that active worlds are disabled.

Managed and imported worlds
MANAGEDIMPORTED
Folderexylia_sandbox_<id>, created by the pluginan existing folder you name
Terrainthis plugin's generator, from a presetwhatever is already there
On creationthe folder is deleted and rebuiltnothing is touched
On deletionthe folder is deletedthe row is removed, the folder stays
Biome and generationeditableignored; the screen shows N/A

Both kinds get the same border, gamerules and PvP. A world moves through CREATING, PREGENERATING and READY, or lands on UNAVAILABLE when it could not be loaded at all. Only READY worlds accept players.

The generator and the five presets

The generator turns every vanilla stage off (noise, surface, bedrock, caves, decorations, structures and mob spawning) and writes the chunk itself. A managed world has no caves, ores, ravines or villages unless a preset's decoration pass puts something there.

Height is a base plus a gentle two-octave undulation, with a mountain lift that only appears in the upper part of the noise range and adds at most ten blocks. Under it comes the preset's layer stack, then bedrock at the bottom. Below y = minY + 40 the fill becomes deepslate regardless of the preset.

PresetBase heightLayers, top downDecoration
Plains74grass block, 3 dirt, stoneshort grass, fern, poppy, dandelion, oak trees
Desert722 sand, 4 sandstone, stonecactus, dead bush
Snowy783 snow block, 3 dirt, stonepacked ice spikes, blue ice
Mushroom74mycelium, 3 dirt, stonebrown and red giant mushrooms
Badlands863 red sand, 4 red sandstone, then eight terracotta bands, stonecactus

Decoration chances are fixed: 6% for an oak tree per eligible column, 7% and 6% for the two mushrooms, 10% for grass and ferns, 1.8% for powder snow, 1.5% for blue ice and dead bush, 0.8% for a flower, 0.4% for a cactus and 0.3% for an ice spike. Trees and mushrooms only spawn away from chunk edges, because a decoration pass cannot reach into the neighbouring chunk.

heightVariation and stoneVariants are written into every world's generation record, but nothing reads them. To change a preset's terrain, change its base height, layer stack or feature list.

Gamerule toggles
ToggleGamerule or flag
mob_spawningdoMobSpawning
spawn_mobs, spawn_animalsthe world's spawn flags
mob_griefingmobGriefing
daylight_cycledoDaylightCycle
weather_cycledoWeatherCycle
tile_dropsdoTileDrops
entity_dropsdoEntityDrops
show_death_messagesshowDeathMessages
immediate_respawndoImmediateRespawn
announce_advancementsannounceAdvancements
disable_item_dropsthis plugin's own: cancels item drops in the world
disable_powder_snowthis plugin's own: cancels powder snow damage and placement
Pre-generation and chunks

When a managed world is created, the plugin asks Chunky to generate a square out to the border radius and waits. Two marker files in the world folder carry the state across restarts: .pregen_pending while a pre-generation is unfinished and .sandbox-generated once the world is complete. The second one, not level.dat, is what the plugin checks to decide whether a world already exists.

Pre-generations run one at a time. A pre-generation stopped before its last chunk does not count as finished. /chunky pause keeps the queue waiting until /chunky continue or the next start. /chunky cancel lets the next world start, and the cancelled one starts over on the next start. A world unloaded during its pre-generation is UNAVAILABLE until the next start.

If Chunky is missing or reports an API version this plugin does not know, pre-generation is skipped: the world is marked complete straight away and generates chunks as players walk into them.

Chunk saving is off in every ready sandbox world and spawn chunks are not kept in memory, so nothing a player builds, breaks or drops survives a restart of that world. Players inside a world are teleported out when the plugin unloads it at shutdown.

Something missing on this page? Tell us on Discord