Version 4.0.0 reworks the parts of BuildSystem that were hardcoded until now. World statuses and navigator categories are yours to define, worlds can be downloaded as single-player saves, physics can be controlled per behaviour, and the developer API has been rewritten. Existing data and configs are migrated automatically on first start.
Requirements
- Java 25
- Minecraft 26.1 or newer
What's new
- Custom world statuses. Statuses are no longer a fixed list. Create, rename, recolour, reorder and delete them in-game with /setup.
- Navigator categories. The public/archive/private tabs are now categories you define yourself, grouping worlds by visibility and status. Each one gets its own /worlds <category> command.
- Navigator layout editor. Drag categories and the settings button into the navigator slots you want.
- World downloads. /worlds download <world> packs a world into a single-player save and sends an expiring link. Served locally or through S3. Off by default.
- Per-world physics exceptions. Keep physics off but allow, say, fluid flow or falling blocks in one world.
- Custom icons and head textures for worlds, folders and categories, pi on creation, /worlds saveTemplate, a configurable void-worldblock, per-option /settings permissions, and EssentialsX warps now load unloaded worlds.
Fixed
A long list, including a rename bug that could delete a world when the copy failed halfway, several backup bugs (first backup of a world, backups after
/buildsystem
reload, the default world backing up every other world), and bulk imiled worlds. The full list is in the release notes.
Before you update
- Your config, messages and world data are migrated automatically on fianyway.
- If you run plugins built on the BuildSystem API, they need to be updated for 4.0.0. The migration guide in the docs covers the changes.
Links
Release notes:
https://github.com/thomasmny/BuildSystem/releases/tag/4.0.0
Docs:
https://buildsystem.eintosti.de
