Sulumin

Minecraft 26.3 with NeoForge built in, plus a converter that lets mods made for older versions run on it. Still in beta: many older mods do not run yet, and the numbers below show how far along it is.

Fuck AI. Sulumin is plain Java and a bit of Python. Nothing is sent to Claude or any other AI to make "mod slop" out of your work.
I'm poor... why would I pay Claude for that? This tool is free and unlimited, and runs on my server at home, which heats my apartment -_-

Conversion gaps

A gap is a piece of the game, a class, method or field, that mods made for the older version use and that the newer version no longer has. Sulumin counts them over its test set of mods, before converting and after.

A mod goes through every step from its own version up to 26.3: a mod made for 1.21.1 goes through all the steps from 1.21.1 to 26.3. The more steps a mod has to go through, the more likely it is not to work. BUT! A big mod may work after going through 9 steps, while a small mod may not work after one step. It depends on what the mod uses.

NeoForge stepGaps leftClosed by the converterLeft
26.2 to 26.3 1220 of 2202 55%
26.1 to 26.2 1175 of 2020 58%
1.21.11 to 26.1 1297 of 1908 68%
1.21.10 to 1.21.11 1110 of 1778 62%
1.21.8 to 1.21.10 1181 of 1508 78%
1.21.5 to 1.21.8 1043 of 1347 77%
1.21.4 to 1.21.5 958 of 1492 64%
1.21.3 to 1.21.4 711 of 858 83%
1.21.1 to 1.21.3 657 of 1725 38%
1.20.6 to 1.21.1 467 of 789 59%
1.20.4 to 1.20.6 488 of 1114 44%
1.20.2 to 1.20.4 212 of 355 60%

Measured on 16 November 2026, build 260b41c4e. Updated from my server.

A real modpack

Sulumin also starts a whole public modpack to see what really happens. Current pack: ChillCraft, for 26.2.

Server, server-side mods Starts, runs a world and stops cleanly. 1 error left.
Server, whole pack Does not start yet.
Client, whole pack Does not start yet.

Port your mod to 26.3

If you make a NeoForge mod for any version from 1.20.2 to 26.2, this tool will give you a version that runs on NeoForge 26.3, with or without Sulumin.

  1. Sign in with Modrinth (you only see projects where you can upload versions).
  2. Pick one of your mods.
  3. My server converts it. None of your mod's code runs during the conversion, and Sulumin doesn't care about your art, so don't worry: no copy :3
  4. Download the converted jar and its report. Both are deleted from my server after 24 hours, 'cause disk storage is really expensive in this economy.

Sign in with Modrinth

What the report looks like

A made-up mod, in the exact format the tool writes.

lanternlight 2.4.1 for NeoForge 26.2, converted for NeoForge 26.3.0.102

Result: converted, not boot-tested.

Changed in your code (5 places)
  LanternBlock.playerDestroy                  Level is now ServerLevel, Player is now ServerPlayer
                                              in Block.playerDestroy().
  LanternBlock (constructor)                  Only the access changed: now public (was protected);
                                              the bytecode calls are the same.
  LanternScreen.open                          Minecraft.screen is gone or changed in 26.3. Now uses
                                              Gui.screen().
  LanternScreen.close                         Minecraft.screen is gone or changed in 26.3. Now uses
                                              Gui.screen().
  RuinPlacement.start                         StructurePlacement.salt() is gone or changed in 26.3.
                                              Now uses Shims.salt(), from the bundled Sulumin library
                                              sulumin-compat-v26_1.

Also changed: 9 files of data, assets and metadata, listed in LICENSE-SULUMIN.txt.

Bundled Sulumin libraries (1)
  sulumin-compat-v26_1 0.1.0    MIT

To do in your source for 26.3
  Replace Level with ServerLevel, Player with ServerPlayer (in Block.playerDestroy()).
  Replace Minecraft.screen (gone or changed in 26.3); the port now uses Gui.screen().
  Replace StructurePlacement.salt() (gone or changed in 26.3); the port now uses Shims.salt().

Keep LICENSE-SULUMIN.txt with the jar, and the markers (the invisible annotation net.sulumin.Ported)
in its classes.
What it cannot port
  • Performance mods and engine fixes: they rewrite the parts of the game that changed the most.
  • Mods that only work because Sulumin changes the game itself.
  • Mods that need another mod that is not ported yet.

When that happens, you get the reason instead of a broken jar.

Licence

Your converted mod keeps your licence. The Sulumin code added to it is under the MIT licence, except a few libraries that come as separate jars inside yours, under the LGPL. They do not change your licence. I only ask one thing: keep the included licence file, which lists every change the tool made, and the markers it leaves on each class and method it changed. They are there so you, or anyone who picks the mod up later, can find their way around it.

Your converted mod does not start?

You can let me keep the converted jar to find out why. It will not be shared with anyone: I look at why it fails, fix the converter, then delete it. This page tells you when it is fixed and deleted. Then run your mod through the tool again, and it should work.

Why the code is not public

Not yet. I do not want to review pull requests full of vibe-coded changes tested against a single mod, and I do not want someone to take the project and run with it. The code will be published when it is ready.