How to Host All The Mods 10 (ATM10) Server
Step-by-step guide to hosting an ATM10 server, NeoForge setup, Java 21, RAM sizing, world pre-generation, and fixing common ATM10 crashes.
What Is All The Mods 10?
All The Mods 10 (ATM10) is the latest entry in the long-running ATM series, and it is a kitchen-sink pack in every sense of the word. With over 400 mods spanning tech, magic, exploration, and quality-of-life, ATM10 aims to include everything worth playing in modern Minecraft. The pack runs on Minecraft 1.21+ and uses NeoForge as its mod loader, not the original Forge. This distinction matters for server setup.
Key mods in the pack include Mekanism (for industrial processing chains), Ars Nouveau (magic automation), Applied Energistics 2 (digital storage), Create (mechanical engineering), and dozens of worldgen mods that reshape how terrain generates. The sheer breadth of content means players will be doing wildly different things on your server at the same time, which creates unique performance challenges.
ATM10 is not a lightweight pack. It was designed for players who want the full modded experience and are willing to throw hardware at it. As a server admin, your job is to make sure that hardware is configured correctly.
Server Requirements
NeoForge
ATM10 requires NeoForge, not the legacy MinecraftForge. NeoForge is a fork that became the primary mod loader for Minecraft 1.20.2+ on the Forge side. The ATM10 server pack specifies which NeoForge version to use, always match it exactly. Running a newer NeoForge build than what the pack was tested against is a common source of crashes.
Download NeoForge from neoforged.net and install the server version. However, if you download the ATM10 server pack from CurseForge, it typically includes an installer script that handles the NeoForge installation for you.
Java 21
Minecraft 1.21+ and NeoForge require Java 21. Java 17 will not work, NeoForge uses Java 21 language features and will refuse to start on older runtimes. On a managed hosting panel, select Java 21 from the version dropdown. On a VPS, install openjdk-21-jre-headless.
Java 21 brings significant garbage collection improvements. The G1 collector is more mature, and you can also experiment with ZGC (Zero-pause Garbage Collector) for large heap sizes. More on that in the performance section.
RAM Allocation
| Player Count | Minimum RAM | Recommended RAM |
|---|---|---|
| 1–5 players | 8 GB | 10 GB |
| 6–10 players | 10 GB | 12 GB |
| 10–20 players | 12 GB | 16 GB |
ATM10 loads over 400 mods into memory, each with their own registries, block entities, and item definitions. The base memory footprint before any player even joins is around 4–5 GB. With players actively exploring and building, 8 GB is the absolute floor. Use our RAM calculator to estimate your needs based on player count and installed mods.
Storage: NVMe Matters
ATM10 has some of the heaviest chunk I/O of any modpack. The custom worldgen mods (Terralith, YUNG's structures, and others) write significantly larger chunk data than vanilla. When players explore new terrain, the server writes thousands of chunks to disk simultaneously. On a spinning HDD or even a slow SATA SSD, this creates I/O bottlenecks that manifest as lag spikes during exploration.
NVMe SSDs handle this workload without breaking a sweat. If your host offers both SSD and NVMe options, spend the extra for NVMe, you will feel the difference during world generation and chunk loading.
Downloading and Installing the Server Pack
Go to the ATM10 CurseForge page and download the server pack. Extract it into your server directory. The pack includes a startup script, on Linux, it is typically called startserver.sh.
Before running it, make it executable:
chmod +x startserver.sh
./startserver.sh
The script usually handles NeoForge installation automatically on first run. It will download the correct NeoForge version, install libraries, and set up the server. You will need to accept the EULA by editing eula.txt after the first attempt.
First Boot
The first boot of ATM10 is slow. Expect 3–8 minutes depending on your hardware. NeoForge needs to load 400+ mods, register tens of thousands of blocks and items, and prepare the world. Initial world generation is especially slow because every custom worldgen mod runs its terrain pipeline for the spawn chunks.
Do not kill the process because it looks stuck. Watch the console, as long as log lines are still appearing, it is working. The server will print "Done" with a time in seconds when it is ready for connections.
Common Issues and Fixes
NeoForge Version Mismatches
The single most common crash on ATM10 is using the wrong NeoForge version. The pack pins a specific NeoForge build. If your host auto-updates NeoForge or if you manually install a different version, mods will fail to load. The crash log will typically contain lines like Missing or unsupported mandatory dependencies or Mod X requires neoforge >= Y. Always use the exact NeoForge version specified in the server pack.
Mod Incompatibilities After Updates
ATM10 updates frequently. When you update the pack, some mods may conflict with each other temporarily. If the pack update notes mention removing a specific mod, make sure it is gone from both your mods/ folder and any cached data. Leftover mod data in the world save can cause chunk corruption.
World Generation Lag
When players explore aggressively, generating new chunks puts enormous strain on the server. Multiple custom worldgen mods stack their processing, Terralith reshapes terrain, YUNG's mods insert complex structures, and biome mods alter vegetation. The result is that chunk generation takes 5–10x longer than vanilla.
Performance Tuning
Pre-Generate Your World
The single best thing you can do for ATM10 performance is pre-generate the world before players join. Use a mod like Chunky (if included in the pack or added separately) to generate a radius of 3,000–5,000 blocks around spawn. This front-loads all that expensive terrain generation so players explore already-generated chunks.
/chunky radius 3000
/chunky start
Let it run overnight. On a good NVMe drive, pre-generating a 3,000-block radius takes 2–4 hours. The resulting world folder will be large (5–15 GB depending on worldgen complexity), but the gameplay experience is dramatically smoother.
Disable Unnecessary Mods
ATM10 includes everything, but not every server community uses everything. If your players are focused on tech mods and nobody touches magic, you can remove some magic mods to reduce memory and tick overhead. Be careful with dependencies though, use the mod list on CurseForge to check what depends on what before removing anything.
Optimize Chunk Loading
Set view-distance=8 and simulation-distance=6 in server.properties. ATM10 adds so many block entities per chunk (machines, pipes, cables, conduits) that each loaded chunk costs more tick time than vanilla. Reducing simulation distance means machines in distant chunks pause when no player is nearby, saving significant TPS.
JVM Flags for Java 21
Java 21 supports modern GC options. For ATM10, a solid starting configuration:
java -Xms10G -Xmx12G -XX:+UseG1GC -XX:MaxGCPauseMillis=130
-XX:+UnlockExperimentalVMOptions -XX:+UnlockDiagnosticVMOptions
-XX:G1NewSizePercent=40 -XX:G1MaxNewSizePercent=50
-XX:G1HeapRegionSize=16M -XX:G1ReservePercent=15
-XX:InitiatingHeapOccupancyPercent=20
-XX:SurvivorRatio=32 -XX:+AlwaysPreTouch
-jar neoforge-server.jar nogui
If you have 16+ GB allocated, consider trying ZGC instead of G1 for potentially lower pause times: -XX:+UseZGC -XX:+ZGenerational. ZGC is designed for large heaps and keeps pause times under a few milliseconds regardless of heap size. Read more in our JVM flags guide.
Monitoring TPS
Use /forge tps in the console to check tick rate. A healthy ATM10 server should maintain 17–20 TPS. If you are consistently below 15, profile the server using Spark (usually bundled with ATM10) by running /spark profiler start, letting it run for 60 seconds, then /spark profiler stop. The report will show which mods and tick operations consume the most time. Astroworld Hosting supports ATM10 with NVMe storage and up to 96 GB RAM, ideal for this heavyweight pack. For general optimization strategies, our optimization guide covers the fundamentals.
Looking for modpack-ready hosting? Astroworld Hosting offers NVMe SSD, up to 96 GB RAM, and the Pterodactyl panel on every plan. See modpack hosting , plans from €6.39/mo.