Create and manage a plot
Choose a size
Section titled “Choose a size”| Size | Width in chunks | Play-area width in blocks |
|---|---|---|
| Small | 8 | 128 |
| Medium | 16 | 256 |
| Large | 32 | 512 |
| Gigantic | 64 | 1,024 |
Use /plot create <size> to create one. These measurements describe the play area, not a promise of unlimited runtime or entity capacity. Plots use Plains biomes initially; intentional biome changes can be made with the available world operations.
Name, icon, and discovery
Section titled “Name, icon, and discovery”/plot name <name> changes the current plot’s name. /plot icon uses the held item for its listing icon. These are owner-managed metadata. Hold the intended item and check the resulting listing in My Plots. /join <id> enters a plot by ID; /p is an alias for /plot.
Add codespace layers
Section titled “Add codespace layers”In authorized Dev mode:
/plot codespace add/plot codespace add blue -c -l/plot codespace removeAn added layer can use a color and optional compact (-c) and line (-l) styles. Combine the flags for compact lines. Tab completion lists supported colors. Removal operates on the layer selected by your position; ordinary removal protects occupied code. -f requests forced removal and can destroy code on that layer. Use it only when you intend that removal.
/plot glitch supplies a tool for manual destruction inside codespaces. This is an editing tool, not a runtime operation or a general undo feature.
Delete your plot
Section titled “Delete your plot”While on your own plot, use /plot delete. Read the Confirm/Cancel dialog before confirming. Only the owner can delete it. Leaving the plot invalidates the confirmation.
Confirmation removes the plot from listings and joins, stops its program, and returns its players to the lobby. The implementation retains underlying data for recovery, but there is no ordinary-player restore command: do not treat deletion as a reversible editor action.