Gradle Error

Not applicable
Issue description

I went to use mcreator and started it up. I was in the middle of starting when my computer crashed for no reason. When I went into mcreator again, it said gradle had an error and it pushed out this really long error code
Executing gradle command: cleanCache clean setupDecompWorkspace --refresh-dependencies
Microsoft Windows [Version 10.0.17134.165]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Pylo\MCreator179>cd forge
C:\Pylo\MCreator179\forge>SET "JAVA_HOME=C:\Pylo\MCreator179\jdk\"
C:\Pylo\MCreator179\forge>SET JAVA_EXE=%JAVA_HOME%\bin\java.exe
C:\Pylo\MCreator179\forge>SET PATH=%JAVA_HOME%\bin\;%PATH%
C:\Pylo\MCreator179\forge>SET "GRADLE_USER_HOME=C:\Users\Jake Li\.mcreator\gradle"
C:\Pylo\MCreator179\forge>gradlew -Dorg.gradle.daemon=false -Dorg.gradle.parallel=false -Dorg.gradle.jvmargs="-Xms1000m -Xmx1500m" cleanCache clean setupDecompWorkspace --refresh-dependencies 
This mapping 'snapshot_20171003' was designed for MC 1.12! Use at your own peril.
C:\Users\Jake Li\.mcreator\gradle\caches\minecraft\net\minecraftforge\forge\1.12.2-\userdev\dev.json could not be parsed
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring root project 'forge'.
> Inherited json file (1.12.2) not found! Maybe you are running in offline mode?
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
Total time: 18.823 secs
Task completed with return code 0 in 19629 milliseconds

Does anyone know what to do?


Issue comments

This bug happens when the user has selected to run the Gradle in offline mode. After a while, some caches get outdated and need to be updated. As the user is in offline mode, this is not possible.

The workaround is to disable the offline mode when you see this error, so the caches can be updated, or to disable the offline mode altogether if there is no good reason to use it.

If you don't run in offline mode, check the internet connection or try the other fix provided in the linked issue.