Kilt: the bridge project that runs (Neo)Forge mods on Fabric

Forge mods are remapped from SRG into Intermediary

The pipeline is described directly in the project documentation. Kilt first remaps a Forge mod from the Forge SRG format into Fabric's Intermediary format, then applies its own fixers to make sure the result behaves correctly inside a Fabric environment. The fixers are Kilt code, maintained by hand, so every mod that passes through Kilt travels through a translation layer with a lot of edge cases in it. The repository layout reflects how the work is split. Top level directories include fml, forge, loader, compat, tweakers and workarounds, alongside the usual src, gradle and build-logic trees. Keeping tweakers and workarounds as separate directories points to a deliberate separation between general runtime adjustments and one-off shims for individual mods or API surfaces, and the src tree holds the mod itself.

The bundled Forge API still waits on mixin injects

The second half of the architecture is the API layer. Kilt recreates FML in a way that works with Fabric Loader, with changes of its own intended to improve on its performance, and it bridges Forge APIs with Fabric native APIs for compatibility. The whole Forge API is already bundled inside Kilt, but bundling is not the same as working. It depends on the patch reimplementations, called injects inside the codebase, being written first in mixin form. The API surface and the mixin patches are therefore two separate pieces of work, and the second one cannot be skipped. A Forge mod that touches an API area whose inject is not implemented yet has no clean failure path, which is the sort of thing that surfaces as a crash rather than an error message. The project credits the Fabricators of Create for Porting Lib and says that without it the effort would have been significantly harder, so part of the heavy lifting lives in an external dependency rather than inside this repository.

No install guide: the README sends you to Modrinth, CurseForge, or the Actions tab

There is no installation procedure in the README, and the project deliberately does not publish one as a conventional install flow. Instead it names the places the build lives. Kilt is published as Alpha on Modrinth and as Beta on CurseForge, both described as release builds and both framed as more stable than what comes out of continuous integration. Nightly builds are reachable from the GitHub Actions page, and a quick access download link is posted in the Discord channel #rules-and-info, which always carries the latest build. That is the whole distribution story: three channels, none of them carrying a documented configuration step. Anyone expecting a conventional loader install guide with a mod file path and a config directory will not find one here.

World breakage and crashes are the expected failure modes

The project documentation is unusually blunt about reliability. Kilt is described as currently highly unstable, and as something that may break worlds and may cause crashes, which is why the author classifies it as Alpha on one platform and Beta on the other rather than presenting it as finished. The reporting guidance follows from that. The instruction is to not report bugs to the mod developers unless they also occur on Forge, and to report them on the Kilt issue tracker instead, provided a similar issue does not already exist. That is a sensible triage policy for a compatibility bridge, because most failures belong to the translation layer rather than to the mod being ported. The practical reading is that Kilt should be tried on a copy of a world, with a backup, before anyone loads an existing save.

Patchwork stopped at 1.16, and Connector runs the other direction

Two comparisons appear in the project FAQ, and both draw a real line. Patchwork aimed at the same goal but has completely halted development, so it will not be updated to modern Minecraft versions past 1.16. The author goes further and states that Kilt has far surpassed Patchwork in development, while noting the two projects had shared different goals despite chasing the same outcome. Connector is the cleaner contrast of the two, because it inverts the direction entirely: Connector aims to have Fabric mods on Forge, while Kilt aims to have Forge mods on Fabric. The author's own framing is that running both together is reasonable. The practical difference between Kilt and Connector is therefore a one word answer to a support question, and the difference between Kilt and Patchwork is that one tracks current Minecraft versions and the other stopped.

Version coverage is a promise, not a schedule

Updates to newer Minecraft versions are described as planned, but the caveat attached to them is worth weighing. Kilt is called an incredibly large undertaking for only two people to work on. A NeoForge 1.21.1 build is stated to be in progress, and only after that does work move forward onto the latest version of Minecraft. Anything in between and earlier is going to be unsupported, with the note that someone else may take on that role instead. So the default branch name and the release tag numbers are the current coverage, and the gap between them is where mod authors will find no support. The release history is short and recent: v21.1.15 on 2026-10-06, v21.1.14 on 2026-09-30 and v21.1.13 on 2026-09-20, with the last push to the repository on 2026-10-20. The code is being worked on, and the support window is still narrow.

Editorial conclusion

Kilt suits a specific reader: someone already committed to Fabric Loader who needs one Forge or NeoForge mod that has no Fabric port, and who can work on a copy of the world rather than a production server. It is a poor fit for a server operator who needs uptime guarantees, for anyone unwilling to chase injector level failures, and for a modpack that has to survive an update cycle intact. Before committing, check three things: whether the specific mod you need is listed as working, whether the build you pull matches your Minecraft version, and whether you have a backup of the world. The last push was on 2026-10-20, so the code is moving, but the author states the project is an incredibly large undertaking carried by two people, and version coverage beyond the current one is not guaranteed.

Frequently asked questions

Official sources

1. KiltMC/Kilt on GitHub
2. License: LGPL-2.1
3. Project website
4. README
5. Releases