How to Host a Modded OneBlock Server (Forge 1.20.1 Guide)
Modded OneBlock takes the classic one-block-at-a-time format and rebuilds it on a custom datapack and world, with its own mod list layered on top on Forge 1.20.1. It's one of the most-downloaded OneBlock packs on all of CurseForge, which also means its custom progression data is easy to break if you host it carelessly. Here's how to set it up correctly from the first boot.
Start with at least 8 GB of RAM allocated to the server. That's the recommended floor for Modded OneBlock — the custom datapack driving block progression plus the mod loader on top of it needs more headroom than a plain OneBlock map, so don't try to squeeze it onto a smaller plan.
Import the modpack directly from its CurseForge project instead of zipping up a client install and uploading that. A clean import pulls the exact mod list, the custom datapack, and the custom world together, so the server starts with the same block progression the pack was built around rather than a mismatched or missing world.
Watch the console through first boot. Let Forge finish loading every mod and let the custom datapack register before anyone joins — on a OneBlock pack, a world that doesn't fully initialize the datapack can leave the starting island broken or the progression phases out of order.
Only invite players once that first boot completes cleanly with no mod errors in the log. OneBlock's whole loop depends on the island generating correctly from block one, so a shaky first start is worth fixing before it has players standing on it.
Take a backup before importing a new world, updating the mod loader, or changing configs. Because Modded OneBlock's progression is baked into its custom datapack and world save, a bad update or a wrong world swap can wipe out everyone's block-tier progress with no way to recover it.
Use a cleaner Modded OneBlock path
CoalHost is built around modpack hosting, which makes Modded OneBlock much less annoying to launch correctly.
Deploy Modded OneBlock now →