Cookies and statistics. We use Google Analytics to understand which pages are useful. Analytics cookies are set only with your consent. You can change your choice at any time at the bottom of the page. More about cookies
Ala Lab studio
Is your mod or plugin stuck on an old Minecraft version? We move it to a new game version or another loader and rewrite the code that no longer works there. Crashes and bugs get fixed along the way. We name the price and deadline once we’ve seen the code.
What we build
Your own mod, a mod from a modpack or a server plugin, as long as there is source code and the right to change it.
The mod runs on an old version, but players have already moved on.
Example order: port a Forge 1.20.1 mod to 1.21.1 to build a modpack on the new version.
The same mod, but for a different loader.
Example order: a Forge-only mod: make a Fabric version so it fits into a modpack with Sodium.
The plugin stopped starting after a server update.
Example order: a 1.16.5 plugin stopped working after the server was updated to 1.21.
The mod or plugin works, but with bugs.
Example order: the server crashes every few hours: find the cause in the logs and fix it.
What changes
Minecraft changes its code in almost every update: it renames classes, drops old ways of registering things and changes the data format. That’s why an old .jar won’t load on a new version and has to be rewritten. We release our own mod, Ala Industrial, for two game versions at once, so we know this from the inside.
The biggest kind of port: new data, registration and rendering. Often it’s almost a new mod on the old logic.
A different loader means different events and APIs. The mod’s logic stays, the wiring around it is rewritten.
Paper offers its own fast APIs, while Folia requires reworking the plugin for multithreading.
We need the source code and the right to change it: you are the author, the mod’s licence allows it, or the author has agreed. Without the source a port is usually impossible. We’ll tell you whether yours can be done once we’ve looked into it.
Porting
How hard a port is depends on where it’s moving from and to. Common cases are below; we’ll give an exact estimate once we’ve seen the code.
| Port | What changes | Difficulty |
|---|---|---|
| 1.20.1 → 1.21.x | What changesItem data components instead of NBT, new registries and recipe format | DifficultyMedium |
| 1.12.2 → 1.21.x | What changesAlmost everything: registration, rendering, data, networking. We keep the logic and rewrite the code | DifficultyHigh |
| 1.21.x → 26.x | What changesTargeted changes in the game code, rendering and input | DifficultyLow or medium |
| Forge → Fabric or NeoForge | What changesEvents, registration and loader setup. The mod’s logic stays | DifficultyMedium |
| Spigot → Paper | What changesOld code usually works; we switch to Paper’s fast APIs | DifficultyLow |
| Paper → Folia | What changesThe plugin is rewritten for region-based work across several threads | DifficultyHigh |
Example tasks
Typical orders, without client names. Messages like these are where a port starts.
Chat
How we work
At every step you know what is done and what comes next.
Path of a port
Send the mod or plugin, a link to the source and the version it should move to. We reply within 8 hours.
We look at the code and at what changed between versions. We fix the scope, price and deadline before starting.
We port it, fix the bugs we find and test it in game on the right version and loader.
The finished .jar, the updated source code and a list of changes. How the code is handed over is agreed before we start.
Price
Tick what needs to be done and watch the amount of work grow. We quote a price once we’ve seen the code and fix it before work starts.
Approximate scope
A small mod or plugin and the next version up.
A mod with blocks and mechanics, or a loader switch.
A big mod or a very old version.
This is a guide, not a price. We name the exact cost and deadline once the task is clear.
Discuss a portQuestions
No. Mods and plugins use the game’s internal code, and it changes in almost every version. An old .jar won’t load on a new version or will crash, so the code has to be rewritten.
Yes, if you have the source code and the right to port it: you are the author, the mod’s licence allows it, or the author has agreed. We check the licence before work starts.
It depends on the size of the mod, the gap between versions and the loader. We quote a price once we’ve seen the code and fix it, together with the deadline, before work starts.
We try to keep block and item names so old worlds still open. If the new version requires migrating data, we’ll warn you in advance and test on a copy of the world.
Yes. Our own mods ship for Fabric and NeoForge from one codebase, and we can set yours up the same way.
The finished .jar for the right version and loader, the updated source code and a list of changes. Rights and support after release are agreed before we start.
Your next project
Send a request and tell us what you want to see in the game. We reply within 8 hours and work through the task, even if so far it is one sentence.
