`mod unknown-owner` for several mods

[Krutoy242]

Your CleanroomMC Discord Username

Krutoy242

Cleanroom Version

0.3.0-alpha

Java Version

Java 24

Graphics Card Vendor

NVidia

Bug Report

When Java 8 output correct names for errors in logs, Cleanroom version just write mod unknown-owner for mod names.

For example, correct error on Java 8:

[main/ERROR] [mixin]: Critical problem: mixins.stellar_core_forge_asmmodparser.json:MixinASMModParser from owner stellar_core target net.minecraftforge.fml.common.discovery.asm.ASMModParser was loaded too early.

And this how it looks like on Cleanroom:

[main/ERROR] [mixin]: Critical problem: mixins.stellar_core_forge_asmmodparser.json:MixinASMModParser from mod unknown-owner target net.minecraftforge.fml.common.discovery.asm.ASMModParser was loaded too early.

Same behavior is true for some other mods, such as vintagefix or rlmixins.

Example log with lot of mod unknown-owner occurrences debug-5.log

Mod List

https://www.curseforge.com/minecraft/modpacks/enigmatica-2-expert-extended

Final Checklist

• [x] I have searched the issues and haven't found a similar issue.
• [x] I have read the readme and know that what is action build.
• [x] I have installed Fugue and it didn't fix my issue.
• [x] I have installed Scalar and it didn't fix my issue.
• [x] I have switched my Forgelin and LibrarianLib to continuous versions(check readme for more detail).
• [ ] I am running a test build from Cleanroom Github Actions. (Or, if I've compiled it myself I plan to fix the issue)

[kappa-maintainer]

My Mixin fork didn't implement complete owner tracking code, so that's expected Will fix after our two Mixin forks merged