#crash

Most bots go offline because the code crashes, runs out of memory, uses an invalid token or missing intents, hits Discord rate limits, or the service is suspended for an unpaid invoice.

Restoring a backup is the safest fix for a corrupted world. If you have none, level.dat_old and region editors like MCA Selector can save most of it.

The server crashed while updating the world. The crash report names the cause, often one broken entity or block entity at specific coordinates. Remove it carefully, with a backup first.

Your server writes everything to logs/latest.log and saves crashes in the crash-reports folder. Here is where to find them and how to spot the line that matters.

A server that stops right after Start prints the reason in the Console. Usually it's a broken plugin or mod, the EULA, wrong Java after a manual change, or a full disk.

java.lang.OutOfMemoryError means the server needed more memory than it has. Find what is using it (too many chunks, entities, plugins or a big modpack) before you upgrade.