2 critical 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.1
What this error means, and every way to fix it →
The server ran out of memory
The server used more RAM than it was allowed. Give it more RAM (raise the RAM setting), or lower the view-distance in server.properties.
Usual suspects: the pack as a whole rather than one mod; memory-leak-prone mods (the AllTheLeaks report in the log, if present, names them).
which explains: The server stalled for too long and was stopped
The stall is a symptom of the finding above, not a separate problem.
which explains: The server crashed and then hung
The hang is the aftermath; the crash above is the story.
which explains: The tick loop fell 4732ms behind, 94 ticks in one go
The tick loop falls behind because of the finding above, not on its own.
Two mods clash inside this pack
A mod patched the game expecting a library or another mod that is missing or the wrong version, so the game crashed when that code ran. The stack trace names the mod (look for handler$...$modname). Remove or exclude that mod server-side, or ask the pack author to ship its missing dependency. The trace points at bettermobcombat.
Usual suspects: the mod named in the mixin or handler frame of the crash.
Why this happens: Mixin apply failed →jump to line 82 sensitive values (addresses, passwords and the like) were stripped before this page was stored.
As received, after redaction.
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.