-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Built Fabric jar using incorrect refmap #43
Comments
Do you have Architectury Plugin installed? It should fix this issue, which really isn't a Loom issue (the mixin config is in the common Gradle project, so its |
What would I have to set in my remapJar task? |
You can't fix it by tweaking The easiest solutions are using Architectury Plugin (in compile-only mode if needed) or specifying the refmap name manually in the mixin config. |
Cool, I've fixed this by doing: loom {
mixin {
defaultRefmapName.set("Bountiful-common-refmap.json")
}
} Do you have an example of how this is done using Architectury Plugin? I'm depending on it in my gradle setup, but I don't exactly know how to utilize it. Thanks so much! |
If you include the common classes in the Fabric jar by bundling |
It's my understanding that I'm already doing this. Could the problem arise because I'm not including transitive dependencies? |
No, I don't think it affects anything since that project dependency won't even have any transitive deps. As far as I can tell, the code should already work 🤔 I also don't think this is directly related to Loom, so I'm moving the issue to Arch Plugin's repo. |
When I try to build my JAR file for Fabric, I get this error:
StructurePoolAccessor is a Mixin in Kambrik, my mod.
I noticed that the .jar file contains a
Kambrik-common-refmap.json
. It's unused inkambrik.mixins.json
. If I add the following line tokambrik.mixins.json
:The mod will launch successfully. As such, it seems that refmaps aren't being linked properly. I don't know much about how refmaps work, or how they're supposed to work, but this is what seems to be happening. It happens with ArchLoom 1.4-SNAPSHOT and 1.5-SNAPSHOT.
The text was updated successfully, but these errors were encountered: