All the Mods 10 Server Setup: Installing ATM10 Server Files

All the Mods 10 (ATM10) is one of the biggest modpacks you can put on a server: 465 mods, over a gigabyte of server files, and a start script built for a machine you control. On a panel server that script never runs, so the settings it would have applied are yours to set. This guide walks through an ATM10 server on GameServerKings, from the Startup tab to the first login, and covers updating the pack without losing the world.

Figures are from ATM10 8.2, released 22 September 2026, and its official server files. If you're installing a later release, check its changelog and server files for the same values.

ATM10 at a Glance

Step 1: Size the Server for 8 GB

ATM10's own server files give Java an 8 GB maximum heap. Treat that as the target, not a stretch goal.

Our servers don't read user_jvm_args.txt. The startup command uses -XX:MaxRAMPercentage=95.0, so the heap is 95% of your plan's RAM and there is no memory field to change. To match the pack's 8 GB heap, choose a plan with at least 8 GB of RAM, and more if several players will spread out and load chunks at once. Minecraft Server RAM and JVM Flags explains why the extra headroom matters.

Disk matters too. During install the 1.22 GB zip and its 1.34 GB of contents sit on the disk together. Delete the zip once it has been unpacked.

Step 2: Set NeoForge 1.21.1 in the Panel

1. Take a backup from the Backups tab if the server has anything on it (How to create a backup).
2. Startup tab: Framework NEOFORGE, Minecraft Version 1.21.1, Docker Image Java 21.
3. Settings → Reinstall. The install script downloads NeoForge and sets the server to launch it. Reinstalling removes only the loader's files. Worlds, mods/, config/ and server.properties stay.

The script installs the newest non-beta NeoForge for 1.21.1, which was 21.1.252 when we checked. That's one build ahead of the 21.1.251 that ATM10 8.2 pins. The Build Number variable doesn't apply to NeoForge. We haven't booted ATM10 8.2 on that newer build ourselves. If the console shows the pack refusing to start because of the NeoForge version, contact support and we'll help you get the build the pack pins.

Step 3: Download and Upload the Server Files

1. On the ATM10 CurseForge page, open Files, click the version your players will use (8.2 here), and download ServerFiles-8.2.zip from that file's Additional Files. The CurseForge app can't download server packs. It has to come from the website.
2. Upload the zip over SFTP (port 2022). At 1.22 GB it's far over the 100 MB browser upload limit on most nodes. See How to upload files via SFTP.
3. In the Files tab, open the zip's menu and choose Unarchive. The zip has no wrapper folder, so mods/, config/, kubejs/ and the rest land directly in the server root. That's where they belong.
4. Delete the zip.

Three files in the zip do nothing on our servers, and you can delete them or leave them: startserver.sh/startserver.bat and neoforge-21.1.251-installer.jar (the panel installed NeoForge in step 2), and user_jvm_args.txt (memory comes from the plan).

Step 4: Apply the Settings the Start Script Would Have Written

On a home PC, ATM10's startserver.sh creates server.properties with its own defaults the first time it runs. On a panel server it never runs, so the server starts with vanilla defaults instead. Set these yourself in server.properties (Files tab), with the server stopped:

Leave server-port and server-ip alone. The panel rewrites them on every boot. Every other key is in Minecraft server.properties: The Complete Reference.

Step 5: First Start

Start the server and watch the Console. With 465 mods, expect a much longer first boot than on a plain server.

Server was on Paper before?

New servers start on Paper. If you're keeping a world Paper created, the first NeoForge start can fail with Missing data pack paper. Set Extra Flags to --safeMode, start once, stop, clear Extra Flags. For ATM10, a fresh world is usually the better choice anyway.

Players install ATM10 8.2 through the CurseForge app (or Prism) and join by address. If a launcher offers them a newer release, they must pick the version the server runs.

Updating ATM10 to a New Release

ATM10 ships frequent updates (8.0, 8.1 and 8.2 came out between 14 August and 22 September 2026). Each one needs its own server files.

1. Read the changelog on CurseForge, or in the pack's GitHub repository, for anything that says a new world is needed.
2. Back up, then stop the server.
3. Delete mods/, kubejs/ and defaultconfigs/, and replace them from the new server files. Leftover jars from the previous release are a classic duplicate-mod crash.
4. Replace config/, but first save a copy of any config you changed yourself. This is also how quest and recipe fixes reach you, because they live in config/ftbquests and kubejs/.
5. Keep world/ and server.properties.
6. Check the new startserver.sh for its NEOFORGE_VERSION. If it changed, reinstall from Settings to fetch a current NeoForge build.
7. Start, check the console, then tell players to update.

Removing a mod removes its blocks and items from the world. Missing Mods in World explains what happens and why the backup matters.

When Something Goes Wrong

• Player can't join with a channel or mod-list error. They are on a different ATM10 release. Match the exact version: see Mismatched mod channel list.
• java.lang.OutOfMemoryError after an hour or two. The heap is too small for the pack. On our servers that means a bigger plan. See OutOfMemoryError: Java heap space.
• Can't keep up! spam. Common during early world generation. If it continues, lower view-distance and simulation-distance further and look for runaway machines with spark.
• Server stops itself during generation. Check that max-tick-time is 180000 as above.
• Java error on start. The Docker image isn't Java 21. Change it and restart. No reinstall needed.
• Recipes or quests look vanilla. kubejs/ or config/ didn't unpack. Re-unarchive the server files.

The workflow for every modpack, not only ATM10, is in How to Make a Modded Minecraft Server. For stack traces, see Reading Minecraft Server Logs and Crash Reports.

---

Made with 💜 by GameServerKings