Metalith

What is new

Servers keep their terrain when the mod set changes. Adding or removing a mod or data pack changes the block and biome ids. 0.1.1 dropped the whole server-side LOD cache when that happened; 0.2.0 renumbers the server's colour table by name instead, in about a quarter of a second for 100,000 entries, and the cached tiles stay. Caches written by 0.1.1 get the name index at their next open, so the change after that is survivable too.

Less memory on big worlds. The snapshots the client keeps of saved chunks are now held under a budget (an eighth of the Java heap, at least 64 MB) and read again from the world files only when a distant tile has to be rebuilt. A 200,000-chunk import that used to hold 2 GB now peaks under 100 MB. What you see and how fast it appears does not change.

Harder to break.

• A server refuses tile requests outside the world, caps each player's answer queue, keeps its request quota across reconnects, reloads its config without losing running values on a typo, really closes idle dimensions, and never drops its cache on a passing disk error.
• On the client, a worker thread that hits an out-of-memory error fails one tile and carries on instead of dying; a Metal renderer that fails closes the LOD session cleanly and hands the world to your shader pack if one loads later; one tile the GPU refuses is skipped and asked for again, never a permanent hole.
• With a shader pack, every hook into Vitrail and Sodium is checked with its exact signature before a feature turns on, so a mismatched version turns the feature off instead of drawing wrong pixels; a failing water pass no longer makes the terrain flicker; a GPU device loss is handled instead of disabling the far terrain for the session.
• A client at the very edge of the world with the maximum LOD radius could lose its server session (a real bug found by review): fixed.

Smaller jar. Development probes and harnesses (about 3,700 lines) no longer ship; the 26.3 jar is 60 KB lighter.

Minecraft 26.2. The terrain sampler tolerates the density shapes of Tectonic and C2ME on both versions; the 26.2 build shares more code with 26.3 and no longer ships a Sodium mixin config for classes it does not have.