Open Starcloudsea opened 9 months ago
Hi, this issue was brought up by my friend manipulating my computer, and the information provided may be less due to perhaps a laggy network or some other reason.
The project that went wrong has been hosted on GitHub (in this repository), and my friend's Forge client works fine after a normal build, but I got an exception on startup after the build, and the exception message is the file above.
I think this problem is bound to happen, but not on every computer.
However, after my friend solved the problem by replacing architectury-forge-9.1.12.jar
and architectury-forge-9.1.12-sources.jar
in the .gradle/loom-cache/remapped_mods/loom_mappings_1_20_1_layered_hash_40359_v2_forge_1_20_1_47_2_20_forge/dev/architectury/architectury-forge/9.1.12
folder (the replacement files all came from my friend's computer), the Forge client now launches normally with no exception thrown.
Oh yeah, the IDEs we use are both IntelliJ IDEA and I haven't made any changes to the Gradle settings since installation.
As well, I created another project with Architectury today, this time I created a 1.20.2 project with Forge, Fabric Loader, Fabric API and Architectury API all up-to-date (I'll give their exact versions at the end), and then, this time, a new exception was thrown:
This file contains the entire log for more than just exceptions.
After throwing this exception, the game is stuck.
Note that I didn't write a single line of code for the main of either the first project I got the error on or the new one (except for the file conversion).
The Fabric client starts fine, even if the Forge client doesn't.
Since my English is very inferior to my friend's, all texts except the first one that my friend sends on his behalf are translated by DeepL.
2 months later this issue still hasn't been answered, I just wanted to ask what's going on? Is this not a bug?
Try to refresh the gradle cache with gradlew --refresh-dependencies
?
crash-2024-02-12_11.41.41-fml.txt client crashes and looks like architectury framework can't be remapped correctly and this bug cannot appeared in every PC