If Minecraft Java Edition reports an entity ticking error, first check whether you have a crash or a lag warning. A crash report that says “Ticking entity” means an entity threw an error while the game was updating it. The console warning “Can’t keep up! Is the server overloaded?” means the server is falling behind. These problems can look similar in play, but they need different fixes.
Use the five-step process below to protect your world, identify the cause, and apply the smallest useful change. It covers the common Minecraft entity ticking error and server lag without relying on risky blanket commands or outdated settings advice.
Minecraft continuously updates entities such as mobs, villagers, minecarts, dropped items, and players. If an update fails for one entity, Java Edition may stop with a crash report containing “Description: Ticking entity.” The report may identify the entity type, dimension, coordinates, exception, and code path. That evidence points toward a specific entity, mod, plugin, or game bug.
By comparison, “Can’t keep up!” is a server performance warning. It appears when the tick loop cannot keep pace with its schedule. An entity-heavy farm can contribute, but so can chunk generation, redstone, plugins, mods, or limited CPU capacity. The older warning text mentions a possible system clock change; that wording does not make clock synchronization a routine fix. Change time settings only if your operating system clock is actually wrong or jumping.
| What you see | What it usually indicates | Start here |
|---|---|---|
| Crash report says “Ticking entity” | An entity update threw an exception | Read the report’s entity, location, and stack trace |
| “Can’t keep up!” in the log, with rubber-banding | The integrated or dedicated server is behind | Profile performance while the lag is happening |
| Low FPS without server warnings | Client rendering or local device load | Check graphics settings and client performance |
For a dedicated server, shut it down cleanly before changing world files, plugins, or configuration. Copy the entire server folder, including the world, mods or plugins, configuration files, and logs. Work on a duplicate if possible. PaperMC’s basic troubleshooting guide also recommends stopping the server and backing it up before investigation. In single-player, exit the world and copy its save folder before trying recovery steps.
For a crash, keep the full crash report and note the Minecraft version, mod loader, entity type, dimension, and coordinates. Look at the exception message and the first useful lines of the stack trace; a mod or plugin name there is a valuable clue. Also check logs/latest.log for the events immediately before the crash. For a lag warning without a crash, note when it happens: near a farm, while exploring new terrain, after a player joins, or only with a particular plugin enabled.
Do not delete region files or remove every entity as a first response. Broad removal can erase villagers, pets, item frames, armor stands, and valuable drops while leaving the actual cause untouched.
If the server is running Paper, the Paper profiling guide recommends Spark, which has been bundled with Paper since Minecraft 1.21. Start a profile during the lag with /spark profiler start --timeout 600. The command returns a report link after the ten-minute sample. Profiling when the server feels normal can miss the workload causing the slowdown.
Use the report to see whether time is going to entity updates, chunk loading, a plugin, or another task. If you are on Vanilla, Fabric, or Forge, use documentation for that server and loader rather than assuming the Paper command or plugin applies. A client frame-rate problem is different from server tick lag, so compare the in-game experience with the server log.
If entity updates dominate, inspect farms and busy chunks for crowded animal or mob pens, piles of dropped items, minecarts, long hopper chains, and continuously active redstone. Reduce or pause one suspected source, then repeat the same activity and compare. Avoid applying an arbitrary “entity cap” value: max-entities is not a standard Java server.properties setting.
For a Java server, you can test a lower simulation-distance to reduce how far from players the server updates living entities. view-distance controls how much world data the server sends to clients; lowering it can help chunk or network load, but it is not the same as directly fixing one bad entity. Check your server software’s documentation and change one value at a time. Paper’s server properties reference explains both settings. Make a backup, stop the server before editing, restart, and retest.
Changing randomTickSpeed affects random block updates, not the normal ticking of mobs. Disabling synchronous chunk writes is not a general entity-lag fix and can affect how data is saved; do not copy that old recommendation without a specific, documented reason.
If the crash always occurs when a particular area loads, use the report’s coordinates to narrow the investigation. Check that the server jar, Minecraft release, loader, mods, and plugins are compatible with one another, then update only components whose maintainers document support for that exact release. If a plugin appears in the stack trace, test with it disabled on a copy. PaperMC documents a binary-search approach for narrowing down plugin conflicts; keep dependent library plugins together while testing. For a Vanilla server jar, use the official Minecraft Java server setup instructions and match the server software to the world you are testing.
If a single entity still crashes a copied world, ask the responsible mod or plugin maintainer for a version-specific fix. As a last resort, use a reputable region-editing tool on the duplicate to remove only the identified entity, following that tool’s own documentation. Confirm the world opens and behaves correctly before replacing the original save.
After each change, repeat the conditions that previously caused the warning or crash and check the log again. For server lag, compare profiler results and note whether movement, block interaction, and mob behavior improve. For a ticking-entity crash, confirm the same chunk can load without producing another crash report. If one change makes no measurable difference, restore the backup or revert that setting before trying the next idea.
The key to resolving the Entity Ticking Minecraft Error is to separate a failing entity from an overloaded tick loop. Preserve the report, protect the world, and let the log or profiler determine whether the next step is entity cleanup, server tuning, or a mod/plugin fix.
Set Super Smash Bros. Ultimate Quickplay to prefer hazards-off stages. Follow the Preferred Rules menu steps and learn why matchmaking may not always honor them.
Enable Server Latency and Packet Loss in Warzone to monitor connection quality, read the overlay, and use recurring spikes to guide troubleshooting.
Learn how to carry from mid lane in League of Legends by setting up waves, choosing safe roam windows, reading side lanes, and converting pressure into objectives.
Fix Minecraft Evoker spell problems with a safe vanilla test, version checks, log review, and a step-by-step way to isolate mod or datapack conflicts.
Fix PUBG stuck on Initializing on Steam with a focused checklist for PC service notices, launch options, game files, downloads, and connection issues.
Fix Brawl Stars stuck at 92% loading with an ordered checklist for service notices, network tests, safe updates, Android cache, and account-safe reinstalling.
Best Dead by Daylight visual filter settings start with a small Gamma lift, neutral color and contrast, and a quick check for dark corners, fog, and bright lights.
Find the Steam and EA app fields for Apex Legends launch options, use EA’s documented FPS command, and see why +exec autoexec.cfg remains unverified.
Reduce input lag on a Nintendo Switch dock for Smash Ultimate with TV Game Mode, a direct HDMI test, controller checks, and online-latency troubleshooting.
Find the best EA SPORTS FC audio settings for a clearer referee whistle: tune Stadium Ambience and Commentary, then troubleshoot output or timing issues.
