If your modpack won't start, read the recovery card above the console first. MineXEngine identifies what stopped the pack and says what it did. Some fixes it makes on its own, such as moving a client-only mod aside. When a pack needs a change the engine isn't sure about, it shows a recommendation and asks you first.
Read the recovery card
When a start fails, a card titled MineXEngine · recovery appears above the console. It has two parts:
- What happened: what went wrong during startup.
- What we did / next: what the engine did, and what you can do now.
The headline uses the engine's own words, such as fixing a startup problem, your server recovered, or couldn't auto-fix this one. A chip beside it shows the state, for example Recovering or Needs attention. Press Dismiss to hide the card; the same lines stay in the console. If the server shows as crashed, press Start to bring it back.
When the pack needs a change
Some packs only start after a mod is taken out. Then you see the banner This pack has a recommended change.
- Click View recommendation. The window, This pack needs a change before it will start, names each file it wants to move. Click Show the crash details to see the error behind it.
- Choose one option:
- Apply the recommended change: the listed files are moved aside into a quarantine folder on your server. Nothing is deleted.
- No: nothing is moved, and the server stays down.
- Run unsupported (no auto-repair): the engine still launches the server but stops trying to fix it. A crashing mod is not moved aside, and the server is not restarted for you.
- Your choice is saved, but the server does not restart by itself. Press Start or Restart to apply it.
Files you move by applying a recommendation go to .mx-quarantine/ in your server's main folder. Mods the engine moves on its own go to mods/.quarantined/. Nothing in either folder is deleted, so you can move a file back with the File Manager. To stop the window opening by itself for this pack, click Don't show again for this pack; the banner stays.
Sometimes the engine can't tell what is wrong. It then says it doesn't yet know why the pack fails and that the pack is not supported by automatic repair for now. Try the other steps on this page.
Automatic repair
Under the console, the Automatic repair tile shows ON or OFF. ON is the default. Turning it off asks you to confirm with I understand, turn automatic repair off. Installing a different pack, or a different version of this one, turns it back on.
With automatic repair ON, the engine removes known client-only mods before boot. If a client-only or unreadable mod file stops the server from starting, it can move that file aside without asking. It can also fetch a missing dependency or repair a broken install. For any other mod that crashes the server, it names the mod and asks you first.
Check the logs yourself
- The console toolbar has buttons to copy all output, download the log file, and share the log to mclo.gs. The mclo.gs button copies a link, and player IP addresses are masked before upload.
- Crash reports are in the
crash-reportsfolder in the File Manager.
Other ways to get running
- Rollback puts the server back to how it was before a change you made, such as a modpack install. See Roll your server back.
- Backups restores an earlier backup. This replaces the whole server folder, not only the world.
- Modpack Installer lets you install a different version of the pack.
- Memory: the panel does not warn you when a pack needs more RAM than your plan has. Watch the Memory tile on your server's page and Memory pressure in Health. If memory sits near your plan's limit, a bigger plan may help. See Memory and Estimated RAM.
If you open a ticket about this, include your mclo.gs link and what the recovery card says. Tickets don't take attachments.