MineXEngine
MineXEngine is the software inside every MineXHost server that sets your modpack up, starts it, and repairs the start failures it can fix safely.
A pass means the modpack installed, started, stayed running through a stability check and answered a server-list ping, or, if the modpack turns that reply off, accepted a connection on its game port. No player joins during the test. See every result
What happens when you install a modpack
Standard one-click install
- Downloads the modpack files
- Uses a template Java version and launch flags
- Starts the server
- If it crashes: you read the log, or open a ticket
MineXEngine
- Detects the mod loader and Minecraft version
- Picks the Java version the server jar needs
- Sizes Java memory flags to your plan
- Sets aside mods a server cannot or should not run, such as client-only and world-backup mods
- Starts the server
- If it crashes:
- A missing dependency: fetches it
- A client-only mod crashed it: moves it aside, and you can put it back
- Another mod is at fault: names the mod and asks you, apart from a few narrow cases
- Your panel shows “Booted cleanly” or “Booted after MineXEngine repaired it”
What it repairs
A missing dependency
A mod needs another mod that the pack did not include. MineXEngine fetches the missing mod and starts the server again.
A mod made only for the game client
Some packs ship mods that only work in the game client, such as menus or shaders, and a server cannot load them. MineXEngine sets aside the ones it has identified as client-only before the first start, and moves one aside if it crashes the server. A moved mod can be put back.
A second copy of a mod
When a pack installs the same mod twice, the server refuses to start. MineXEngine moves the extra copy aside.
The wrong Java version
Each Minecraft version needs a particular Java version. MineXEngine reads the one the server jar needs and starts with it, from Java 8 for older packs up to Java 25.
What it won’t do without asking
After a crash, MineXEngine does not remove the mod that crashed your server. It names the mod in your panel and asks you first, and nothing changes until you decide.
The exceptions are narrow: a client-only mod that crashes the server, a second copy of a mod, a mod whose mods.toml file is broken, a mod MineXEngine has shown stops the server from starting while it is installed, and the existing copy of a dependency it replaces with the version another mod needs.
Before the first start, it also sets aside mods a server cannot or should not run, such as mods made only for the game client, a second copy of a mod, a mod file too damaged to open, and world-backup mods, because the panel already backs up your server.
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.
When a start fails for a reason MineXEngine cannot repair, it stops and your panel shows what happened, instead of restarting forever.
How we test
Our QA Lab installs public CurseForge and Modrinth modpacks on test servers running MineXEngine, starts them, and records whether each one passes. No player joins during the test, so gameplay is not tested. Test servers can remove a mod that crashes them without asking, which customer servers do only in the narrow cases above, so the test results page shows how the passing modpacks started, including whether they needed a repair, and lists the ones that failed, with the reason.
Questions
Is MineXEngine AI?
No. Ordinary code: known crash signatures, each mapped to a specific fix.
Does MineXEngine remove my mods?
Before the first start it sets aside mods a server cannot or should not run, such as mods made only for the game client, a second copy of a mod, a mod file too damaged to open, and world-backup mods, because the panel already backs up your server. After a crash it names the mod at fault and asks you, except in a few narrow cases where it moves a mod aside: a client-only mod that crashes the server, a second copy of a mod, a mod whose mods.toml file is broken, a mod it has shown stops the server from starting while it is installed, and the existing copy of a dependency it 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.
Does every modpack start?
No. We test public modpacks on MineXEngine and publish pass rates by version, along with the modpacks that failed and why, at minexhost.com/test-results.
How is a test server different from my server?
A test server can remove a mod that crashes it without asking, and it may get more memory than your plan. Your server names the mod and asks you first, apart from the narrow cases above, and runs with your plan’s memory, so a large pack that passes a test can still run out of memory on a small plan.