Server Crashing with just create as the issue. 1.20.1 create v. 6.0.2

[nshade404]

Context

I usually try to solve these types of issues myself but I have been crafting a decently large modpack with the intention of playing with friends. However we have come across a crash that seems to keep showing up despite the removal of all mods that would interact with create. here is my servers most recent crash log in hopes we can figure this out with more eyes.

PS: i am fairly new to development like this. So i am still bad at reading these logs. I am hoping this is not just a missed line of errors on my part

Crash Report

https://mclo.gs/nqKOTwC

Latest Log

https://mclo.gs/ACuscOE

Mixin.out.zip

.mixin.out.zip

[nshade404]

that was the wrong log one second

update: the link has been set to the right log

[ChiefArug]

That crash report seems to be missing part of the error, can you send the latest.log file as well?

[nshade404]

That crash report seems to be missing part of the error, can you send the latest.log file as well?

I sure can here is the log labeled latest. sorry if there is a lot of congestion. we run mod optimizer since not every mod can run on a server for the pack.

latest.log

https://mclo.gs/ACuscOE

Update: I set the latest log at the top as well for easier access

[ChiefArug]

Well mods optimiser is doing a terrible job at what it says it does, there are tons of errors in there related to client only code trying to load, including at least one client only mod (let sleeping dogs lie).

It seems that the root cause of create failing to load is also something trying to load a client only class, specifically a mixin into create, so one of your create addons is broken. Remove them in small groups till it works to find which one it is.

[nshade404]

Is that not the log with them all disengaged? unless I have missed one that was my first instinct. which is why I posted here. It was still occurring with no create addons. At least none immediately apparent. tried again without let sleeping dogs lie and still got this error. Would there be a place create mixins could create a permanent change to the mod. I did have a similar issue with epic fight and soaring sword that seemed to permanently cause epic fight to crash despite removing the mod and the addon called weapons of miracle which bugged out. I had to completely uninstall said mods and reinstall epic fight without letting soaring sword touch the pack again.

Update: also the creator of mod optimizer said his mod would not catch all "client" mods as it had to be updated with that information

[ChiefArug]

Yes, that log doesn't have any create addons, though some mods have compat with create without being explicit addons. It could also be create tripping on a 'landmine' another mod dropped (a bug in that mod).
Can you add the argument -Dmixin.dumpTargetOnFailure=true to your args, get it to crash, then send a zip of the .mixin.out folder?

[nshade404]

Yes, that log doesn't have any create addons, though some mods have compat with create without being explicit addons. It could also be create tripping on a 'landmine' another mod dropped (a bug in that mod). Can you add the argument -Dmixin.dumpTargetOnFailure=true to your args, get it to crash, then send a zip of the .mixin.out folder?

I have added the mixin.zip to the starting post so you can access it quickly

[ChiefArug]

That is so strange. That zip says the problematic mixin is targetting net.minecraft.world.level.block.TntBlock, however according to WAIFU there are only 7 mixins to there, and after looking at their code none of them have something that would trigger the crash seen here...
The only mod you have installed from that list is Quad, try removing that just in case that is the cause. (it shouldn't be though, as the dump contains all their mixins already injected, and the error is a mixin failing to inject...)

You don't happen to have any mods installed that aren't on CF or MR, or are pretty recent (since yesterday, WAIFU is pretty up to date)?