-
Notifications
You must be signed in to change notification settings - Fork 12
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
Comments
While there is an |
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. |
(I hit shift while I was trying to make a new line, bruh.) For now, I'll just try to set the Edit: I figured out how. # in gradle.properties
loom.ignoreDependencyLoomVersionValidation=true |
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:
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.
The text was updated successfully, but these errors were encountered: