-
Notifications
You must be signed in to change notification settings - Fork 34
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
Elytraslot crashes on neoforge due to mismatched mixinsquared versions #297
Comments
elytraslot needs to update mixinssquared |
So I have to report it to elytra slot owner? |
yes |
same issue happens with chunksending mod bruh |
We are working on a fix |
alright |
the issue with elytra slot is solved, but now additional lantern does the same 💀 |
elytra trims was the problem, mixinsquared github will provide a fix soon ig, for now the mod works |
I aim to fix this inside mixinsquared itself, when loading jij'd jars I assumed that neo would only load the latest, like fabric, but it doesn't, it tries to load all versions and causes a resolution exception when multiple versions are loaded which is a right pain in the arse. |
neo does load only the latest version. the problem is what Jij identifies jars by group and name given in jarjar parameters. the group of mixinssquared changed so neo thinks its a different mod |
group never changed. Maven changed when migrating from jitpack but the group has always been the same |
This comment was marked as resolved.
This comment was marked as resolved.
Ah I see, nvm, The jij of the loader-specific module pulls from the maven group. Well I did this to myself 💀 |
1.21.1
https://mclo.gs/Z3ZAKNt
The text was updated successfully, but these errors were encountered: