Docs / How Orca builds a mod

How Orca builds a mod

You describe the Minecraft content you want in plain English, and Orca builds the whole thing for you. Say "add a sapphire ore that drops gems and a sword that sets mobs on fire," and the AI writes the code, draws the block and item textures, generates any 3D models, compiles a real .jar, and hands you a finished file. You do not touch a line of Java or open a single config.

The part that makes the file actually work is the build loop. Orca does not just generate code and hope it runs. It boots a real test server, loads your mod, reads any error it hits, patches itself, and rebuilds until the jar compiles clean and the art pack is complete. The file you download has already been proven to load. For the wider walkthrough and a first prompt to try, see the hub and the how-to guide.

From a sentence to a file

The build runs as one loop. You start it with a sentence, and Orca carries the request all the way to a downloadable file.

  • Describe it in plain English, for example "a pickaxe that mines a 3x3 area" or "a friendly fox mob that follows you."
  • The AI writes the code for your loader and Minecraft version, then generates the block and item textures (PNG) and any custom 3D models.
  • It compiles the project into a real .jar (Fabric, Forge, or NeoForge), a plugin .jar (Paper, Spigot, Bukkit), a Bedrock add-on, or a packed .zip, depending on what you asked for.
  • It boots a real test server in the sandbox and load-tests the build to confirm Minecraft actually accepts it.
  • When the build passes, Orca signs the file and hands it to you. The desktop app refuses unsigned files, so a signed file is your proof it came from Orca clean.

The auto-fix loop

Code rarely compiles perfectly the first time, and Orca handles that without asking you. If the build fails, the AI reads the actual error, patches the code or the art pack, and rebuilds. It repeats this until the jar compiles and every texture and model the mod references is present.

You are not stuck watching a red error you cannot read. The loop runs until the build is green or the AI tells you plainly that something in the request cannot be done. Either way you get a clear result, not a broken half-mod.

Watch it work, then keep your project

You can follow the whole build as it happens, and everything you make is saved so you can come back and change it later.

  • A live creation view shows the steps as Orca writes code, generates art, compiles, and load-tests.
  • Every creation lands in a saved project workspace with an in-browser file and texture editor, so you can open the source files, repaint a texture, and rebuild.
  • Builds run in the background, so you can keep chatting or start another mod while the first one finishes.

Reuse work across projects

Once you have made something, you can pull it into a new build instead of describing it again. Tell Orca "add the enchantment from my other mod" or "reuse the fire sword I made last week," and it carries that piece into the current project. Your past creations become parts you can build with.

From the saved workspace you can keep editing your own creations freely, and you can pick a different loader or Minecraft version (1.21.4 down to 1.12.2, or type your own) when you want the same idea on another setup.

Ready to build?

Start free

Related