How to Host an FTB Continuum Server

Start with at least 8 GB of dedicated RAM. That's the floor FTB Continuum itself recommends, and it's not padding — the GregTech New Horizons-inspired recipe overhaul leans on long ore-processing chains and multiblock machines that keep a lot of tile entities and recipe state loaded at once, even with a small group online.

Import the modpack directly from a CurseForge-aware installer instead of copying a client's mods folder onto a server. A hand-copied client export drags in client-only mods and skips server-side dependencies that Continuum's automation and logistics mods expect, and those gaps show up as missing-recipe or crash-on-join errors later.

Watch the console through the first boot instead of walking away. Forge has to resolve a large mod and recipe set before the world finishes generating — let it run until you see a clean 'Done' with no repeated class-loading errors or missing-dependency warnings, since Continuum's recipe overhaul is exactly the kind of thing that fails loudly if a mod didn't load right.

Only invite players in after that first startup has finished clean. Joining mid-load on a modpack this dependency-heavy is how players end up with broken block textures, missing recipes, or a crash the moment they open a multiblock controller.

Take a backup before importing a new world, updating Forge or any mod, or touching configs. A GregTech-style processing line can represent hours of planned automation and logistics — losing that to a bad update is a much bigger setback here than in a lighter pack.