Staging a Chronicle World 📦🌎
A Chronicle needs more than a splendid name and dramatic lore. It also needs an actual Bedrock world, preferably one containing land.
The replacement world is uploaded as a .mcworld package and attached to the intended Chronicle through the protected Chronicle administration workflow.
What happens during staging
The system stores the upload outside the public web directory and records:
- original filename
- file size
- uploader
- upload timestamp
- SHA-256 checksum
- validation status
- approval status
- immutable audit history
The archive is inspected safely. A valid package must contain a recognizable Bedrock world structure, including level.dat.
What the validator blocks
The staging service rejects packages with problems such as:
- malformed archives
- missing
level.dat - dangerous path traversal entries
- unsupported archive layouts
- suspicious or excessive extraction sizes
- checksum changes after approval
- attempts to overwrite an approved package silently
In technical terms, the package must be a world, not a zip file wearing a fake mustache. 🥸
Validation is not approval
A world that passes automated validation is only valid, not approved.
An authorized administrator must review and approve the staged package separately. Approval records the package checksum, approver, timestamp, and audit reason. Once approved, the package contents and checksum are locked.
Replacing an approved package requires an explicit revocation or supersession record. Nothing vanishes down the audit-history trapdoor.
Staging does not affect the live world
Uploading or approving a staged world does not stop BDS, move directories, change PvP, activate a Chronicle, or replace the current world. It simply prepares the next world behind several very sturdy doors. 🚪🚪🚪