Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Playing with friends? Godlike.Host runs hosted Minecraft Java servers from 10 data-center locations, with free DDoS protection.
“Exception in server tick loop” is a crash wrapper, not a diagnosis. The reliable fix comes from the first Caused by: line and the deepest useful entries beneath it. One report may identify an old server’s JSON list files; another may identify a mod, an unregistered dimension type, a Superflat upgrade failure, or a damaged installation. Stop making changes, back up the world, capture the crash report or latest.log, and then follow only the branch that matches the stack trace.
What the error means
Minecraft’s server tick loop is the repeating process that advances the game simulation: entities, block updates, world generation, scheduled tasks and other server work. When an exception escapes that loop, Minecraft stops the server and often presents the generic headline Exception in server tick loop.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Minecraft | Java & Bedrock Deluxe Collection | Windows Digital Code | $39.99 | Buy on Amazon |
| 2 |
|
Minecraft | Java & Bedrock Ultimate Collection | Windows Digital Code | $49.99 | Buy on Amazon |
| 3 |
|
Minecraft | Standard Edition | XBOX Digital Code | $19.99 | Buy on Amazon |
| 4 |
|
Minecraft | $6.99 | Buy on Amazon |
| 5 |
|
Minecraft - Bedrock Edition PS4 | $42.98 | Buy on Amazon |
The headline does not identify the failing component. Mojang issue records show materially different causes under the same wording. MC-187673 records an unregistered dimension type, while MC-241778 records a Superflat-world upgrade crash involving biome decoration. Older hosting documentation records a separate NullPointerException pattern in net.minecraft.server.v1_7_R3.JsonList.load(JsonList.java:171), associated with JSON list files. Treating every occurrence as the same problem can destroy useful data without fixing the crash.
Do this before changing anything
- Stop the server or close the game. Do not repeatedly launch a world while files are being changed.
- Make a Java Edition world backup. In the official launcher, use Edit World → Make Backup. Minecraft Help says the backup is a dated ZIP file available from the backups folder. Keep that ZIP outside the installation you are troubleshooting.
- Save the evidence. Copy the crash report and
latest.logbefore deleting files or changing mods. Preserve the original so you can compare a later test. - Find the first
Caused by:line. Read downward to the deepest package, mod ID, file name, dimension, chunk or player named in the trace. The final exception and the first named Minecraft or mod component are usually more useful than the headline. - Choose one branch. Apply the narrow remedy indicated by the trace. Do not delete unrelated configuration files as a generic fix.
Identify the failing category
| What the trace names | Likely branch | First recovery test | How reversible it is |
|---|---|---|---|
JsonList.load, ops.json, whitelist.json or the old v1_7_R3 server package |
JSON-list variant | Stop the server, back up the files and recreate the named JSON lists | Restore the backed-up files if the test does not help |
| Forge, Fabric, NeoForge, a mod ID, a mixin or a configuration parser | Mod, loader or configuration incompatibility | Disable or roll back the named component and test the same game version with a clean profile | Re-enable components in small groups |
| Dimension type, biome decoration, chunk generation, entity data or one particular world | World, dimension, chunk or upgrade failure | Test a copy of the backup and create a new world on the same version | The original backup remains untouched |
| A clean installation launches only after removing old settings, or the trace points to the runtime environment | Installation, Java or memory problem | Create a clean installation on the same game version, then verify Java and launch settings | Copy old settings back selectively |
Branch A: repair the old JSON-list variant
Use this branch only when the stack trace points to JSON list loading. Hyper Layer describes the exact older-server pattern as java.lang.NullPointerException: Exception in server tick loop at net.minecraft.server.v1_7_R3.JsonList.load(JsonList.java:171). The implicated files are commonly ops.json and whitelist.json; the documented recreation procedure also removes usercache.json.
#1 Best Overall
- DELUXE COLLECTION — Includes Minecraft: Java & Bedrock Edition, three Bedrock add-ons, three exclusive Character Creator items, and 700 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
Procedure
- Stop the server completely and confirm that its Java process has exited.
- Open the server’s file manager or the directory containing the server JAR.
- Make a separate copy of
ops.json,whitelist.jsonandusercache.jsonbefore removing anything. - Delete those three files from the active server directory.
- Start the server again. Minecraft should recreate the files during startup.
- Check the new
latest.logand join the server only after startup completes without the same exception.
AleForge documents the same sequence and identifies those files as the usual cause for this exact older-server trace. This is a targeted repair, not a universal “tick loop” fix. If the trace names a mod, dimension, chunk or different file, stop and use the corresponding branch instead.
Branch B: isolate a mod, loader, mixin or configuration
If the deepest stack-trace entries name Forge, Fabric, NeoForge, a mod identifier, a mixin or a configuration parser, the failing component is more informative than the generic headline. A mismatch can occur after changing the Minecraft version, loader version, mod version or a configuration file.
Controlled rollback
- Record the Minecraft version, loader version and the exact mod or configuration named in the trace.
- Stop the server or exit the launcher.
- Disable or roll back only the named component. Keep the original file in a separate backup folder rather than overwriting it.
- Launch a clean profile on the same Minecraft and Java versions. Do not change several variables at once.
- Test the affected world or reproduce the action that caused the crash.
- If the clean profile works, re-enable mods in small groups. When the exception returns, divide that group again until one component or combination is isolated.
Minecraft Help states that modding is not officially supported and that Minecraft Support cannot assist with issues arising from mod usage. Mods are third-party software; once the trace identifies one, the mod author or mod-pack maintainer is the appropriate escalation path. Include the complete trace, game version, loader version and the smallest set of enabled components when reporting it.
What not to do in this branch
- Do not replace every configuration file before identifying the parser or mod named in the trace.
- Do not assume that installing more RAM will correct an incompatible mixin or malformed setting.
- Do not compare a modded test on one Minecraft version with a clean test on another; that changes the result you are trying to measure.
Branch C: world, dimension, chunk or upgrade failure
Choose this branch when the trace names a dimension type, biome decoration, chunk generation, entity data or one particular world. A new world is a diagnostic test, not proof that the old world is safe to delete.
Use a copy, not the original
- Keep the dated backup untouched.
- Duplicate the world folder and give the copy a test name.
- Run the copy with the same Minecraft version, loader and mods that created it.
- Create a new world with that identical software set.
- Compare the results: if the new world loads but the copy fails, the problem is associated with world data, a dimension or generated content rather than a basic installation launch.
MC-187673 documents an unregistered dimension type. MC-241778 documents a Superflat-world upgrade failure tied to biome decoration. Their listed fixes are historical records—1.16 Pre-release 3 for MC-187673 and 1.18 Pre-release 4 for MC-241778—not guarantees for current versions. They demonstrate why deleting unrelated settings or reinstalling Java cannot be assumed to repair world data.
When one location is named
If the report identifies a dimension, chunk, entity or player, preserve that information. Avoid teleporting repeatedly into the failing area or editing the original world until you have a restorable copy. A world-specific crash may require a version-compatible repair from the pack maintainer or a carefully targeted edit; the generic headline alone does not establish which data is safe to remove.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #2
- ULTIMATE COLLECTION — Includes Minecraft: Java & Bedrock Edition, five Bedrock add-ons, five exclusive Character Creator items, and 1000 Minecoins.
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that’s unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world filled with surprises.
- SURVIVE THE ADVENTURE — Face mysterious foes, travel across exciting landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play cross-platform with friends in Bedrock Edition on console, mobile, and PC, or join community servers in Java Edition on PC, Mac, and Linux. Online console multiplayer requires a platform-specific subscription (sold separately).
Branch D: test the installation, Java and memory
Clean-install test
Create a new Minecraft Java installation using the same game version. If it launches normally, Minecraft Help recommends troubleshooting downloaded mods or advanced settings from the old installation and copying defaults selectively. Move settings back one group at a time so a failing option can be identified.
A clean installation that still crashes does not prove that the world is corrupt. Return to the trace: a named mod, dimension or data file can fail in both installations.
Dedicated-server prerequisites
For a dedicated server, verify the basics in the official server setup guidance:
- Java is installed and up to date.
- The server JAR matches the intended Minecraft version.
- You launch from the server directory with the Java command rather than from an unrelated working directory.
java -jar server.jarReplace server.jar with the actual filename of your server JAR. A command that points to a different JAR or runs from the wrong directory can load the wrong files, but it will not explain a trace that clearly names malformed JSON or a world-generation component.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteReview JVM memory only when the evidence supports it
Minecraft Help explains that the maximum heap is controlled by the -Xmx value. Back up worlds before changing launch arguments. Official guidance says 32-bit systems top out at 4 GB and recommends no more than half of system RAM on 64-bit systems.
Memory is an environmental setting, not a cure for every crash. Increasing -Xmx will not repair malformed JSON, an incompatible mod or damaged world data. If the log shows an environmental memory failure, change the value conservatively, launch again and compare the new log with the saved original.
Rank #3
- CREATE YOUR WORLD — Build whatever you imagine in an infinite world that is unique in every playthrough.
- EXPLORE AND CRAFT — Discover biomes, resources, and mobs, then craft your way through a sandbox world full of surprises.
- SURVIVAL ADVENTURES — Face mysterious foes, travel across varied landscapes, and venture into perilous dimensions.
- PLAY TOGETHER — Play solo or join friends in local split-screen and cross-platform play across console, mobile, and PC. Online multiplayer supports up to 8 players.
- COMMUNITY PLAY — Connect with players on community servers, or subscribe to Realms Plus (sold separately) to play with up to 10 friends on a private server.
Read the log without guessing
Crash reports usually contain a short summary followed by a stack trace. Start at the earliest Caused by: entry and continue through nested causes; a later wrapper can hide the line that names the real file or component. Note the thread name, the Minecraft version, the loader, and any path or registry identifier that appears repeatedly. A line naming JsonList.load points to a different action than one naming a mixin callback or chunk-generation class.
Save both the report generated at the crash and the latest.log from the same attempt. If a second launch produces a different trace, keep both and label them by time. This prevents a successful test from overwriting the evidence from the failing run. For support requests, include the complete trace and the exact reproduction step rather than only the headline; the surrounding lines establish whether the failure is repeatable during startup, world loading or a particular in-game action.
How to compare recovery options safely
When more than one action appears possible, evaluate each option against four questions:
- Does the stack trace identify a file, mod or world? Prefer the action that directly addresses that named item.
- Can you reverse it? A dated world ZIP and copies of files make a test safer than deleting the only copy.
- Are the versions identical? Keep Minecraft, Java, loader and mod versions constant while testing one variable.
- Does it reproduce in a clean, unmodded installation? A clean result narrows the fault toward downloaded mods or advanced settings; a failure that follows the world points back toward data or generation.
| Recovery action | Best evidence for using it | What it can establish |
|---|---|---|
| Recreate JSON list files | JsonList.load and the old v1_7_R3 trace |
Whether the legacy list files are blocking startup |
| Disable one mod or loader component | A named mod ID, mixin, loader or config parser | Whether that component or its interaction causes the exception |
| Load a copied world and a new world | Dimension, biome, chunk or entity entries | Whether the failure follows existing world data |
| Launch a clean installation | Installation settings or runtime symptoms without a more specific name | Whether old downloaded files or advanced settings are involved |
Adjust -Xmx |
A log that indicates a memory or environment problem | Whether the configured heap is insufficient for that workload |
Managed hosting can make recovery safer
If you run the server through a hosting provider, prefer a plan with file-manager access and world backups. Those two features let you copy the crash report, preserve the dated world archive and recreate only the files named by the trace without waiting for a provider to perform every change. Confirm that you can download a backup and restore it before testing a risky world or mod change.
Hosting support is most useful when you provide the exact Minecraft version, server JAR, Java version, complete crash report and the steps that reproduce the failure. Support cannot infer a cause from the headline alone. Keep your own backup even when the host advertises backups, and test changes on a copied world whenever the trace points to dimensions, chunks or entity data.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common dead ends
Deleting every configuration file
This can remove useful settings while leaving the real cause untouched. Delete only the JSON files in the documented legacy branch, and only after making copies.
Rank #4
- Skins! We have biome settlers, city folk, town folk, and more!
- The Nether and all its inhabitants. Fight Ghasts and make friends with Pigmen
- Cross platform play for up to five players between Pocket Edition and Windows 10
- Revamped touch controls, controller support, and a controller mapping screen
- Enhanced Weather effects! Accumulating snow and more
Reinstalling Java first
Java can be relevant when the clean-install or dedicated-server checks point to the runtime. It does not logically repair an unregistered dimension type, a biome-decoration upgrade failure or an incompatible mod.
Adding as much RAM as possible
More heap can help an actual memory shortage, but the official limit guidance still applies: up to 4 GB on 32-bit systems and no more than half of system RAM recommended on 64-bit systems. Heap changes do not rewrite malformed files or world data.
Testing several changes simultaneously
Changing Java, the server JAR, every mod and the world folder at once destroys the comparison. Restore the backup, return to the original versions and test one branch at a time.
Assuming the headline identifies the cause
The same wrapper covers unrelated failures. Always preserve and read the first Caused by: chain before selecting a remedy.
When to escalate
- Escalate to a mod author or pack maintainer when a mod, mixin or loader component remains the deepest named cause after a clean-profile test.
- Escalate to the server administrator or hosting support when the old JSON-list branch reproduces after the files are recreated, or when the server cannot launch with a verified JAR and Java installation.
- Escalate a world-specific failure with the copied world, complete crash report,
latest.log, Minecraft version, Java version and exact reproduction steps. Keep the original backup private and unchanged.
There is no universal “server tick loop fix.” The correct repair is the smallest reversible change that addresses the component named by the stack trace.
Frequently Asked Questions
What does “Exception in server tick loop” mean?
It is a crash wrapper indicating that an exception escaped Minecraft’s repeating server simulation loop. The headline is not a diagnosis; read the first Caused by: chain and the deepest named file, mod, dimension or world element.
Best Value
- Play and share with friends on console, mobile and Windows 10
- discover community creations in the new in-game store
- access new mini games and game modes through servers
Should I delete ops.json and whitelist.json?
Only when the trace matches the old net.minecraft.server.v1_7_R3.JsonList.load(JsonList.java:171) pattern. Stop the server, copy ops.json, whitelist.json and usercache.json, then remove the active copies so Minecraft can recreate them.
Free tools Windows power users keep installed
One-click scans. No signup required.
Will reinstalling Java or adding RAM fix the crash?
Only if the log points to a runtime or memory problem. Java and heap changes do not repair malformed JSON, incompatible mods, unregistered dimension types or damaged world data. On 32-bit systems the documented maximum is 4 GB; on 64-bit systems Minecraft Help recommends no more than half of system RAM.
A new world loads, but my old world crashes. What does that show?
It suggests the failure follows existing world data, a dimension, generated content or an upgrade path rather than a basic installation launch. Test a copy of the backed-up world with the identical Minecraft, Java, loader and mod versions; never delete the original as a test.
How do I isolate a mod causing the tick-loop error?
Record the named mod, loader and versions, disable only that component, and test a clean profile on the same Minecraft and Java versions. If the clean profile works, re-enable mods in small groups until the failing component or combination is isolated.
What should I send to a mod author or host?
Send the complete crash report and matching latest.log, Minecraft and Java versions, loader and mod versions, server JAR, and exact reproduction steps. Include the smallest enabled component set that still reproduces the failure, while keeping your original world backup unchanged.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsThe Bottom Line
Back up first, read the deepest Caused by: line, and make one reversible change at a time. Recreate JSON lists only for the documented legacy trace; isolate named mods; test copied worlds for dimension or chunk failures; and adjust Java or -Xmx only when the log supports an environmental diagnosis.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
