How do I start an All the Mods 10 (ATM10) server?

All the Mods 10 (ATM10) is the big all-round modpack of the moment: over 400 mods on NeoForge for Minecraft 1.21.1, covering everything from tech and magic to exploration. A pack this size does make demands on your server: with too little RAM it won't even survive the first boot. In this guide you'll install ATM10 step by step through the panel, pick a plan with enough memory and set the key performance options, so your ATM10 server stays smooth even with a full group of players.

Step 1: Install ATM10 via the modpack installer

1. Log in to the MC-Node panel at panel.mc-node.net and open your Minecraft server.
2. Already running a world on this server? Create a backup first via the Backups tab — the installation replaces your server files.
3. Open your server's modpack installer and search for All the Mods 10.
4. Select the latest version of the pack and start the installation. The installer downloads the server files and sets up the matching NeoForge version automatically.
5. Write down the exact version number you install: your players will need precisely the same pack version on their client.

Can't find ATM10 in the list, or do you prefer uploading the server files yourself? Follow how to manually install a modpack. Want to know more about the difference between NeoForge and other server types? Read which Minecraft server software should I choose.

Step 2: Pick enough RAM (10–12 GB as a baseline)

The RAM recommendation on the pack page is a client value. A server has to keep track of the chunks, machines and mobs of all players at once, so it needs more. For an ATM10 server, use these guidelines:

• 1–5 players: 10–12 GB
• 5–15 players: 12–16 GB
• 15+ players or heavy automation: 16 GB or more

Torn between two plans? In how much RAM does your Minecraft server need you'll learn which signals tell you it's time to upgrade and why the Java heap is always smaller than your plan.

Step 3: The first boot takes a while — that's normal

1. Go to the Console tab and start the server.
2. On the first boot NeoForge sets up its libraries and over 400 mods load their registries and configs. Expect 5 to 15 minutes before the server comes online.
3. Don't restart in the meantime, even if the console seems to pause. Only if nothing at all appears in the console for ten minutes or more is something actually wrong.
4. The server is ready once you see Done (…)! For help, type "help". Later boots are noticeably faster, usually within a few minutes.

Performance: keeping ATM10 smooth

Three measures deliver by far the biggest gains:

1. Pre-generate your world with Chunky. Chunky ships with ATM10. Type chunky radius 3000 in the console, then chunky start. The server will generate all chunks within 3000 blocks of spawn in advance. Generating new terrain is the biggest source of lag in a large pack, so run this overnight or while nobody is online — the work is then already done before your players start exploring.
2. Lower the simulation distance. Open server.properties via the Files tab and set simulation-distance=6 and view-distance=8. Also set sync-chunk-writes=false; this makes writing chunks to disk considerably lighter. Restart the server to apply the changes.
3. Limit force-loaded chunks and hunt lag sources with spark. The spark profiler is included in the pack: spark tps in the console shows your tick times, and spark profiler start (followed a few minutes later by spark profiler stop) shows exactly which machines or mob farms cost the most time. Also keep the number of chunks players force-load through FTB Chunks limited — everything that's force-loaded keeps ticking even when nobody is online.

Common problems

• Server ends up in a crash loop during startup — If you see java.lang.OutOfMemoryError: Java heap space in the console, or the server keeps dying while loading the world, it doesn't have enough RAM. With less than 10 GB, ATM10 rarely makes it through startup reliably. Upgrade your plan and try again.
• Players can't join ("Incompatible mod set" or missing mods) — The pack version on the client doesn't match the one on the server. Compare both version numbers and update the client in the launcher, or install exactly the same version on the server as your players are using.
• Updated the pack and now the world is broken — Never update without a backup. Mods are sometimes removed between pack versions, and their blocks and machines then vanish from your world. Restore your backup via the Backups tab and read the pack's changelog before trying again.
• Lag whenever players explore new areas — The world hasn't been pre-generated far enough. Run Chunky again with a larger radius at a quiet moment.

Ready for your first players

Your All the Mods 10 server is now running with enough RAM, a pre-generated world and sharp settings. As a finishing touch, set up a daily automatic backup via the Schedules tab — with a pack this size you always want a recent restore point. Stuck somewhere? Open a ticket via our support page and include your server name and the last lines from the console.