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

Using Loom 1.5 on multiloader crashes #3556

Closed
CrypticVerse opened this issue Jan 28, 2024 · 2 comments
Closed

Using Loom 1.5 on multiloader crashes #3556

CrypticVerse opened this issue Jan 28, 2024 · 2 comments

Comments

@CrypticVerse
Copy link

Developing mod using:
Fabric API: 0.95.0+1.20.4
Fabric Loader: 0.15.3
Forge: 49.0.19
NeoForge: 20.4.83-beta

Log:

Configure project :common
Targeting Minecraft '1.20.4' on a 'JOINED' platform

Configure project :fabric
Fabric Loom: 1.5.7
Found existing cache lock file, rebuilding loom cache. This may have been caused by a failed or canceled build.

FAILURE: Build failed with an exception.

  • What went wrong:
    A problem occurred configuring project ':fabric'.

Failed to notify project evaluation listener.
Failed to setup Minecraft, java.lang.RuntimeException: Unexpected IllegalAccessException occurred (Gson 2.9.1). Certain ReflectionAccessFilter features require Java >= 9 to work correctly. If you are not using ReflectionAccessFilter, report this to the Gson maintainers.
Unexpected IllegalAccessException occurred (Gson 2.9.1). Certain ReflectionAccessFilter features require Java >= 9 to work correctly. If you are not using ReflectionAccessFilter, report this to the Gson maintainers.

  • Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.

CONFIGURE FAILED in 281ms

@CrypticVerse
Copy link
Author

This happens when trying to launch the fabric client

@modmuss50
Copy link
Member

This is a duplicate of: FabricMC/fabric-loom#1020 and is a Gradle bug.

Make sure to update the foojay resolver plugin if you are using it, if not ensure that your plugin versons are specified in the root project.

@modmuss50 modmuss50 closed this as not planned Won't fix, can't repro, duplicate, stale Jan 28, 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

2 participants