Configuration
Blueprint's settings live in plugins/Blueprint/config.yml, created on first start. There is no reload command, so restart the server after editing it.
Default file
storage:
type: yaml
worlds:
container-directory: "blueprint"
page-size: 10
fallback-world: "world"
hub-world: "world"
auto-open-created-worlds: true
auto-open-clones: true
close-on-restart: false
snapshots:
enabled: true
auto-backup-before-restore: true
max-per-world: 25
safety:
require-delete-confirmation: true
allowed-world-name-regex: "^[a-z0-9_-]{3,32}$"
messages:
prefix: "<gradient:#00aaff:#0066ff><bold>Blueprint</bold></gradient> <dark_gray>»</dark_gray> "
storage
| Option | Default | Description |
|---|---|---|
type | yaml | How Blueprint stores world records. yaml is the only supported value. See Data Files. |
worlds
| Option | Default | Description |
|---|---|---|
container-directory | blueprint | The folder that holds all worlds. It must match settings.world-container in bukkit.yml. Blueprint uses it to check your setup and warn in the console if they differ; changing it here does not move anything. |
page-size | 10 | Worlds shown per page of /bp list. |
fallback-world | world | Where players are sent when the world they are in unloads, and where they land if they log in inside a Blueprint world. If this world is not loaded, the server's first world is used. |
hub-world | world | Where /bp hub sends players. If you remove this line, it defaults to fallback-world. |
auto-open-created-worlds | true | Load new worlds from /bp create straight away and teleport the creator there. When false, new worlds start closed. |
auto-open-clones | true | Load the new world from /bp clone as soon as the copy finishes. When false, clones start closed. |
close-on-restart | false | When true, every world that was open or locked is marked closed on startup instead of being reloaded. See Restarts. |
Separate hub and fallback worlds
fallback-world is where players are dumped when something unloads. hub-world is where they choose to go. Most servers point both at the same lobby, but you can split them, for example a quiet holding area as the fallback and a showcase world as the hub.
snapshots
| Option | Default | Description |
|---|---|---|
enabled | true | When false, /bp snapshot create is refused. Existing snapshots can still be listed, restored, and deleted. |
auto-backup-before-restore | true | Take a pre-restore- snapshot of the current world before every restore, so the restore can be undone. |
max-per-world | 25 | The most snapshots a world keeps. The oldest are deleted when a new one is taken. 0 means unlimited. See Pruning. |
safety
| Option | Default | Description |
|---|---|---|
require-delete-confirmation | true | Require the word confirm at the end of /bp delete. When false, /bp delete <world> deletes immediately. |
allowed-world-name-regex | ^[a-z0-9_-]{3,32}$ | A regular expression every new world name must match. Names are lowercased before they are checked. |
Keep world names file-system safe
World names become folder names. If you loosen the regex, keep it to characters that are safe in folder names on your host, and never allow /, \, or ...
messages
| Option | Default | Description |
|---|---|---|
prefix | Blue "Blueprint »" gradient | Put in front of every Blueprint chat message. Uses MiniMessage formatting. Set it to "" for no prefix. |
The message text itself is not configurable.