NeoForge 1.20.1 Modpack Server Hosting

27 NeoForge 1.20.1 modpacks that MineXHost's QA Lab has tested often enough to report a result. Minecraft 1.20.1 servers run on Java 17; MineXEngine sets it up.

Each QA Lab test is a boot-and-ping test on a MineXHost QA server: MineXEngine installs the modpack, starts the server, and the server must stay running and answer a Minecraft server-list ping (or, if the pack turns that off, accept a connection on its game port). It does not measure sustained TPS, player joins or long-run stability.

A modpack gets a listed page when all of these hold: it is in our QA Lab's test catalogue; it has at least 5 public QA Lab tests with a clear result on MineXEngine 80.0.0 or newer and at least 50% of them passed; no defect in the pack itself is confirmed; a QA Lab test passed in the last 45 days; and its mod loader and Minecraft version are known, from how the pack is published (as resolved when a QA Lab test installed it) or from MineXEngine's detection in a QA Lab test. A loader and Minecraft version page like this one is listed once at least 5 of its packs are. Failures are included in every count; the full results are on the modpack test results page.

All modpack server pages, grouped by mod loader and Minecraft version.

Other NeoForge versions

• NeoForge 26.3 modpack server hosting (5 packs)
• NeoForge 26.2 modpack server hosting (6 packs)
• NeoForge 26.1.2 modpack server hosting (11 packs)
• NeoForge 1.21.1 modpack server hosting (381 packs)

These results come from MineXHost's QA Lab test servers. Test servers differ from customer servers:

• Test servers may automatically remove a mod that crashes the server.
• On a customer server, MineXEngine sets aside mods that cannot or should not run there before the first start, such as mods made only for the game client, a second copy of a mod that is installed twice, a mod file too damaged to open, and world-backup mods, because the panel already backs up your server. After a crash it fetches a missing dependency on its own. A mod that crashes the server is named, and you decide whether to remove it.
• After a crash, a customer server moves a mod aside without asking only in a few narrow cases: a mod whose mods.toml file is broken, a client-only mod that crashes the server, a mod MineXEngine has shown stops the server from starting while it is installed, a second copy of a mod that is installed twice, and the existing copy of a dependency that MineXEngine replaces with the version another mod needs. An empty mod file is removed. Every other mod MineXEngine sets aside is moved into a separate folder, not deleted, and can be put back.
• Test servers get 12 GB of memory. Plans start at 3 GB, so a large modpack that passes here can run out of memory on a smaller plan.