Minecraft mod generator for Fabric and NeoForge

A plugin runs only on the server. Paper, Spigot and their forks load it, and players join with an unmodified Minecraft client. Plugins are the right tool for server rules, commands, economies and minigames, as long as everything can be done with the blocks and items the game already has.

A mod changes the game itself. It loads through a mod loader such as Fabric or NeoForge and can add new blocks, items, entities, screens, keybinds or rendering changes. When a mod adds content, the same .jar has to be installed on the server and on every player's client, otherwise they cannot connect.

Some mods only need one side. A minimap, a HUD overlay or a zoom key is client-only and works on any server. A server-only mod can change game logic while players keep their vanilla client, as long as it adds no new content.

Fabric is the default loader. It targets Minecraft 26.1.2, 26.2 and 26.3 and uses Mojang's own names for the game's classes, which is how the Fabric toolchain works on the 26.x line.

NeoForge is available on 26.3, 26.2, 26.1.2 and 1.21.1. NeoForge has only published beta builds for 26.3 so far, so that version is marked as beta in the generator. 1.21.1 remains useful for the many modpacks that settled on that release.

Pick the version your game or modpack really runs. The code, the libraries and the build are all tied to it: a mod compiled for 26.2 is meant for 26.2, not for the release before or after.

Once you submit your description, our AI writes the mod: the main class, the loader manifest, registrations, event listeners and any client code. The project is then built with Gradle, the build tool Fabric and NeoForge both rely on, against the Minecraft and loader versions you chose.

If the compiler rejects something, such as a wrong import or a method that does not exist in that version, the errors are sent back to the AI. It corrects the code and the build runs again, so what you download is a .jar that actually compiled.

After that, the mod opens in the online editor. You see its files and ask for changes in plain words, like “make the sword deal 2 more damage” or “add a crafting recipe for the ruby block”, and each change is rebuilt the same way.

The first time a mod is built for a given Minecraft and loader version, Gradle has to download and prepare that toolchain: the game, the loader and their libraries. This one-time step takes a few minutes.

The prepared toolchain is then reused, so later builds on the same version finish much faster. If your first mod on a version seems slow, it is this setup at work, not a problem with your code.

Content mods are the most common requests: a new material with its tools, a food item with effects, a weapon with a special ability. Quality-of-life mods fit just as well: a HUD that shows coordinates and the time of day, a key that toggles a display, a chat message on a specific event.

Keep each request focused. A mod that does one clear thing compiles cleanly and is easy to adjust. Grow it step by step in the editor rather than describing a full overhaul in a single prompt.

If all you need is commands or server rules, a plugin is simpler to deploy: see our Minecraft plugin generator.