Crash diagnosis table
| Crash pattern | Likely cause | First fix |
|---|---|---|
| Window opens and closes immediately | Missing .NET 8 Runtime or hidden launch error | Run from terminal and check .NET 8. |
| Crashes after config edit | Broken JSON, wrong value, or wrong config file | Restore the last working config. |
| Crashes while loading world | Save problem, wrong world path, or update mismatch | Preserve files and test a backup. |
| Crashes after update | Changed files, mismatched config, or damaged save | Back up current state and validate server files. |
| Crashes under player load | CPU, RAM, upload, or host instability | Lower load and check server requirements. |
Safe crash recovery steps
- Stop restarting repeatedly if the same crash happens.
- Copy the current save folder, config file, and latest logs.
- Launch from PowerShell, Terminal, or SSH so the error stays visible.
- Check for .NET 8 Runtime errors first.
- If the crash started after a config edit, restore the last working config.
- If the crash started after an update, validate files only after preserving saves.
- Test with one player before reopening the server to the full group.
Do not hide crashes with auto restart
Auto restart is useful for a stable server, but it can hide a real crash loop. If the server keeps crashing, fix the root cause before adding scheduled restarts or service managers.
Related Romestead server guides
Start with server logs location, fix runtime issues with .NET 8 Runtime, repair settings with config.json explained, recover saves with world not loading, and avoid unsafe restarts with server auto restart.