Describe the bug

When launching a dev build of AQM2 with updated mods including ae2, I get stuck in a infinite load and looking at latest log there was a crash that occurred but did not exit the game.

Crash: https://gist.github.com/itsdinkd/9fd6936177219eec60c5c04a411f7e48
Log: https://gist.github.com/itsdinkd/ae3da4185ce4833d58393553f78ebad3

How to reproduce the bug

Not quite sure but I've updated AE2, and several other mods including fabric API and modloader from 11.9 to 11.10

Expected behavior

to load

Additional details

No response

Which minecraft version are you using?

1.18

On which mod loaders does it happen?

Fabric

Crash log

https://gist.github.com/itsdinkd/9fd6936177219eec60c5c04a411f7e48

downgraded to appliedenergistics2-fabric-11.6.6.jar and crash is gone. has to be either 11.7 or 11.6.7

I tested this with AE2 appliedenergistics2-fabric-11.7.0.jar, fabric-api-0.67.0+1.18.2.jar and the latest loader version and could not reproduce the crash. I don't see how core fabric-api classes not being found during init could really be related to AE2 itself.

try without using not enough crashes ... And please post the actual crashlog, looks like you extracted the crash from the game log

I highly doubt this is AE2 related. In case there's more information to the contrary please let me know in this issue.
I suspect it is the randomized mod loading order that has the placebo effect of downgrading "fixing" this.