The JarJar Artifact ID between Vanillin and other mods is different ("neoforge" vs "flywheel-neoforge-1.21.1")

[leon-o]

Hello! First of all, thank you for the incredible work on Flywheel and Vanillin.

I’ve encountered a JarJar version negotiation issue when my mod is installed alongside Vanillin. It appears that Vanillin’s metadata.json identifies the Flywheel artifact as neoforge, not flywheel-neoforge-1.21.1.

The Conflict

Because the Artifact IDs do not match, NeoForge treats them as two distinct libraries rather than two versions of the same library. This causes:

1. JarJar to skip version negotiation.
2. Both 1.0.4 (from Vanillin) and 1.0.6 (from my mod) to be present in the classpath.
3. A loading crash because my mod explicitly requires [1.0.6,) via mods.toml, but the loader defaults to the instance registered by Vanillin.

Current "Hack" Solution

To keep my mod functional for users, I have implemented a rather "dirty" workaround:

• I’ve manually renamed the Flywheel 1.0.6 JAR to neoforge-1.0.6.jar in my local libs folder.
• I'm forcing my jarJar configuration to use the neoforge artifact ID to match Vanillin’s metadata.

While this works, it is a very fragile "hack" and could lead to further confusion as more mods update to Flywheel 1.0.6+.

Suggestion

Would it be possible to align the Artifact ID in Vanillin's build script with the public Maven coordinate (flywheel-neoforge-1.21.1) in a future update? This would allow NeoForge to correctly negotiate the highest version when multiple mods bundle Flywheel.

[IThundxr]

This is probably because JiJ doesn't correctly handle local projects being JiJ'd, we'll have to look into if it's possible to change that ourselves or if this would be a neoforge issue

[IThundxr]

#322 should fix this