Minecraft Mod Maker AI: Build a Forge or Fabric Mod (2026)

A Minecraft mod maker turns your description into the source code of a Forge or Fabric mod, so you can add new items, blocks, or interface changes without writing the Java yourself. This guide explains what a mod is compared with a plugin, how to choose a loader and version, how to write a prompt, and how to test your mod in a development client before you share it.

Mods and plugins look similar on the surface, but they are different kinds of project. Making the right choice first saves time.

Mod or plugin: what is the difference

| | Plugin (Spigot, Paper) | Mod (Forge, Fabric) | | --- | --- | --- | | Where it runs | Server only | Client and server, both need it | | Where it goes | The plugins/ folder | The mods/ folder | | Built with | Bukkit, Spigot, or Paper API | Forge or Fabric API | | What players install | Nothing | The same mod and loader version | | Typical use | Commands, permissions, minigames, economy | New blocks, items, mobs, dimensions, interface changes |

A plugin runs on a server that accepts regular, vanilla clients. A mod changes the game itself, so every player must have it installed. Forge and Fabric are separate loaders, and a jar built for one does not load on the other.

Choose a plugin if you want gameplay logic on a Paper server that players join with the regular launcher. Choose a mod if you want new content and every player agrees to install it.

For plugins, see the Minecraft plugin generator. For mods, see the Minecraft mod maker.

Choose the loader and version first

Before you write a prompt, decide three things:

1. The loader. Pick Fabric or Forge and stay with it for the whole project.
2. The Minecraft version. A mod is built for one version. Write it into the prompt.
3. Dependencies. Most Fabric mods need Fabric API. Check the requirements before you start.

Write the prompt

A good mod prompt names the loader, the version, the mod id, and each feature in a sentence. Example:

Create a Fabric mod for Minecraft [your version] called "Starter Tools". Mod id: starter_tools. Add a copper pickaxe with 250 durability and the same mining speed as the iron pickaxe, plus a block called "Lantern Stone" that emits light level 10. Do not add networking or server-only code.

In your first version, keep one feature per prompt. Test it, then add the next feature. This makes errors much easier to trace.

What you get back

The project layout depends on the loader and version, but a Fabric project usually contains the build scripts, the Java source, and two metadata files:

starter-tools/
├── build.gradle
├── gradle.properties
├── settings.gradle
└── src/main/
    ├── java/...                   (your code)
    └── resources/
        ├── fabric.mod.json        (mod id, version, dependencies)
        └── assets/starter_tools/  (textures, models, language file)

A Forge project uses META-INF/mods.toml instead of fabric.mod.json, and its build uses ForgeGradle or ModDevGradle.

Mod id rules: use lowercase letters, numbers, and underscores. Keep it identical in the metadata file, the code, and the asset folder name. Mismatches are a common cause of missing textures.

Test in a development client

A development client runs Minecraft from your project, with your mod loaded, without installing it in your launcher. It is the fastest way to find problems.

1. Install the Java version your Minecraft version needs. Recent releases need Java 21.
2. Open the project in an IDE such as IntelliJ IDEA, or work from a terminal in the project folder.
3. Run ./gradlew runClient on macOS or Linux, or gradlew.bat runClient on Windows.
4. Wait for the first run. It downloads Minecraft, the mappings, and the loader, so it takes a while.
5. In the game, create a creative world and try every feature: the item, the block, the recipe, the texture.
6. Read run/logs/latest.log for errors and warnings that mention your mod id.
7. When everything works, run ./gradlew build. The distributable .jar is in build/libs/.

Before you share the mod, test it with a second client connected to a local server that runs the same loader and version.

Install on a server

A mod that adds content must be in the mods folder of the server and of every client. The server needs the same loader and Minecraft version. Install dependencies such as Fabric API on both sides. Start the server once and check the log for a line that lists your mod as loaded.

Common mistakes

• Mixing loaders: a Forge jar in a Fabric mods folder does not load.
• Using the wrong Minecraft version. Rebuild the mod for the version you run.
• A missing dependency, most often Fabric API.
• The wrong Java version, which breaks the build or the first launch.
• Uppercase letters or spaces in the mod id.
• Client-only code, such as rendering or screen classes, running on a dedicated server. This crashes the server at startup. Keep client-only code in client-only classes.
• Expecting a mod to work in the plugins folder. It belongs in mods.
• Sharing a jar with players before testing it in a development client.

When to hire a developer

Simple items, blocks, and recipes are a good fit for generation. A developer is worth the cost when the mod needs networking between client and server, custom data saved to a world, compatibility with other popular mods, or performance tuning for large servers. Review all generated code and test it on the target version before any public release.

The Starter plan is free: it gives 10 EC per day and 20 EC per month, and does not ask for a card. Hobby (50 EC for €5, one-time), Builder (250 EC for €20, one-time), Studio (800 EC for €50, one-time), and Pro (€18 per month, 300 EC per month, with the Fast and Ultra models) are on the pricing page. EC means EnderCredits.

Frequently asked questions

Do I need to know Java?

You do not need to write Java from scratch to get a working starting point. You still need to run the project, read error messages, and check what the code does. A few basics help a lot.

Can a Forge mod run on a Fabric server?

No. Forge and Fabric are different loaders with different APIs. Build a separate jar for each one you support.

Do players need the mod installed?

If the mod adds blocks, items, or client-side behavior, yes. Players need the same version and the same loader. A plugin does not require anything on the client.