Skip to content

v26.2-0.17.0

Choose a tag to compare

@tpwalke2 tpwalke2 released this 06 Aug 10:55
· 101 commits to releases/26.2 since this release
8a0e440

Summary

Breaking Changes

  • Sign storage is now region-sharded. Instead of one signs.json per world, sign data is split into per-region files under bluemapsignmarkers/<level>/<dimension>/. This happens automatically on first boot after upgrading — your old signs.json is renamed as a backup, not deleted. (#109)
  • Signs removed from unloaded chunks now get cleaned up on load. If a sign's block is gone when its chunk loads (e.g. its region file was deleted or regenerated outside the mod), the matching marker is now removed instead of lingering on the map. (#110)
  • Downgrading is not supported. Once you upgrade and the mod migrates your sign data to the region-sharded format, going back to v26.2-0.16.0 or earlier is unsafe — older versions only read the old signs.json, which will be stale.
  • Back up before you upgrade. As good practice, back up your sign storage folder and config/bluemapsignmarkers/BMSM-Core.json before installing this release.

Fixes

  • Fixed a bug where upgrading from an old world save could crash the migration or silently drop signs when a sign's marker-group prefix could no longer be found. (#138)
  • Fixed a bug where one invalid or missing marker-group prefix in your config could stop all sign processing. Invalid groups are now caught once at config load and logged, instead of crashing every sign parse. (#139)
  • /bluemap reload now removes markers for signs whose prefix no longer matches any configured marker group, instead of leaving them behind. (#121)
  • Fixed a rare race condition on server startup that could affect sign loading. (#167)
  • Fixed a bug where reloading BlueMap's config (/bluemap reload) could leave a disabled connector still listening for events, risking duplicate or inconsistent marker updates. (#140)

Internal

  • Added broad unit test coverage across the sign-parsing, persistence, and config layers, and hardened several concurrency-sensitive paths for correctness.

What's Changed

Full Changelog: v26.2-0.16.0...v26.2-0.17.0