5 warnings, 1 observation found. Every finding below comes from what was actually in the pasted files. Treat the fixes as suggestions: they cover the common causes, and this case may need more digging.
ForgeMinecraft 1.20.1Java 17
This looks like a client log, not a server log. The findings below apply to the player's machine.
What this error means, and every way to fix it →
This log contains 499 lines logged at ERROR level and none matched a known failure signature. That is not a clean bill: the most repeated one is summarised in the findings above, and every one of them is in the log below.
A world-generation feature is writing outside its chunk: tfmg:oil_deposit
Minecraft logs this every time a placed feature sets blocks in a chunk it does not own: 83 lines here, mostly from tfmg:oil_deposit. The mod or datapack that defines that feature has a bug in its size or placement. Each line is a lock contention and a slow chunk, and enough of them look like lag while new terrain generates. Update the mod or datapack that provides tfmg, or if it is your own datapack shrink the feature so it stays within its chunk. It is not world corruption and the server is safe to keep running; it just generates slowly.
Usual suspects: tfmg.
jump to line 3338AllTheLeaks is reporting objects the server cannot free
The AllTheLeaks mod is printing its leak report: no types listed yet. Invalid cloned players: 0. Memory in use grew by 175MB between its checks. Objects the game has finished with are still referenced by something, so garbage collection cannot reclaim them and the heap fills until the server stalls or dies with an out-of-memory error. The bracketed name after each leaking type is the mod holding the reference; update or remove those first, minecraft itself rarely leaks. Cloned players point at a respawn or dimension-travel bug in a mod. Until it is fixed, restart on a schedule before the heap fills, and run /atl force_refresh after players log out to see which mod keeps growing.
jump to line 81701 config or data file is empty or corrupt
Gson could not parse a file the game or a mod tried to load (tags/items/foods222.json is named just above the first error). "End of input at line 1 column 1" is an empty file, which is what a crash or kill mid-write leaves behind; "Expected BEGIN_OBJECT but was STRING" is text where JSON was expected. Whatever depended on that file is running on defaults or not at all. Find the file (the lines just above each error usually name it), back it up, then delete it so the mod regenerates it, or restore it from a backup. If the same file keeps breaking, the disk filled up or the server is being killed while it saves.
jump to line 3840The tick loop fell 2403ms behind, 48 ticks in one go
A tick took far longer than the 50ms it is allowed, so the server ran behind real time and skipped ahead to catch up (once in this log). Players see rubber-banding, delayed block breaks and mobs that stutter. One burst after a restart, a world upgrade or a chunk pre-generation run is normal. A steady stream is lag with a cause: profile it with spark (/spark profiler start --timeout 120 in the console) rather than guessing. The usual culprits are view-distance and simulation-distance set too high, entity or item build-ups, chunks generating live as players explore, and garbage collection pauses when the heap is too small.
Why this happens: Diagnosing server lag →jump to line 7508563 error lines and none matched a known signature. The most repeated (JsonParseException): "JsonParseException: JSON data was null or empty" 8 times
Roastd has no signature for this one yet, so here is the raw material. Also in there: "JsonSyntaxException: Unknown type 'minecraft:alternative'" (4 times), "JsonSyntaxException: Expected name to be an item, was unknown string 'butchery_alexs_mobs:rawcaimansteak'" (3 times). Search the exact message with the mod or plugin name; if the server crashed, paste the newest file from crash-reports/ as well, and bring the share link to our Discord so a signature gets written.
jump to line 1829Refmap warnings are cluttering the log
A "reference map could not be read" warning on its own is usually harmless build noise from a mod, not the cause of a crash. Ignore these lines unless a real mixin failure appears further down. They only matter when paired with an injection error.
jump to line 427399 sensitive values (addresses, passwords and the like) were stripped before this page was stored.
Showing 2240 of 8180 lines, after redaction: the start, the end, and the lines the findings point at.
Need more help or want to discuss your issue further? Join our Discord and bring the link to this page.
Join our DiscordRun a community? Add the Roastd bot and anyone can roast a crash log in your support channel.
Add the Roastd botGot a server of your own that deserves a second opinion?
Roast your own serverRoastd is a free tool built by Hostd. This diagnosis stays put. The log it was read from is deleted on a timer.