How to Make an ATM10 Server

The short version

1. ATM10 runs on Minecraft 1.21.1 with NeoForge, so the server needs Java 21.
2. Use the official server pack published with each release on the pack's CurseForge page — not the client files.
3. Give it enough memory. Plan on 16 GB for a small group and 20 GB for more players. This is the single decision that makes or breaks an ATM10 server.
4. Keep every player on the same version. ATM10 updates often, and the server and every client must match.

On a hosted server, steps 1 and 2 disappear: the panel's installer puts the pack, NeoForge and the right Java in place for you.

What ATM10 needs, checked against its release data

ATM10 releases frequently — version 8.2 came out in September 2026, a few weeks after 8.1. That pace is good for the pack and a trap for servers: a server and a client one version apart usually cannot talk to each other. Decide as a group when to update, and update everyone together.

If a bug looks like the pack's rather than yours, the GitHub tracker above is where the ATM team collects reports, and searching it first often turns up the fix.

How much RAM an ATM10 server really needs

ATM10 loads hundreds of mods before the first player joins, and every player adds their own loaded area — plus whatever machines and chunk loaders they have built. That is why an ATM10 server that starts fine can fall over a month later, once the factories are running.

Why not less? A 9 GB plan will often start ATM10 and even run it for one or two players early on, but it leaves no headroom: garbage collection pauses get longer, the server stutters when someone explores, and it runs out of memory as bases grow. 16 GB is where ATM10 stops being a constant fight.

And why not simply more? Past what the pack needs, extra memory does not make ticks faster — Minecraft's world simulation runs mostly on one core. What helps then is pre-generating the world, keeping the view distance moderate, and watching for the one runaway machine that is loading chunks for no reason. For the general sizing logic, see how much RAM a Minecraft server needs.

Path A: run the server pack yourself

Self-hosting ATM10 is possible on a strong PC, but remember the machine has to carry both the server and, if you also play on it, a client that wants a lot of memory of its own.

1. Install Java 21 and check it with java -version.
2. Download the server pack for the exact version you want from the ATM10 page on CurseForge, and unzip it into an empty folder.
3. Run the pack's start script. It installs NeoForge on the first run and creates the usual NeoForge files, including user_jvm_args.txt. Accept the EULA in eula.txt when asked.
4. Set the memory in user_jvm_args.txt. The file ships with the line commented out and a note that 4 GB is a good default for a modded server — ATM10 needs far more:

   -Xmx12G

   Leave room for the operating system: on a 16 GB machine, 12 GB for the server is about the limit.
5. Start it and be patient. The first start of ATM10 takes minutes, not seconds. Wait for the Done line.
6. Open TCP port 25565 for players outside your network; the port forwarding guide covers how, and when it cannot work.

For the general side of running modded servers yourself — loaders, mods versus plugins, keeping client and server in step — see how to make a modded Minecraft server.

Path B: one-click install on a hosted server

ATM10 is the pack our customers install most often through the panel, so this path is well trodden.

1. Pick a plan with enough memory — MC Emerald (16 GB) for a small group, MC Netherite (20 GB) for more, on HytHost modded Minecraft hosting.
2. Open the Modpacks tab in the panel, search for "All the Mods 10", and choose the version your players use.
3. Install. The installer downloads the server pack, installs NeoForge and runs the server on Java 21 — nothing to unzip or configure by hand, and the memory is set from your plan.
4. Start it and share the address. Watch the first boot in the console; it takes a few minutes.

The server stays online without your PC, on NVMe storage behind Voxility DDoS filtering, with a 99.9% Uptime SLA. If the pack will not start, live chat support is available from 8 AM to 11 PM (Chișinău time).

Updating ATM10 without losing the world

A pack update is the riskiest thing you will do to an ATM10 world. Mods get added and removed between versions, and a block from a removed mod simply disappears from every base that used it.

1. Back up the whole server first — the world and the config folders — and keep that copy until you are sure the update is fine.
2. Read the changelog for removed mods and for notes about world compatibility.
3. Update the server and every client to the same version, on the same day.
4. Start once and check the log for missing-block warnings before letting everyone back in.

If an update goes wrong, restoring the backup and staying on the previous version is always a valid choice. There is no rule that a server must run the newest release.

Common ATM10 server problems

Players are kicked right after joining

A mismatched mod channel list or an internal exception on connect means the player's pack version is not the server's. It is not RAM and not the network: have them install exactly the server's version.

java.lang.OutOfMemoryError

The server ran out of the memory it was allowed. Raise -Xmx (self-hosted) or move to a larger plan — and if it happens only as bases grow, look for chunk loaders keeping large areas loaded.

The server stops with "A single server tick took 60.00 seconds"

The watchdog killed a server that froze, which on a pack this size is usually a very slow start or a huge first generation. Give it more memory first. As a last resort for slow starts, max-tick-time in server.properties controls that limit; -1 disables it.

UnsupportedClassVersionError at start-up

The server was launched on Java older than 21. ATM10 on Minecraft 1.21.1 needs Java 21.