Crash on launch of Nomifactory CEu

[lynxx131]

Your CleanroomMC Discord Username

No response

Cleanroom Version

universal-0.2.3-alpha+build.5.run.696

Java Version

Java 21

Graphics Card Vendor

Other (Please Specify)

Bug Report

If I work around the config file issue in #200 then the next hurdle I hit is the client crashes on launch with following crash report.

This is a vanilla Nomifactory 1.7a installation with no changes other than working around the config file issue I reported in #200 where I just copied the contents of nomilabs.cfg into the file called nomilabs which is created in the config directory after first launch.

This issue does not occur under vanilla Forge.

crash-2024-09-05_10.34.18-client.txt

Mod List

All mods included in Nomifactory 1.7a Curseforge pack + Fugue 0.16.3 and Scalar 2.11.

MMC Instance Notes

This instance is built using Github Action.

Using installer artifact from commit: b132d86
Action URL: https://github.com/CleanroomMC/Cleanroom/actions/runs/10658856743

Final Checklist

• I have searched the issues and haven't found a similar issue.
• I have read the known incompatibilities and this is not related to one of those.
• I have installed Fugue and it does not fix this issue.
• I am using experimental branch and have installed Scalar and it does not fix this issue.
• I am running a test build from Cleanroom Github Actions. (Or, if I've compiled it myself I plan to fix the issue)

[Rongmario]

May we have your full log please? It seems like packmode wasn't loaded/or loaded incorrectly.

[lynxx131]

Here is my latest and debug log files.

debug.log
latest.log

[kappa-maintainer]

Reported to nomi-ceu developers

[erialsan]

Similar problem, probably due to Packmode
I'll report back to the author, but I'll add Packmode to Fugue's config and see if it can be addressed.

[erialsan]

Apparently this is an inherent problem with recent Cleanroom builds!

[kappa-maintainer]

That's because nomilabs is relying on old classloader architecture lazily in recent updates, nobody to blame here