Concurrent Chunk Management Engine - Forge

C2ME-Forge 0.2.0-forge.9.8 (Minecraft 1.20.1) - build 2026-10-02

On top of forge.9.7: the permanent server freeze with Dimensional Doors, two ways a chunk could lose its latest state when it unloads, terrain seams after rejoining a world, and Valkyrien Skies compatibility. No worldgen changes, existing worlds unaffected.

Fixed
• Permanent server freeze while Dimensional Doors builds pocket dimensions (SCE Protocol; the log said "re-entrant chunk load protection is active" and the server froze anyway). Dimensional Doors fills a new pocket chunk at the very end of the step that turns it into a finished chunk, after Forge has cleared the marker C2ME's protection relied on but before the chunk counts as finished; a mod asking for that chunk from there (MineColonies Compatibility does, on every block removal) waited forever. The protection now covers the whole step. Verified with a stand-in making the same request: froze before, starts normally now
• A chunk loaded again shortly after it unloaded could come back as its previous saved version or be generated from scratch: edits rolled back, Valkyrien Skies ship chunks came back empty. Loading did not wait for that chunk's background save, and C2ME's storage thread could answer a read that arrived right after a write with the older data. Both fixed. With saves delayed on purpose, 63 of 64 chunks lost an edit before; none do now, in four runs
• A chunk whose unload save had to be retried was never saved: the retry found it already marked as saved. It now stays marked until the retry has written it (63 of 64 chunks lost an edit before, none now). Both save problems are inherited from upstream C2ME
• Hard seams and ridges at the edge of the explored area after leaving and rejoining a singleplayer world (Tectonic + Lithostitched, forge.9.6). The optional fast chunk serializer saved chunks still being generated incorrectly, so they finished with different terrain than their neighbours. forge.9.6 and earlier used it whatever the setting said; default setups have been fixed since forge.9.7, and forge.9.8 turns the fast serializer off completely. With Tectonic + Lithostitched, compared with the same seed without C2ME: forge.9.6 was up to 36 blocks off around the first area, forge.9.8 matches. Terrain already saved with a seam stays as it is

Compatibility
• Valkyrien Skies: ships vanishing and the player freezing. Besides the reload fix above, C2ME's no-tick view distance kept chunks beyond the simulation distance loaded but not ready for ticking, and ship physics only uses ticking-ready chunks. With Valkyrien Skies installed the no-tick view distance now switches itself off (logged), and Valkyrien Skies' own save check runs before C2ME's

Configuration
• noTickViewDistance.enabled = false in c2me.toml now actually turns the no-tick view distance off; before, it had no effect on Forge
• ioSystem.gcFreeChunkSerializer is ignored (see the seam fix); one log line says so if it is set to true

Drop-in update - recommended for everyone on forge.9.x, and required if you use Dimensional Doors or Valkyrien Skies. No config changes needed.

--------------------------------------------------------------------------------

C2ME-Forge 0.2.0-forge.9.7 (Minecraft 1.20.1) - build 2026-09-26

On top of forge.9.6: chunk saving now does everything Forge's own save does, and the freeze protection works next to Canary. No worldgen changes, existing worlds unaffected, and chunks damaged by earlier versions are repaired when they load.

Fixed
• Mods' own per-chunk data was never saved. Forge's chunk save fires an event that mods use to store data in the chunk (Architectury passes it on to its mods; Mekanism, Immersive Engineering, Blood Magic and Project MMO use it directly). C2ME replaces both ways a chunk gets saved and fired that event in neither, so that data was gone after a restart or once the chunk unloaded. The event now fires at the same point as in Forge and what mods add is written into the chunk
• Console spam "ChunkSerializer: heights has to be of length 16". The optional fast chunk serializer is off by default and switches itself off with Architectury, but the setting never reached the part of C2ME that saves chunks, so it ran on every autosave and shutdown save anyway and wrote one piece of terrain-blending data in a form Minecraft rejects on every load. Blocks, items and block entities were never affected. Chunk saving now follows the setting, the serializer writes that data the way Minecraft does, and chunks already written the broken way are repaired as they load
• Permanent server freeze with Canary installed. Canary replaces the chunk request that the freeze protection from forge.9.4 hooks into, so the protection never ran ("re-entrant chunk load protection has NOT run" in the log). It now also hooks the method Canary and Radium add. With Radium, which guarded against this itself, the false alarm is gone

Drop-in update - recommended for everyone on forge.9.x, and required if you use Architectury-based mods, Canary, Mekanism, Immersive Engineering, Blood Magic or Project MMO. No config changes needed.
Support: https://discord.gg/s7BYs6Njj5