Changelog

• World downloads: /worlds download <world> (buildsystem.download) packs a world into a single-player save and sends a clickable, expiring link. Since Paper 26.1 a world is a dimension of the main level and has no level.dat of its own, so the export rebuilds the save layout the client expects. An animated action-bar progress bar tracks the packing. Off by default - enable under world.download in config.yml. Links are pinned to the client that uses them first, rate limited, size and storage capped, and exports never include player data.

• Configurable void-world block: Choose the block placed at the spawn of newly generated void worlds (world.void-block.enabled / material, default GOLD_BLOCK), or disable it entirely. The block is only placed on initial generation, never on later loads, imports, or renames, and it never overwrites an existing block.

• Per-world physics exceptions: Physics control is no longer all-or-nothing. Right-click the physics toggle in /worlds edit to open the exceptions menu (same buildsystem.edit.physics permission) and re-allow individual behaviors (block updates, connections, falling blocks, fluid flow, leaf decay, growth, spreading, block forming, block fading) while the world's physics stay disabled. Values persist per world; the world.disabled-physics config section is replaced by per-category defaults under world.defaults.physics-exceptions (existing configs migrate automatically).

• Custom world statuses: Create, restyle, reorder and delete world statuses in-game (/setup → World Statuses) or via statuses.yml. The status editor is a drag-and-drop layout screen, the same as the navigator editor, so you also decide exactly where each status sits in the /worlds setStatus picker. Built-in defaults can be restyled or deleted (never the last remaining status). Assign with dynamic permission buildsystem.setstatus.<id>.

• Navigator categories: Group worlds by visibilities and statuses into customizable tabs. A world is listed in every category that groups it, supporting overlapping tab listings. Any category can be deleted, including the last one. The navigator then stays empty until you reset to defaults. Create with dynamic permission buildsystem.create.category.<categoryId>; admins with create bypass can create in any category.

• Per-category commands & visibility: Every category (built-in or custom) gets a /worlds <category> shortcut, generated from the navigator instead of the old hardcoded archive/private/public. The dynamic permission buildsystem.navigator.category.<categoryId> (granted by default) governs both the shortcut and whether the category shows in the navigator, so denying it hides a category and disables its command together. A real subcommand always wins a name clash, so a category named like a command never shadows it.

• In-game /setup GUI: Redesigned configuration hub branching to editors for default world-type icons, world statuses, and the navigator layout. Features a 16-color concrete block/dye picker, scrollable/filterable item picker, player-head skull texture support, and confirm/reset controls. "Reset to defaults" restores statuses, categories, and default world-type icons.

• Navigator Layout editor: Integrated editor (/setup → Navigator Layout) that manages categories and arranges where each category and the settings button appear in the inventory navigator. Click to drag/drop, drop outside to remove, drop on the delete target (textured skull) to delete the category, right-click to edit, and create categories directly. Includes automatic inventory snapshotting and restore safeguards. The status editor (/setup → World Statuses) is built on the same screen.

