How to Fix a Scales and Skies Server That Keeps Crashing

1. Server fails to boot, or crashes immediately on startup

Forge 1.18.2 requires Java 17 — this is the first thing to check on any boot failure, and it's an easy one to miss if you're reusing a host or launch profile from an older pack. Running the server jar on Java 8 or 11 typically fails fast, before the world even loads, often with an unhelpful early-exit rather than a clear 'wrong Java version' message.

• Confirm the server is launching with Java 17, not an older runtime carried over from another pack
• Check the very first lines of the crash log, not the bottom — version-mismatch failures usually show up near the top

2. Server lags badly or crashes once dragons are actively being tamed and flown

A clean boot that later lags or crashes once players are active is a different problem than a boot failure, and with this pack it's usually tied to dragon activity specifically. Dragon entities with flight physics and bonding AI carry notably heavier per-tick cost than vanilla mobs — a well-documented pattern on any pack built around large, complex companion creatures.

If TPS holds fine with no dragons tamed and starts dropping as more get tamed, ridden, or set to follow players around, that's the entity load, not a memory leak or a corrupted mod. Watch tick time specifically during active flight and taming sessions to confirm.

3. Crash only happens after several hours, not right away

Delayed crashes — ones that show up well into a session rather than at boot — point away from a config or version problem and toward something accumulating over time. On a pack with persistent per-player bonding data, that's often either memory pressure building up as more dragon entities and their saved state pile up, or a save file slowly growing corrupted from repeated unclean shutdowns.

4. Dragon bonding data looks corrupted or a player's progress resets

Dragon bonding and trust-progression state is persistent per-player data, so an unclean shutdown mid-write is a plausible source of save corruption that surfaces as a delayed crash or as a player simply losing their bond progress on next login. If this happens right after a hard stop, forced restart, or host-side kill rather than a normal in-game stop, that's the likely cause — the fix going forward is always stopping the server cleanly and keeping regular backups, since bonding data generally can't be reconstructed after the fact.

5. RAM under the pack's realistic floor

The real floor for Isle of Berk (Scales and Skies) is 6 GB — not a generic 4 GB guess for a mid-sized Forge pack, because the dragon entity AI and flight pathing push memory and tick cost meaningfully higher than a plain survival modpack of similar mod count. Under-provisioning rarely shows up as an instant, clean crash; it usually looks like cascading lag and longer GC pauses as more dragons get tamed and loaded, tick times creeping up over a session, and then eventually a tick timeout or watchdog crash once the heap is squeezed too hard to recover.