All The Mods 10 server setup on Hostd

ATM10 is a kitchen-sink NeoForge pack on Minecraft 1.21. Pick the Heavy tier, install in one click, and apply two server.properties tweaks before you invite people.

The short version

All The Mods 10 is a kitchen-sink NeoForge pack on Minecraft 1.21. Pick the Heavy tier at 10 GB, install the pack in one click from the Modpack tab, and let first boot finish before anyone joins. Then set max-tick-time to -1 and lower view-distance before you invite people.

All The Mods 10 (ATM10) is a 350+ mod kitchen-sink pack on Minecraft 1.21 NeoForge. It is the most popular kitchen-sink pack of the 1.21 era and the one most people land on after Better MC and ATM9. Hostd installs ATM10 in one click; the only decisions you need to make are the tier and the seed.

#Pick the right tier

ATM10 needs the 10 GB plan at minimum. With 4 to 6 players actively spread across the world, expect to use 7 to 8 GB of heap; that leaves enough headroom for chunk loads not to thrash. With 8+ players, or once one of you starts a Mekanism digital miner running, move to the 14 GB plan.

The 6 GB Modded tier looks tempting because the install will technically finish on it. The TPS will not survive first contact with a populated chunk; do not try it.

#Installing the pack

At order time: on the Minecraft Java Configure page, toggle Modded, search "All The Mods 10", and pick it. The download happens during provisioning so the dashboard will show "Installing modpack" for a couple of minutes after the server is up.

On an existing server: Dashboard → your server → Modpack → search "All The Mods 10" → Install. Take a backup first if you have anything you want to keep (Taking a manual backup); we replace the mods folder cleanly but the world conversion from another pack rarely goes well.

#First boot

The first boot takes 5 to 10 minutes:

  1. NeoForge loads the mod jars (about a minute on Heavy).
  2. Worldgen registers every dimension and biome the pack adds (about two minutes).
  3. The spawn chunk is generated and pre-loaded.
  4. The server prints "Done" and starts accepting connections.

Watch the Console panel during this; the line "For help, type help" means you can join. Connect with the address shown on the Connect tab.

#server.properties tweaks worth doing

ATM10's defaults are fine for most groups, but two settings are worth changing early:

  • view-distance=8. The pack defaults to 10. Drop to 8 (or even 6 on Heavy with several players); the TPS gain is real and the visible difference is small.
  • simulation-distance=6. Lower than view-distance, because simulating mob AI further out than 6 chunks is what makes the tick spike.

Edit them in Files → /data/server.properties and restart.

#Pre-generate the world

ATM10 has heavy worldgen: lots of dimensions, lots of structures. Running Chunky, which loads on NeoForge, to pre-generate a 2,000 block radius around spawn saves a lot of lag spikes when your players first explore.

/chunky radius 2000
/chunky start

Let it run overnight; the dashboard shows the progress.

#Where to go next

#Frequently asked questions

How much RAM does an ATM10 server need?

10 GB is the floor, not the recommendation. All The Mods 10 is a kitchen-sink pack and the mod count alone eats several gigabytes before a single player connects. Running it on 6 GB produces constant chunk-load stalls and eventual heap errors.

Why does ATM10 take so long to start the first time?

First boot generates the world, builds mod registries and writes config files for several hundred mods. Ten minutes or more is normal. The dashboard shows live install progress, and joining before it finishes is how people convince themselves the server is broken.

What server.properties settings should I change for ATM10?

Set max-tick-time to -1 so the watchdog does not kill the server during a long chunk generation, and drop view-distance to around 10. Both changes cost you very little and remove the two most common sources of ATM10 complaints.

Written and maintained by the Hostd engineering team. Last updated 2026-05-23. Notice a mistake? Tell us.

Keep reading