How to Fix a Dragoncraft Server That Keeps Crashing
Dragoncraft is a dragon-focused adventure pack on NeoForge 1.21.1, built around Ice and Fire-style dragon mods where players find, tame, and train dragons through a world of dragon lairs and challenges. That combination — a newer NeoForge/Java 21 stack plus mods that add large, AI-heavy entities and persistent per-player progress data — creates a specific set of crash patterns that are worth ruling out in order before you assume the pack itself is broken.
See the Dragoncraft pack page for the full RAM and setup breakdown before you chase anything else.
1. Wrong Java version from a previous pack
NeoForge on Minecraft 1.21.x requires Java 21. If this server (or this host slot) was previously running an older modpack on Java 17 or Java 8, and the switch to Dragoncraft didn't fully update the runtime the server launches with, you'll see an immediate boot failure rather than a mid-game crash. This is a common cause specifically because it's easy to miss — the server files look fine, but the JVM underneath is wrong.
- Check the very first lines of the startup log for a Java version or 'UnsupportedClassVersionError' message
- Confirm the server is actually launching under Java 21, not an older install left on the host
2. Dragon AI load causing tick timeouts
Dragon entities are not vanilla-weight mobs. Ice and Fire-style dragon mods run heavier AI, flight pathing, and territory/combat logic per dragon per tick — a well-documented pattern across any pack built around this mod family. If several dragons (tamed or wild) are loaded in the same area at once, especially during combat or breeding, tick time can spike well past normal and trigger a watchdog timeout, which looks like a sudden 'crash' even though the real cause is sustained lag.
3. Companion bond and growth data corruption
Dragon-companion bond and growth tracking is persistent per-player data that gets written to disk as players interact with their dragons. An unclean shutdown — a host crash, a forced kill, a power event — while that data is mid-write is a plausible source of save corruption. Corrupted companion data doesn't always crash the server instantly; it can surface later as a delayed crash the next time that player's dragon data is loaded.
- Always use a clean Stop rather than killing the process when a dragon-heavy session has been active
- Keep a recent backup before any manual edit to player or dragon data files
4. Conflicts introduced by third-party dragon or companion add-ons
If you've added extra mods on top of the base Dragoncraft list — particularly anything else touching entity AI, pathfinding, or tameable-mob frameworks — overlapping logic between two dragon-related mods is a common source of instability in packs built around a single large creature mod. If you've ruled out the Java version and the load-related causes above, this is the next place to check: try removing any added mods one at a time to isolate the conflict before assuming the base pack is at fault.
5. RAM under the pack's realistic floor
The real floor for Dragoncraft is 6 GB. Under-provisioning below that doesn't usually produce a clean, instant crash — it shows up first as cascading lag and longer garbage-collection pauses as the heap fills, which then escalates into a tick timeout once dragon AI load or several players push the server past what the heap can sustain. If your server is behaving fine at low population but destabilizes as more players and dragons load in, check RAM allocation before anything else on this list.
FAQ
Why does my Dragoncraft server fail to boot right after I migrated or reinstalled it?+
NeoForge on Minecraft 1.21.1 requires Java 21. If the server was previously running an older pack (1.20.1 or earlier) on Java 17 or 8, and the launcher didn't fully switch runtimes, the server process will fail at boot. Check the startup log for a Java version error before looking anywhere else — it's one of the most-reported causes of a Dragoncraft pack refusing to start at all.
Why does the server lag hard or time out when a lot of dragons are nearby?+
Dragon entities from Ice and Fire-style mods carry significantly heavier AI and pathfinding logic than vanilla mobs — flight pathing, territory checks, and combat behavior all run more calculation per tick. On a crowded server with several tamed or wild dragons loaded at once, this is a well-documented pattern for tick time spikes and eventual watchdog timeouts, not a one-off bug.
How much RAM does Dragoncraft actually need?+
The verified real-world floor for Dragoncraft is 6 GB. Running below that doesn't usually produce a clean crash — it shows up first as rising GC pause times and slow tick rate, which then escalates into a watchdog tick timeout under load (for example, when several dragons and their AI are active at once).
Host Dragoncraft on hardware sized for its real floor
Dragoncraft needs a real 6 GB RAM floor to handle dragon AI load without tipping into tick timeouts, and taking a backup before any risky change keeps a bad companion-data write from turning into a lost save.
View Minecraft Hosting →