How to Fix an Ampz Server That Keeps Crashing

1. Server won't boot — check the Java version first

NeoForge on Minecraft 1.21.1 requires Java 21. If the server was spun up from an older template or an environment with a leftover Java 8 or Java 17 install still taking priority, the server process will fail to start cleanly, often with no obvious in-game symptom since the world never loads. This is one of the most common causes of an Ampz server that 'crashes' immediately on every boot attempt.

• Confirm the launch command is actually resolving to Java 21, not an older cached install
• Re-check this after any host-side Java update or pack migration

2. Detonations cause a short, sharp tick spike

Ampz's missile and explosion mechanics are a core part of its identity, carried over from Voltz. A large detonation generates a burst of block updates and entity ticks concentrated in a single moment, which is a different load profile than steady automation lag. On a server running close to its limits, that burst can push one tick past the watchdog timeout and trigger a crash rather than just a visible stutter.

If crashes cluster around specific build patterns — large stockpiles of explosives, chained detonations, or missile strikes on dense builds — this tick-spike pattern is the likely culprit rather than a general stability issue.

3. Power-plant automation adds sustained tick overhead

Separately from detonation spikes, Ampz's industrial power-plant automation adds its own steady tick cost as production chains scale up. This is the same category pattern seen on other automation-heavy tech packs: the server runs fine early on, then degrades as players build out larger plants, and what looks like a sudden crash is often the tail end of a slow TPS decline that finally hits a timeout.

4. Rule out corrupted config or a bad world chunk

If crashes aren't tied to a specific action (a detonation, scaling up a plant) but happen seemingly at random or always at the same location, check for a corrupted chunk or a config file that got partially written during a previous unclean shutdown. Restoring from a recent backup before the crashes started is a faster and safer first step than trying to hand-edit config files on a live world.

5. RAM under the pack's realistic floor

The real floor for Ampz (Voltz for 1.21) is 6 GB. Running below that doesn't usually produce a clean, instant crash — it shows up first as cascading lag and longer garbage-collection pauses as the pack's industrial and destruction mechanics compete for headroom, and only escalates into an actual crash once a tick finally blows past the server's timeout. If you're seeing gradual TPS decay before a crash rather than an immediate failure, under-provisioned RAM is worth checking before anything else on this list.