Docs / Editing and uploading mods

Editing and uploading mods

A finished mod is rarely the last word. Maybe the sword needs more damage, the new mob needs a different texture, or a config value is off. In Orca you do not open a code editor and hunt for the right line. You describe the change in plain English and the AI edits the code, regenerates any art that changed, and rebuilds the file. The same build loop that made the mod runs again: it compiles, boots a real test server to confirm the jar loads, fixes its own build errors, and hands you a new signed file when it passes.

There are three doors into editing. You can keep iterating on the creations you already made, you can edit a third-party mod or modpack when its license allows, and you can upload a file you made elsewhere and remix it. The walkthrough at edit a Minecraft mod with AI shows the flow end to end. This page covers all three doors and the one rule that ties them together: respect the license.

Edit your own creations

Everything you build with Orca lands in a saved project workspace, so it is always there to change. Tell Orca what you want different and it edits the code and rebuilds the file for you.

You can also open the in-browser file and texture editor to touch the project directly, and you can pull pieces across projects, like adding the enchantment from one mod into another.

  • Describe a change in chat and the AI patches the code, regenerates changed textures or models, and rebuilds.
  • Edit code, textures, and files by hand in the in-browser workspace editor.
  • Reuse work across projects, for example "add the enchantment from my other mod".
  • Builds run in the background, so you can keep chatting while a rebuild finishes.

Edit a third-party mod or modpack

Orca can also edit mods and modpacks that did not start in your workspace, as long as the license permits it. Pull something in from the 39,000+ mods, modpacks, and plugins on Modrinth and CurseForge, then ask for the change you want.

The change flow is the same as for your own work. You describe what should be different, the AI edits and rebuilds, and the load test confirms the new jar still boots. Where a license does not allow edits, Orca will not rebuild that file for you.

Upload your own file and remix it

Already have a file from another tool or an older project? Upload it and remix it in Orca. Supported formats and the size limit:

  • Mods and plugins as .jar, packs and server files as .zip, Bedrock add-ons as .mcaddon and .mcpack.
  • Up to 100 MB per upload.
  • Every upload is scanned before it reaches the AI, including checks for zip-bombs, path traversal, and malware.
  • Pick the loader and Minecraft version for the remix, anywhere from 1.21.4 down to 1.12.2, or type your own version.

How an edit is built

An edit runs through the same safety loop as a fresh build, so a changed file is held to the same bar as a new one.

The AI rewrites the code and regenerates any art that changed, compiles the jar, and boots a real test server in the sandbox to confirm it loads. If the build breaks, it reads the error, patches, and rebuilds until both the jar and the art pack are complete. The result is a finished, cryptographically signed file. The desktop app refuses unsigned files, so a signed build is your sign that the edit passed.

Respect the license

The line between editing your own work and editing someone else's is the license. Your own creations are yours to change freely. Third-party mods and modpacks can only be edited where the license allows it, and the same applies to anything you upload: only remix files you have the right to remix.

If a license blocks edits, Orca will not rebuild that file. Publishing has its own guardrails too, so check the acceptable use policy before you share a remix in the public gallery.

Ready to build?

Start free

Related