Mods (Fabric & Forge)
Mods change Minecraft itself — new blocks, items, mobs, and mechanics. On Lanzinha you run them
on a Fabric or Forge world, attach them by uploading their .jar files, and Lanzinha
re-applies them every time a room boots.
- Why mods need a Fabric or Forge world, chosen at create time
- Why Fabric and Forge mods aren't interchangeable
- How to upload, replace, and remove a mod
- How modded data persists, and how this works with imported worlds
Mods need a Fabric or Forge world
Mods only run on a Fabric or Forge world. You pick the engine when you create the world, next to the version, and it can't be changed afterward — to switch engines, create a new world. The engine selector only appears for versions that ship with Fabric/Forge baked in; older versions are Paper-only.
A Paper world runs plugins, not mods, and you can't mix plugins and mods on one world.
Fabric and Forge are different ecosystems
Fabric and Forge are separate ecosystems. A Fabric mod won't run on a Forge server, and a Forge mod won't run on a Fabric server — so download the build that matches your world's engine.
Fabric also needs the Fabric API mod for most mods to work. Fabric API is a normal mod:
you upload its .jar to the world alongside your other mods. Forge mods need a Forge world on a
matching version.
| Engine | Runs | Also needs |
|---|---|---|
| Fabric | Fabric mods | The Fabric API mod (uploaded like any other mod) |
| Forge | Forge mods | A matching-version Forge world |
| Paper | Plugins, not mods | — |
Upload a mod
From the world's page in Worlds, upload each mod:
| Detail | Value |
|---|---|
| File type | .jar |
| Per-file limit | 512 MiB |
| Storage | Counts against your account storage quota |
| Where it goes | The server's mods/ folder |
- Replace a mod by re-uploading a file with the same name — that's how you update it.
- Remove a mod anytime, as long as no room is running on the world. Uploads are rejected if they would push you over your storage quota.
Persistence
- Generated data persists. Modded chunks, machines, inventories, and per-mod config you changed in-game are backed up with the world and carry over between sessions.
- The jars are re-applied from your uploads each time the room boots. They're immutable from your upload, so to update a mod you re-upload the new jar — the world keeps its data.
How mods are run
Mods run real code on the server, so Lanzinha runs them in a hardened sandbox.
Because mods run server-side code, the feature is advanced and may be gated or limited while it rolls out. It may not be enabled on your account yet — if you don't see it, reach out to support.
Importing a modded world
When you bring your own world, Lanzinha imports the terrain and player data — but it does not pull mods out of the archive. A heavily-modded imported world still needs you to attach the matching mods (on a Fabric or Forge world) for the mod-added blocks and items to work.
Import the world for its terrain, then upload the same mods it used — matched to the same engine and version — to reproduce a modded server you ran elsewhere.
Lanzinha is an independent host and is not affiliated with Mojang/Microsoft, FabricMC, or Forge.
→ Related: Minecraft servers · Bring your own world · Plugins (Paper)