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

Elytraslot crashes on neoforge due to mismatched mixinsquared versions #297

Closed
VaporeonScripts opened this issue Sep 24, 2024 · 15 comments
Closed
Labels
Mod Compatibility This is a compatibility issue with another mod

Comments

@VaporeonScripts
Copy link

1.21.1
https://mclo.gs/Z3ZAKNt

@1foxy2
Copy link
Collaborator

1foxy2 commented Sep 24, 2024

elytraslot needs to update mixinssquared

@VaporeonScripts
Copy link
Author

So I have to report it to elytra slot owner?

@1foxy2
Copy link
Collaborator

1foxy2 commented Sep 24, 2024

yes

@VaporeonScripts
Copy link
Author

@FxMorin FxMorin added the Mod Compatibility This is a compatibility issue with another mod label Sep 27, 2024
@FxMorin FxMorin changed the title new neoforge version of the mod causes crash Elytraslot crashes on neoforge due to mismatched mixinsquared versions Sep 27, 2024
@VaporeonScripts
Copy link
Author

same issue happens with chunksending mod bruh

@FxMorin
Copy link
Owner

FxMorin commented Sep 27, 2024

We are working on a fix

@VaporeonScripts
Copy link
Author

alright

@VaporeonScripts
Copy link
Author

the issue with elytra slot is solved, but now additional lantern does the same 💀

@VaporeonScripts
Copy link
Author

elytra trims was the problem, mixinsquared github will provide a fix soon ig, for now the mod works

@Bawnorton
Copy link
Contributor

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.

@1foxy2
Copy link
Collaborator

1foxy2 commented Sep 30, 2024

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

@Bawnorton
Copy link
Contributor

group never changed. Maven changed when migrating from jitpack but the group has always been the same

@1foxy2
Copy link
Collaborator

1foxy2 commented Sep 30, 2024

it was com.github.bawnorton. now its com.bawnorton
image

@Bawnorton

This comment was marked as resolved.

@Bawnorton
Copy link
Contributor

Bawnorton commented Sep 30, 2024

Ah I see, nvm, The jij of the loader-specific module pulls from the maven group. Well I did this to myself 💀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mod Compatibility This is a compatibility issue with another mod
Projects
None yet
Development

No branches or pull requests

4 participants