Modkit

One Gradle DSL for building multi-loader Minecraft mods from a single codebase.

You describe your mod once in a modkit { } block. Modkit wraps the build tools the ecosystem already relies on and drives them for whatever loader and Minecraft version you're targeting. That way you don't have to wire each tool up by hand, and differently for every loader.

Modkit is open-source! Check out the code.

Start here

• Introduction: what Modkit is, the mod-dev pain it removes, and how it stacks up against the alternatives.
• Getting started: a minimal single-loader mod, built end-to-end with Modkit.

Learn the model

• The Modkit model: the shared modkit { } model and how the active loader gets picked.
• The plugin suite: the modules, and the wrap-don't-reinvent thinking behind them.
• Multi-version builds: building one codebase against many Minecraft versions with Stonecutter.

Guides

• Mod metadata: generate manifests (e.g., fabric.mod.json) from the model.
• Mixins: register mixin configs and lint targets.
• Dependencies: mod(), jar-in-jar nest(), and mod repositories.
• Run configurations: unified client/server/data/gametest runs.
• Data generation: wire datagen across both loaders.
• Publishing: Modrinth, CurseForge, GitHub, Discord.
• Continuous integration: generate a version × loader CI matrix.
• Testing: pure-logic JUnit and NeoForge GameTest.
• Multi-version: set up a monorepo or single-mod version matrix.

Reference

• modkit { } (core) and the per-plugin reference: Loaders, Metadata, Mixins, Dependencies, Run, Datagen, Publish, CI, Testing, Multiversion, Scaffold.