Concurent Chunk Management Engine - Forge

C2ME-Forge 0.2.0-forge.4 - build 2026-08-20

Compatibility
• Fixed a crash / mixin conflicts with Lithium forks that weren't recognised. The Lithium-family detection is now centralised and covers Canary, Radium (Reforged), Harium, Radon and Lithium - for BOTH the chunk-manager mixin and the NBT/Util allocation mixins. Previously Harium crashed on world load, and Radium slipped through the alloc gate (the "Method overwrite conflict for MixinNbtCompound / Skipping method" spam), which left C2ME's allocation mixin half-applied and could cause unrendered chunks. Note: two Lithium forks installed together (e.g. Canary + Harium) still conflict with each other - that is not a C2ME issue; use only one.
• Added a compatibility patch for The Lost Cities. Its deferred block placements no longer force-load chunks from the server tick under C2ME's async chunk system, fixing the "ServerHangWatchdog: a single server tick took 120 seconds" hang. No city blocks are lost - placements simply wait until their chunk is loaded.

Drop-in update - recommended for everyone on forge.3, especially with any Lithium fork (Canary / Radium / Harium / Radon) or The Lost Cities installed.