World Management Commands
These commands cover the full lifecycle of Blueprint-managed worlds — from creation through to deletion.
/blueprint create <name>
Creates a new world with the given name.
/blueprint create lobby
Blueprint prefixes the folder name with the configured world-folder-prefix (default: blueprint_). The world is generated and loaded automatically.
Validation: The name must match the world-name-pattern regex defined in config.yml.
/blueprint list [page]
Lists all Blueprint-managed worlds with their current status.
/blueprint list
/blueprint list 2
Each entry shows the world name, whether it is loaded or unloaded, and whether it is locked. Use the optional page number to paginate results.
/blueprint tp <world>
Teleports you to the spawn point of the specified world.
/blueprint tp lobby
The world must be open (loaded) to teleport to it. Use /blueprint open first if needed.
/blueprint open <world>
Loads a world that was previously closed.
/blueprint open lobby
Once open, players can be teleported into the world.
/blueprint close <world>
Unloads a world and disconnects all players currently in it.
/blueprint close lobby
Closing a world saves it to disk and frees server memory. The world data is not deleted. Use /blueprint open to reload it.
You must close a world before cloning or restoring a snapshot into it.
/blueprint lock <world>
Prevents any block placements, block breaks, or entity modifications in the world.
/blueprint lock lobby
Players with the blueprint.bypass.lock permission can still build in locked worlds.
/blueprint unlock <world>
Re-enables block and entity modifications in the world.
/blueprint unlock lobby
/blueprint clone <source> <target>
Duplicates a world asynchronously. The source world must be closed before cloning.
/blueprint close lobby
/blueprint clone lobby lobby-backup
Blueprint cleans up UID and session files from the clone automatically to prevent Minecraft from treating it as the same world.
/blueprint delete <world> [confirm]
Permanently deletes a world and all its files from disk.
/blueprint delete lobby
/blueprint delete lobby confirm
When require-delete-confirmation is enabled in config.yml (the default), you must run the command twice — first without confirm to stage the deletion, then with confirm to execute it.
Deletion is permanent. Blueprint does not keep a copy of the world after deletion. Take a snapshot first if you may need the world later.