• Per-world, folder, and category icons: Set a custom icon material or skull texture for each world, folder and category (e.g. %viewer% for the viewer's own head). In the world editor (/worlds edit), click the world item to pick a material, or right-click a player-head icon to set its texture (buildsystem.edit.icon).

• Custom World Seed: Shift-click a predefined world type in the create menu to set its seed. Numeric input is used as the literal seed, other text hashes to a long, and a blank entry falls through to a random seed.

• Pinned Worlds: Force specific worlds to stay at the top of navigator lists (buildsystem.edit.pin).

• Runtime Templates: Copy active worlds to templates/ using /worlds saveTemplate <world> [templateName] (buildsystem.savetemplate).

• Granular Options: Limit /settings toggles with individual permission nodes (buildsystem.setting.<option>).

• Dynamic Builder Access: Restrict template/generator creation dynamically with buildsystem.create.template.<name> and buildsystem.create.generator.<name>.

• Permission Whitelist: Limit /worlds setPermission assignments using world-permission-whitelist in config.yml.

• API Additions: World lifecycle events, folder events, backup events, dynamic WorldService.importWorlds() bulk load, typed WorldData access through a WorldDataKey<T> catalog (data.get(WorldDataKey.PERMISSION) / data.set(WorldDataKey.BLOCK_BREAKING, true)), registries for statuses and categories, and per-status picker placement (BuildWorldStatus#getStatusSlot() / isShownInStatusMenu()).

• System Requirements: Requires Java 25 and Minecraft 26.1 or newer.

• Configuration Versioning: Automatic migration of config.yml and messages.yml on load. Built-in statuses seeded automatically from legacy keys.

• Navigator commands: The fixed /worlds archive, /worlds private and /worlds public subcommands were replaced by per-category /worlds <category> shortcuts (see Added). Existing setups keep working, because the three built-in categories still answer to those names.

• World creation limits: world.max-amount.* is now world.limits.*, and the value is the default number of worlds one player may create of that visibility rather than a count of every world on the server. A buildsystem.create.<visibility>.<amount> node overrides it, buildsystem.admin ignores it, and worlds are counted per visibility, so a private-world limit no longer blocks public ones. Values carry over automatically.

• API Overhaul:

  • Moved BuildWorldManipulationEvent to de.eintosti.buildsystem.api.event.world.

  • World creation and importing are now fluent (WorldService.newWorld() / importWorld()).

  • Type<T> renamed to Property<T>.

  • BuildWorld.getWorld() returns Optional<org.bukkit.World>.

  • BuildWorldStatus and NavigatorCategory are now interfaces managed via registry.

  • Per-world private boolean replaced with Visibility (EVERYONE/ADDED_PLAYERS).

  • Plugin instances registered through Bukkit's ServicesManager.

• Removed (API): Pruned BuildWorld.setLoaded(boolean), BuildWorld.asProfileable(), WorldData.getConfigFormat(), WorldData.getAllData(), and public registration entrypoints on BuildSystemProvider.

• Dropped Configuration Flags: Removed legacy toggles per-option-permissions and restrict-template-access.

• Compatibility & Safety:

  • Paper/Spigot GameRule compatibility via XGameRule class bridge.

  • Thread-safety: block checks, world-rename registry mutations, and skull profile callbacks forced to run on the main server thread.

  • Path-traversal guards added to template and world directory resolution, plus a containment check on the public WorldService.newWorld(String) and on deletion so a name resolving outside the world container is rejected (#481).

• Backups: Backup thread pool bounded, credentials validated on load, and SFTP exceptions thrown cleanly as IOException.

• Backup credentials from the environment: AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and BUILDSYSTEM_SFTP_PASSWORD can supply backup credentials instead of config.yml, and take precedence when set. Previously these were documented but could not work, because config.yml was required to hold a value before the environment was ever consulted.

• Default world backups: The server's default world no longer folds every other world into its own backup. Since Paper 26.1 all worlds live inside it, so its backup now covers only its own data. Restoring it in-place is refused - that would have deleted every world on the server.

• Local backups: The first backup of any world failed because its per-world directory was never created.

• Backups after a reload: /buildsystem reload swapped the backup backend but left recently-used worlds bound to the old one, which had already been closed - their next backup failed against a shut-down S3/SFTP client and a deleted temporary directory. Backups also no longer overlap on the same world, so the per-world retention limit cannot be overshot by two backups running at once.

• World Loading: A world whose stored difficulty is unreadable no longer disappears on load. It falls back to Peaceful, like the plugin's other world enums. World settings missing from disk (block protections, and the last-edited/loaded/unloaded timestamps) now load with the same defaults a freshly created world gets, instead of coming back disabled or stamped at epoch zero.

• World Renaming: Fixed rename persistence and the parsing done when a renamed world is unloaded.

• World renaming could destroy a world: The directory copy logged failures instead of reporting them, so a rename that only partly copied the world went on to delete the original and reported success. The copy now fails loudly, the original is kept, and the player is told (worlds_rename_error, a message that existed but was never sent). The same silent-copy problem made a failed template save report success and let a world be created around a half-copied template (new worlds_template_creation_error).

• /night: Running it on an unknown world reported the /day error message instead of its own.

• Scoreboard: The per-second refresh read the player's world and its BuildSystem data off the main thread, and recomputed every placeholder once per scoreboard line rather than once per refresh. It now resolves them once, on the main thread.

• settings.date-format: Timestamps are formatted with java.time instead of the legacy formatter. Common patterns such as dd/MM/yyyy are unaffected; a pattern the new formatter cannot parse now logs a warning and falls back to dd/MM/yyyy instead of erroring on every render.

• Missing message keys: A missing key used for item lore is now reported in the console, like a missing key used for a name already was. Previously it rendered as empty lore with no warning at all.

• Bulk world import: A world that failed to import is now reported (new worlds_importall_world_failed message) rather than silently reducing the count, and WorldService.importWorlds() logs every skipped or failed world instead of discarding the outcome. A world that throws mid-import no longer strands the run, which previously left the "import already in progress" flag set until restart and blocked every later bulk import.

• Import flags: /worlds import -t <type> with an unknown type, and /worlds importAll -g <generator> with an unknown generator, were silently ignored - the world imported with the default instead, and nothing said so. Both now report the bad value (new worlds_import_unknown_type) and stop.

• Navigator after "reset to defaults": Resetting statuses or categories discarded the custom ones without updating what referenced them, so folders in a discarded category vanished from the navigator - along with the worlds inside them - until the next restart. Resetting now cascades exactly as deleting one does.

• World Deletion: A world directory that fails to delete is now reported instead of silently leaving files behind.

• Game Rules: Game-rule names updated to the current API.

• Disable Interactions: The setting now covers every interactable block. It previously used a hand-maintained block list that had fallen behind Minecraft, so newer blocks (crafter, trial spawner, vault, decorated pot, copper doors/trapdoors/bulbs, pale oak doors and gates, creaking heart) could still be opened with the setting enabled.

• GUI Fixes: Click matching hardened against the target menu only (preventing inventory clicks from triggering button actions), duplicate listener registrations fixed, and placeholder substitutions converted to literal matches.

• Performance Optimizations:

  • Cached navigator armor stands, eliminating per-tick entity scans.

  • Removed per-tick location allocations in NoClip checks.

  • Reduced memory allocation in scoreboard rendering, color processing, and the template menu.

Upgrading from BuildSystem 3.x to 4.0.0? Please read our comprehensive Migration Guide for detailed instructions on:

• Automatic database & file conversion.

• Configuration updates and removed flags.

• New dynamic permission nodes.

• Language file (messages.yml) changes.

• Developer API upgrade guidelines and package moves.