How to Host a Conquest of Dragons Server (2026 Setup Guide)

Start the server with at least 6 GB of RAM allocated. That's the recommended floor for Conquest of Dragons on Forge 1.20.1 — the pack layers a structured quest book, boss-tier dragon AI, and per-territory progression tracking on top of standard world simulation, and under-provisioning shows up as slow quest book loading and dragon fights that stutter right when the hits start landing.

Import the modpack directly from its official release instead of rebuilding it from a client export. A clean import guarantees the quest book, territory unlock logic, and dragon boss configs match what players see client-side — mismatched versions are the single most common cause of quests that silently refuse to complete.

Watch the console through the full first boot. Let the quest book data, territory definitions, and dragon spawn tables finish initializing before you consider the server ready — Conquest of Dragons front-loads a lot of registry work for its progression system, and a server that looks 'done' ten seconds early can still be missing boss configs.

Only invite players once that first boot has completed cleanly with no mod errors in the log. Joining mid-initialization is how players end up with quest book entries that never populate or territories that show as unlocked when they aren't.

Take a backup before importing a new world, updating Forge or any mod, or editing a territory/boss config. Conquest of Dragons ties a player's progress to which dragons they've already defeated and which territories that unlocked — losing that state means replaying boss fights your group already won.