Lithium 0.26.1 for Minecraft 26.3 released on 16 September 2026, one day after Wilderness Bound, and the release notes say it fixes two critical issues. A critical fix twenty-four hours after a port is exactly what you expect and exactly why nobody should update a server on release day.
What “critical” means in an optimisation mod
Not a crash, usually. Critical here means the mod was producing behaviour that differs from vanilla – a farm rate that is wrong, an entity that does not path correctly, a container that merges stacks it should not.
Those are worse than crashes because they are silent and they are already saved. A crash loses you nothing; a subtly wrong world is a world you keep playing.
Why the first port always has bugs
Lithium works by replacing Minecraft’s implementations with faster ones that produce identical results. When Minecraft’s implementation changes, every replacement has to be re-verified against the new behaviour – and the only way to be certain is to run it.
A port is therefore a hypothesis. The first week after a Minecraft release is the test.
The rule this implies
- Single player, vanilla: update whenever you like.
- Single player, modded: wait for your mods, then wait a week more.
- Server: wait two weeks minimum, and test on a copy first.
- Server with technical builds: wait a month, then test the farms specifically.
That last one is not caution for its own sake. Technical builds depend on exact timings, and an optimisation mod’s first port is the most likely thing to change them.
Diagnosing before you blame the mod
If something behaves oddly after an update, the order is: disable the individual optimisation, then the mod, then look elsewhere. Lithium’s config exposes every optimisation separately precisely so that step one is possible.
That granularity is unusual and it is the main reason technical servers are willing to run it at all.
Where it belongs in a server setup
Alongside a networking mod, a chunk loading mod and a memory mod – four different bottlenecks, no overlap. Adding all four is normal; adding one and expecting a general improvement is the usual disappointment.
Before any of them, though, comes measurement. What to tune before you pay for more RAM puts the diagnosis first, because the most common server upgrade fixes the least common server problem.
Client side too
Lithium helps a client in exactly the same situations it helps a server: busy worlds, big farms, lots of entities. It does nothing for rendering, and the reason people conclude it “does nothing” is usually that rendering was their problem all along.
Matching the mod to the symptom is the whole skill here, and the shortlist and what each one fixes is organised around that rather than around which is fastest.
Release timeline for 26.3
- 15 September 2026 – Wilderness Bound releases.
- 16 September 2026 – Lithium 0.26.1, two critical fixes.
- Same week – the rest of the optimisation layer follows.
The 26.2 line remains at 0.25.3 from July, and the 26.1.2 line at 0.24.7. Three supported branches, which is the condition the whole ecosystem is in during a transition.
The backup warning, again
It appears in every Lithium release and it is more relevant on a day-old port than at any other time. Copy the world folder before the first launch. It takes thirty seconds and it is the difference between a bad week and an inconvenient afternoon.
What vanilla parity actually requires
Every optimisation in the mod has to produce bit-identical results to the code it replaces, in every case, including the ones nobody tests – a hopper with a comparator on it, a mob pathing around a fence gate, a farm that depends on an entity being pushed exactly one block per tick.
Technical Minecraft players build machines on those details. A change of one tick somewhere is the difference between a working farm and one that jams overnight.
How to test after updating
- Copy the world before doing anything.
- Run each automated farm for a full in-game day and compare output to what you expect.
- Check villager breeding and trading, which are the most timing-sensitive vanilla systems.
- Watch hopper chains, which are where most parity bugs show up first.
Twenty minutes of that catches almost everything, and it is far cheaper than discovering a problem a week later when the world has moved on.
Three branches at once
- 0.26.1 for 26.3.
- 0.25.3 for 26.2, from July.
- 0.24.7 for 26.1.2, from July.
Servers rarely run the newest, so the older branches are not legacy support – they are where most of the mod’s actual deployment is.
Images: Distant Horizons and Additional Structures project galleries on Modrinth.