World and tick crashes

Ticking memory connection — the single-player server lost the client

What it looks like in the log

ticking memory connection
ticking connection

How to fix it

  1. In single player the game runs a server inside itself; this is a packet it could not handle
  2. The Caused by: block below names the mod that sent or read it
  3. Nearly always a mod sending more data than the packet allows
SeverityStops the game
CategoryWorld and tick crashes

Check your own log

Related errors

World and tick crashesAdding Entity to Track (Entity Is Already Tracked)Read the stack trace directly below 'Adding entity to track' or 'spawnEntity' to check if a specific mod or plWorld and tick crashesCreate Contraption Crash: Cannot read field "x" because "mf.axis" is nullUpdate the Create mod (and any Create add-ons) to the latest version newer than 6.0.10, which includes the upsWorld and tick crashesIllegalStateException: Do not call getCapability on an invalid cache (Create Fluid Crash)Update the Create mod to the newest available 1.21.1 release, as multiple fluid capability cache bugs in FluidWorld and tick crashesLithium Chunk Reset: Could Not Initialize Block State FlagsClose Minecraft immediately without exploring further so no additional chunks are loaded and overwritten.World and tick crashesRendering Block Entity / Tesselating block in worldThe crash report block below the error names the block and its coordinatesWorld and tick crashesServer thread has not responded — Watchdog shut the server downThe trace printed by the watchdog shows what the tick was busy doing