Commands

Blueprint has one command, /blueprint, with the alias /bp. Running it with no arguments shows the help listing, which only includes the commands you have permission to use.

Tab completion suggests subcommands, world names, and snapshot IDs. Where it makes sense, it narrows the list: /bp open only suggests closed worlds, /bp unlock only suggests locked ones, and so on.

World names are always converted to lowercase, so /bp tp MyBuild and /bp tp mybuild are the same world.

Summary

Command	Description	Permission
/bp help	Show the commands available to you.	blueprint.command.help
/bp version	Show the Blueprint and server version.	blueprint.command.version
/bp create <world>	Create a new empty build world.	blueprint.command.create
/bp import <world>	Register an existing world folder with Blueprint.	blueprint.command.import
/bp list [page]	List managed worlds and their status.	blueprint.command.list
/bp tp <world>	Teleport to a world's spawn. Players only.	blueprint.command.teleport
/bp hub	Teleport to the hub world. Players only.	blueprint.command.hub
/bp open <world>	Load a closed world.	blueprint.command.open
/bp close <world>	Unload a world.	blueprint.command.close
/bp lock <world>	Protect a world against changes.	blueprint.command.lock
/bp unlock <world>	Remove the protection.	blueprint.command.unlock
/bp clone <source> <target>	Copy a world into a new world.	blueprint.command.clone
/bp rename <world> <new-name>	Rename a world.	blueprint.command.rename
/bp snapshot create [world]	Take a snapshot.	blueprint.command.snapshot
/bp snapshot list [world]	List a world's snapshots.	blueprint.command.snapshot
/bp snapshot restore <world> <id>	Restore a snapshot.	blueprint.command.snapshot
/bp snapshot delete <world> <id>	Delete a snapshot.	blueprint.command.snapshot
/bp delete <world> confirm	Permanently delete a world.	blueprint.command.delete

Commands that do not say "players only" also work from the console.

World names

A world name must match safety.allowed-world-name-regex. The default allows 3 to 32 characters: lowercase letters, numbers, hyphens, and underscores. lobby, spawn-v2, and event_2026 are all valid; ab (too short) and my world (space) are not.

The same rule applies to new names given to create, import, clone, and rename.

Creating and importing

/bp create <world>

Creates a new void world with a 3×3 glass spawn platform at 0, 64, 0. Players spawn standing on it.

• With auto-open-created-worlds: true (the default) the world is loaded straight away, and a player running the command is teleported there.
• With it set to false the world is registered as closed. The platform is built the first time the world is opened.

Fails if a Blueprint world with that name already exists, or if a folder with that name is already on disk in blueprint/.

/bp import <world>

Registers a world that already exists on disk. Use it for worlds downloaded from elsewhere, or made before Blueprint was installed.

1. Copy the world into blueprint/<world>/. The folder must contain region/ with at least one .mca file.
2. Run /bp import <world>.

The world is loaded immediately, build-world rules are applied, and a player running the command is teleported to it. No spawn platform is added and existing terrain is never overwritten.

If the folder on disk uses different capitals, such as blueprint/SpawnV2/, Blueprint finds it and renames it to lowercase for you.

Ungenerated areas stay empty

Blueprint loads every world with its void generator. Chunks that already exist load normally, but walking past the edge of the original map reveals empty void, not new terrain.

Moving around

/bp list [page]

Lists managed worlds, newest first, page-size per page (10 by default). Each line shows the name, status, and folder:

  lobby | OPEN | lobby
  castle | OPEN [LOCKED] | castle
  old-spawn | CLOSED | old-spawn

/bp tp <world>

Teleports you to a world's spawn. The world must be open or locked. If it is marked open but is not loaded yet, for example straight after a restart, Blueprint loads it first.

A closed world must be opened with /bp open before you can teleport to it.

/bp hub

Teleports you to the spawn of the world set as hub-world. This is also where the portal-blocked message points players, since portals are disabled (see How Worlds Work).

Loading and protecting

/bp open <world>

Loads a closed world so players can enter it. Build-world rules are applied every time a world loads.

/bp close <world>

Saves and unloads a world to free memory. Anyone inside is moved to the fallback world first.

Closing a locked world clears the lock. Lock it again after reopening if it still needs protecting.

/bp lock <world>

Protects a world against changes. A closed world is loaded when you lock it. See Locked worlds for exactly what is blocked.

/bp unlock <world>

Removes the lock. The world stays loaded and becomes open.

Copying and renaming

/bp clone <source> <target>

Copies a world into a new world. The copy runs in the background.

1. If the source is loaded, it is saved and unloaded while the files are copied. Anyone in the source world is moved to the fallback world.
2. The copy is given a fresh world identity so Paper treats it as a separate world.
3. The source is loaded again if it was loaded before.
4. With auto-open-clones: true (the default) the new world is loaded straight away. Otherwise it starts closed.

The clone does not carry over the source's level.dat, so it spawns players at the default void spawn point (0, 65, 0) rather than the source world's spawn.

/bp rename <world> <new-name>

Renames a world and its folder on disk. Snapshots move with it. If the world was loaded, players are moved to the fallback world, the folder is renamed, and the world is loaded again under the new name.

Snapshots

See Snapshots for the full picture. In short:

• /bp snapshot create [world] copies the world. Without a world name it uses the world you are standing in.
• /bp snapshot list [world] lists snapshots, newest first, with their UTC timestamps.
• /bp snapshot restore <world> <id> replaces the world with a snapshot, taking a backup first.
• /bp snapshot delete <world> <id> removes a snapshot.

Deleting

/bp delete <world> confirm

Permanently deletes a world's folder and its Blueprint record. Anyone inside is moved to the fallback world first.

Without the word confirm, Blueprint only prints a warning and the exact command to run. You can turn the confirmation step off with safety.require-delete-confirmation: false.

Deleting a world deletes its snapshots

Snapshots are stored inside the world's folder, so they are removed with it. If you might want the build back, copy the world folder somewhere safe before deleting.

Utility

/bp help

Lists every subcommand you have permission for, with its usage and a short description.

/bp version

Shows the installed Blueprint version and the server version.