Choose by required features, not by popularity
Start with the experience your players need. A plugin-based Java server, a client-and-server modpack, and a Bedrock community solve different problems. Migrating after a world is active can require data conversion, plugin replacement, or a fresh world, so make the software decision before launch.
| Software | Platform | Main strength | Best fit |
|---|---|---|---|
| Vanilla | Official Java behavior | No Bukkit plugins; simple baseline | Small private worlds and compatibility testing |
| Paper | Java plugin server | Performance and administration controls; Bukkit/Spigot plugin ecosystem | Most small public or private Java communities |
| Purpur | Paper-derived Java server | Additional gameplay configuration | Owners who need Paper compatibility plus more behavior controls |
| Fabric | Lightweight mod loader | Modern mod ecosystem; exact client/server mod planning | Performance mods and curated modded experiences |
| Forge | Modding platform | Large modpack ecosystem and deep gameplay modifications | Established Forge packs and heavily modded servers |
| Nukkit | Bedrock protocol server implementation | Plugin-oriented Bedrock communities; behavior differs from official BDS | Bedrock communities that specifically need Nukkit plugins |
| Official Bedrock Dedicated Server | Official Bedrock server | Closest official Bedrock dedicated behavior | Bedrock worlds that do not require Nukkit plugins |
Decision questions
- Which edition do players own?
- Must players install files on their devices?
- Are required extensions plugins, mods, behavior packs, or Nukkit plugins?
- Does every required extension support the same game version?
- Can the server be backed up and restored before updates?
- Will the chosen software fit PortalMine’s currently supported server types?
Compatibility boundaries
Paper plugins do not become Fabric or Forge mods. Fabric and Forge mods are not automatically interchangeable. Nukkit plugins target Nukkit-compatible APIs, not Java Bukkit APIs. Protocol bridges can help some players connect across editions, but they do not make every gameplay mechanic, inventory format, or add-on compatible.
Migration checklist
- Export a complete backup and record the current software version.
- Test a copy, never the only production world.
- Inventory every plugin, mod, datapack, behavior pack, and custom configuration.
- Read conversion notes for player data, dimensions, inventories, and entities.
- Run a representative player test before announcing the migration.
Next guides
Plugin, mod, and add-on compatibility
Extension type is the strongest filter. A Bukkit-compatible plugin expects server software such as Paper or Purpur. A Fabric mod expects Fabric Loader and may need Fabric API. A Forge mod expects a compatible Forge build. A Nukkit plugin targets a Bedrock-protocol server implementation. Behavior packs and resource packs belong to a different Bedrock content pipeline. Similar names do not make these systems interchangeable.
World portability
World folders are not always safely portable across editions, implementations, and heavily modified environments. Even when terrain loads, player inventories, dimensions, entities, plugin databases, modded blocks, and custom metadata can differ. Test a copied world and keep the original untouched until every important feature has been verified.
Supportability checklist
- The project has current documentation and release notes.
- The required game version is supported.
- Every extension has a trusted download source.
- The startup method is understood and reproducible.
- A clean test server reaches a ready state.
- The world can be restored after a failed update.