How to Fix an Another Quality Modpack 2 - AQM2 Server That Keeps Crashing
Another Quality Modpack 2 - AQM2 is a Fabric kitchen-sink for Minecraft 1.19.2 that leans on deliberate mod curation — Tech Reborn for tech, a magic and exploration layer, and optimization mods like Lithium, Sodium, and Starlight to keep it running smoothly. Because the mod list itself is curated for compatibility, most crash reports on this pack trace back to environment issues (wrong Java version, undersized RAM) rather than mod conflicts. This guide walks through the checks in the order that actually resolves most tickets.
See the Another Quality Modpack 2 - AQM2 pack page for the full RAM and setup breakdown before you chase anything else.
1. Confirm you're running Java 17
Fabric on Minecraft 1.19.2 requires Java 17 — this is the first thing to check on any boot failure or immediate crash on startup. A server JAR launched under an older Java runtime left over from a previous pack install, or a host that defaults to Java 8/11 for 'Minecraft servers' generically, will fail before the world even loads. Confirm the launch script or panel is explicitly pointed at a Java 17 (or newer, where supported) runtime.
- Check the java -version output used by the server's start command
- Check any java_version or runtime setting in your host panel matches 17, not 8 or 11
2. Watch for Tech Reborn tick overhead as bases scale up
Tech Reborn's multiblock machines and their processing chains add real tick overhead, and that overhead grows with how much a base has expanded — more machines, more connected chains, more items being processed per tick. This is the same general pattern seen across other multiblock-heavy tech mods: a server can run smoothly for weeks and then start showing lag spikes or tick timeouts once one or two players build out a large automated setup.
If crashes started coinciding with a specific base growing, that's a stronger signal than a random mod conflict — it points at tick load, not a broken mod.
3. Rule out environment before blaming mods
Because AQM2 is a deliberately curated pack, the mod list has already been checked for compatibility — which means the odds of a genuine mod-vs-mod conflict causing your crash are lower than on a loosely assembled kitchen-sink pack. Work through Java version and RAM first (sections 1 and 5), and only start suspecting an individual mod once both of those are confirmed correct and the crash still reproduces.
4. Check for corrupted config or world data after a bad shutdown
A hard crash, a host outage, or a forced kill of the server process mid-save can leave a config file or chunk data in a half-written state. On restart, this often shows up as a repeatable crash at a specific point (loading a dimension, loading a player's inventory) rather than a random one. If the crash is consistent and reproducible on every boot attempt, restoring from the most recent clean backup is usually faster than trying to hand-edit the affected file.
5. RAM under the pack's realistic floor
The real floor for AQM2 is 6 GB — note that this is the pack's own verified floor, not a generic guess, and it benefits from the pack's built-in optimization mods (Lithium, Sodium, Starlight) keeping baseline overhead lower than a typical 1.19.2 kitchen-sink pack of similar scope. Running under that floor rarely produces an instant, clean crash. What you'll see instead is cascading lag as garbage collection pauses get longer and more frequent under memory pressure, TPS dropping as the server struggles to keep up, and eventually a tick timeout that looks like a crash but is really the server giving up after falling too far behind. If you're seeing that pattern, check allocated RAM before anything else.
FAQ
My AQM2 server won't even boot — where do I start?+
Check the Java version first. AQM2 runs on Fabric for Minecraft 1.19.2, which requires Java 17 — if the server is still pointed at Java 8 or 11 from an older setup, it will fail to boot or crash almost immediately. This is the single most common cause of boot failures on this pack, so rule it out before looking at mods.
The server runs fine for a while then crashes once a base gets big — is that normal?+
It's a known pattern for tech packs like this one. Tech Reborn's multiblock machines (and processing chains built around them) add tick overhead that scales with how much a base has grown, so a server that was stable early on can start showing lag spikes or timeouts once players build out larger automated setups. It's the same category of issue seen with other multiblock-heavy tech mods, not unique to AQM2.
How much RAM does AQM2 actually need?+
The real floor for AQM2 is 6 GB. That's lower than what a generic kitchen-sink pack of this size might suggest, since AQM2 is deliberately curated with optimization mods (Lithium, Sodium, Starlight) that keep overhead down — but running below 6 GB will still produce the usual under-provisioning symptoms: rising GC pause times, cascading lag, and eventually a tick timeout rather than a clean crash.
Host Another Quality Modpack 2 - AQM2 on hardware sized for its real floor
AQM2 needs a real 6 GB RAM floor to stay stable as Tech Reborn bases scale up, so provision for that and take a backup before any risky change like a big mod or config update.
View Minecraft Hosting →