-
-
Notifications
You must be signed in to change notification settings - Fork 193
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
NeoForge mod not compiles #822
Comments
@Byllfighter This is likely some other plugin interfering with the Gradle Tasks that re-compiles the Minecraft sources. Anyway: Please click the "Run with --stacktrace option [..]" link and post the result. |
|
This issue not occurs on Forge or Fabric |
Can you try running |
This is an Mcreator project |
Yes, it's MCreator project, but I also have this issue in Visual Studio in non-MCreator projects |
@Byllfighter Have you tried intellij for the project? Is your project on github or something for others to clone and try to reproduce your issue? Visual studio isn't supported for mod development. Visual Studio Code is slightly better. But intellij and eclipse are the main IDEs supported for mod development |
I can confirm this bug (in a Windows terminal, simply by using ./gradlew build) |
IntelliJ works, but Visual Studio and MCreator still have this issue |
Visual Studio is not a supported environment. Even if it were, it appears to not support modern gradle versions: redhat-developer/vscode-java#3648 |
It does, and the particular issue was somehow fixed by me restarting my pc. Very confused. I can't reproduce this error in neo 1.20.4 or 1.20.6, mind you. It all just works as expected. |
I can reproduce the bug, and it affects Minecraft 1.20.4 and Minecraft 1.20.6 |
Linking the new gradle issue report that will help fix this case for people unable to build neoforge mods |
Closing this as it is a Gradle bug |
Minecraft Version: 1.20.4 (other versions not tested)
NeoForge Version: 20.4.223
Logs:
Steps to Reproduce:
Description of issue:
Mod build fails on neoFormRecompile. This issue not occurs on Java 8.
The text was updated successfully, but these errors were encountered: