Skip to content
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

[Likely Unfixable] Issues with Architectury Loom #45

Open
RedstoneWizard08 opened this issue Nov 27, 2024 · 3 comments
Open

[Likely Unfixable] Issues with Architectury Loom #45

RedstoneWizard08 opened this issue Nov 27, 2024 · 3 comments

Comments

@RedstoneWizard08
Copy link
Contributor

Is your feature request related to a problem? Please describe.

When trying to use Veil in a Fabric/NeoForge multiplatform project (1.21.1) with Architectury Loom, it fails to build because Veil uses Fabric Loom 1.8-SNAPSHOT for the 1.21.1 builds, whereas Architectury Loom v1.8-SNAPSHOT doesn't exist, and it fails with:

> Failed to setup Minecraft, java.lang.IllegalStateException: Mod was built with a newer version of Loom (1.8.9), you are using Loom (1.7.414)

Describe the solution you'd like

It would be great if Veil could roll back Loom to 1.7-SNAPSHOT.

Describe alternatives you've considered

N/A (Well I could build it myself but that would be less convenient and I'm sure I'm not going to be the only one with this issue.)

Additional context

Using Veil 1.0.0.28 for Minecraft 1.21.1 and Architectury Loom 1.7-SNAPSHOT.

@RedstoneWizard08
Copy link
Contributor Author

RedstoneWizard08 commented Nov 27, 2024

While there is an exp/1.8 branch on the Architectury Loom GitHub, it is currently not on their maven (and it doesn't even look like it works, CI is failing), and therefore basically unusable.

@RedstoneWizard08
Copy link
Contributor Author

I understand that Sodium (I haven't looked at Iris) is using Loom 1.8 which makes this difficult, and I would love to see a permanent solution in the future, which will likely be whenever Architectury Loom 1.8 comes out.

@RedstoneWizard08
Copy link
Contributor Author

RedstoneWizard08 commented Nov 27, 2024

(I hit shift while I was trying to make a new line, bruh.)

For now, I'll just try to set the ignoreDependencyLoomVersionValidation property to true (if I can figure out how).

Edit: I figured out how.
For anyone who encounters the same issue:

# in gradle.properties
loom.ignoreDependencyLoomVersionValidation=true

@RedstoneWizard08 RedstoneWizard08 changed the title Issues with Architectury Loom [Likely Unfixable] Issues with Architectury Loom Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant