How to Fix a Project Architect 2 Server That Keeps Crashing
Project Architect 2 is a creative building and architecture pack on Forge 1.20.1 — hundreds of building-focused mods like Macaw's series, Supplementaries, and Chipped give builders a huge decor palette, with no tech or magic progression layer behind it. That design actually works in your favor when something crashes: with no automation systems generating tick load, most crashes on this pack come down to environment issues (Java version, RAM) or the sheer size of player-built structures, rather than mod-on-mod conflicts.
See the Project Architect 2 pack page for the full RAM and setup breakdown before you chase anything else.
1. Confirm you're running Java 17
Forge on Minecraft 1.20.1 requires Java 17 — this is a hard requirement of Forge at that version, not a pack-specific quirk. If the server was set up on an older runtime, or a panel/host defaulted to a legacy Java version, you'll typically see the server fail very early, often before the world finishes loading. This is the fastest check to rule out and should be the first thing you look at before touching RAM or mod configs.
- Check the Java version your server process is actually launching with, not just what's installed on the box
- An early, pre-world-load crash points here before anywhere else
2. Rule out RAM before assuming a mod is at fault
Project Architect 2 loads hundreds of building-focused mods, and even without automation systems, that mod count alone adds up in base memory overhead. If the server runs fine for a while and then crashes or hangs under load — especially as players explore more of the built world — insufficient RAM is a more likely explanation than a specific mod conflict, given how few interaction-heavy systems this pack actually has.
3. Autosave pressure from large hand-built structures
This pack is built for large-scale creative construction, and very large hand-built structures can meaningfully increase world-save time and memory pressure during autosave. If crashes or freezes consistently happen around the same interval rather than at random, check whether that interval lines up with autosave — it's worth knowing this is a save-size effect before assuming it's a bug in a specific mod.
4. Decor/block mod overlap, not automation conflicts
With dozens of decor and building mods like Macaw's series, Supplementaries, and Chipped all adding blocks, there's a wider-than-usual surface for texture or block-registration overlap between mods in this category, compared to the mod-interaction crashes you'd see in a tech or magic pack. If a crash log points at a specific decor mod rather than a core game system, that's consistent with this category of issue rather than something exotic.
5. RAM under the pack's realistic floor
The real floor for Project Architect 2 is 5 GB — treat that as the minimum, not a target. Running under that floor rarely produces a single clean crash message; instead you'll typically see cascading lag and garbage-collection pauses that get worse over a play session, eventually ending in a tick timeout or watchdog crash rather than an instant, obvious failure. If your server has been drifting slower over hours before it finally drops, check RAM against the 5 GB floor before anything else.
FAQ
Project Architect 2 has no tech or magic mods — why is my server still crashing?+
That's actually useful information. Packs built around automation, tech progression, or magic systems (Create, Applied Energistics, Mekanism, Botania, etc.) tend to crash from mod interactions and chunk-loading tick load. Project Architect 2 is a pure building pack — Macaw's series, Supplementaries, Chipped — with no automation layer, so it has far fewer of those interaction-driven crash sources. In practice that means most crashes trace back to the environment: wrong Java version, insufficient RAM, or disk/world-save pressure, rather than two mods fighting over the same event.
Does the pack really need Java 17?+
Yes. Project Architect 2 runs on Forge for Minecraft 1.20.1, and Forge on 1.20.1 requires Java 17 — this isn't pack-specific, it's a hard requirement of Forge itself at that Minecraft version. Running it on Java 8 or Java 11 (leftover from an older install, or a panel that defaulted to the wrong runtime) is one of the first things to rule out before looking anywhere else, especially if the server fails before the world even loads.
Why does my server lag or crash specifically during a save, not during normal play?+
Project Architect 2 is designed for large hand-built structures, and very large builds increase world-save time and memory pressure during autosave. If a crash consistently lines up with an autosave tick rather than with players moving around or opening menus, that's a sign the save itself — not a mod conflict — is the bottleneck. Spacing out autosave intervals and making sure the server has enough RAM headroom above the pack's floor both help here.
Host Project Architect 2 on hardware sized for its real floor
Project Architect 2 needs at least 5 GB of RAM to run reliably, and taking a backup before any config change or Java upgrade means a bad experiment never costs you the world.
View Minecraft Hosting →