NexthostingLogs

Logs / Error guide / Minecraft

Minecraft: “Exception in server tick loop” and reading crash reports

What the message means

While the server was computing a tick, an error occurred that nobody caught. The server stops and writes a crash report to the crash-reports folder. The message itself is generic – the cause is a few lines below it.

What it looks like in the log

[21:15:40] [Server thread/INFO]: Starting minecraft server version 1.20.1
[21:15:52] [Server thread/INFO]: Done (12.044s)! For help, type "help"
[22:03:17] [Server thread/ERROR]: Encountered an unexpected exception
net.minecraft.ReportedException: Ticking block entity
at net.minecraft.server.MinecraftServer.tickChildren(MinecraftServer.java:1032)
Caused by: java.lang.NullPointerException: Cannot invoke "net.minecraft.world.level.Level.getBlockState()" because "level" is null
at com.example.pipes.block.PipeBlockEntity.tick(PipeBlockEntity.java:88)
[22:03:17] [Server thread/ERROR]: This crash report has been saved to: /home/container/crash-reports/crash-2026-11-14_22.03.17-server.txt

Excerpt from an example log, marked the way the analysis marks it.

Common causes

  • A mod or plugin throws an error in a block, item or entity (“Ticking block entity”, “Ticking entity”).
  • A corrupted chunk or block after a crash or mod change.
  • Out of memory (then OutOfMemoryError is directly below).
  • Two mods that interfere with each other.

How to fix it

  1. Read the lines under the message down to the first “Caused by”: that's where the actual exception is, usually with a package name that belongs to a mod.
  2. If “Ticking block entity” or “Ticking entity” is in the report, the section below it gives the coordinates. Remove the block or entity there (back up first!) or update the mod it belongs to.
  3. Update the affected mod or remove it as a test.
  4. If the crash always happens at the same spot in the world, restore a backup of that region.