Lithium 0.25.3 for Minecraft 26.2 released on 29 July 2026, alongside 0.24.7 for 26.1.2 – two branches, same day. The release notes are short and carry a warning that is worth taking seriously: back up your world before using the mod.
Why an optimisation mod warns about backups
Because Lithium does not add anything. It rewrites how the game does things it already does – mob AI, block ticking, collision, hopper logic – and gets its speed by finding a faster path to the same result.
When one of those rewrites is subtly wrong, the result is not a crash. It is a world where something behaves differently to vanilla, and that difference is already saved.
What it actually optimises
- Entity AI and pathfinding, which is most of the tick time in a populated world.
- Block tick scheduling.
- Collision resolution.
- Hopper and container logic, which matters enormously on technical servers.
Every one of those is configurable and can be disabled individually, which is unusual and is exactly what you want from a mod that touches game logic.
Where the gain shows up
On the server side, as tick time. Lithium is one of the few mods that helps a dedicated server more than a client, and the improvement is largest in worlds with a lot going on – farms, villagers, mob-heavy areas.
If your server is struggling, this belongs in the diagnosis before any hardware decision. What to tune before paying for more RAM puts it in order with the other options.
Client-side too
Yes, and it stacks with the rendering mods rather than competing with them – different bottleneck, different fix. The reason people run four performance mods is that each one addresses a distinct problem, and the shortlist is built around that separation rather than around which is fastest.
Two branches, one day
Shipping 0.25.3 for 26.2 and 0.24.7 for 26.1.2 together is deliberate maintenance of an older line for players who have not moved. Modpacks lag Minecraft by months, and a mod that abandons the previous version strands them.
Not every project does this. The ones that do are the ones modpack authors build on.
Follow-up
Lithium 0.26.1 for 26.3 arrived on 16 September 2026, the day after Wilderness Bound, fixing two critical issues found immediately on release. The backup warning applies there more than anywhere.
Practical advice
If something behaves oddly with Lithium installed, disable the individual optimisation rather than the mod. The config file lists every one of them with a description, which turns “the mod broke my farm” into a ten-minute bisect instead of an uninstall.
How Lithium differs from a rendering mod
Rendering mods change what you see and cannot affect the world. Lithium changes how the world is computed, which means a bug in it is a bug in your save.
That is the entire reason for the backup warning, and it is why the mod ships with every optimisation individually toggleable – so a suspected problem can be isolated rather than guessed at.
The optimisations that matter most
- Entity AI – pathfinding is the single largest tick cost in most worlds.
- Hopper logic – on technical servers, hoppers are the tick budget.
- Block ticking – matters in farms and in large redstone.
- Collision – matters where many entities occupy a small space.
Every one of those is invisible in an empty world and decisive in a busy one, which is why benchmark numbers for this mod vary so wildly between testers.
Vanilla parity as a design rule
Lithium’s stated goal is to change nothing observable. An optimisation that alters farm rates, mob behaviour or redstone timing is a bug by the project’s own definition, even if it is faster.
That rule is why technical players will run it. A performance mod that changes behaviour is unusable on a server where people build machines that depend on exact timings.
Where the mod does not help
- Low frame rate in an empty world – that is rendering.
- Stutter while flying – that is chunk loading.
- Memory exhaustion – different mod, different problem.
Installing Lithium for a rendering complaint is one of the most common mismatches in modded Minecraft, and it produces the conclusion that the mod does nothing.
Configuration file
The mixin config lists every optimisation with a short description of what it does. It is one of the few config files in Minecraft worth reading end to end, and it doubles as an education in where the game spends its time.
A last word on the backup warning. It is not boilerplate and it is not fear – it is the honest consequence of a mod that changes how a world is computed rather than how it is drawn. The project has an excellent record, and the correct response is still to copy the save folder before the first launch on a new version. That habit costs thirty seconds and has saved more worlds than any single mod has improved.
Images: C2ME and MoreCulling project galleries on Modrinth.