MCreator 1.9.1: Crash Bug [Here no solution]

Started by TheLuxureSlime on Sat, 10/12/2019 - 20:49

Topic category: Bugs and solutions

Last seen on 08:35, 22. Nov 2019
Joined Sep 2018
User points:

Statistics:

  • Comments:
  • Forum topics:
  • Modifications:
  • Wiki pages:
MCreator 1.9.1: Crash Bug [Here no solution]
Sat, 10/12/2019 - 20:49

Some letters deleted... because... it russian letters :/

Regenerate code and build:
Executing gradle command: build
Build info: MCreator 1.9.1, 64-bit, 10176 MB, Windows 7 - cmd, JVM 1.8.0_222, JAVA_HOME: C:/Program Files/Pylo/MCreator/jdk/jre
(c) ®® ©Є®® (Microsoft Corp.), 2009. ‚.
I:\MCreator + Exploracraft\Exploracraft>gradlew -Dorg.gradle.java.home="C:/Program Files/Pylo/MCreator/jdk/jre" -Dorg.gradle.parallel=true -Dorg.gradle.jvmargs="-Xms625m -Xmx1048m" build --offline 
Parallel execution is an incubating feature.
FAILURE: Build failed with an exception.
* Where:
Build file 'I:\MCreator + Exploracraft\Exploracraft\build.gradle' line: 10
* What went wrong:
A problem occurred evaluating root project 'Exploracraft'.
> Failed to apply plugin [id 'net.minecraftforge.gradle.forge']
   > java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1
* 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
BUILD FAILED in 1s
I:\MCreator + Exploracraft\Exploracraft>
Task completed with return code 0 in 1453 milliseconds

This action will regenerate base mod source files and build the gradle project:
Executing gradle command: build
Build info: MCreator 1.9.1, 64-bit, 10176 MB, Windows 7 - cmd, JVM 1.8.0_222, JAVA_HOME: C:/Program Files/Pylo/MCreator/jdk/jre
(c)  (Microsoft Corp.), 2009. ‚.
I:\MCreator + Exploracraft\Exploracraft>gradlew -Dorg.gradle.java.home="C:/Program Files/Pylo/MCreator/jdk/jre" -Dorg.gradle.parallel=true -Dorg.gradle.jvmargs="-Xms625m -Xmx1048m" build --offline 
Parallel execution is an incubating feature.
FAILURE: Build failed with an exception.
* Where:
Build file 'I:\MCreator + Exploracraft\Exploracraft\build.gradle' line: 10
* What went wrong:
A problem occurred evaluating root project 'Exploracraft'.
> Failed to apply plugin [id 'net.minecraftforge.gradle.forge']
   > java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1
* 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
BUILD FAILED in 1s
I:\MCreator + Exploracraft\Exploracraft>
Task completed with return code 0 in 1445 milliseconds

Run Client:
Executing gradle command: runClient
Build info: MCreator 1.9.1, 64-bit, 10176 MB, Windows 7 - cmd, JVM 1.8.0_222, JAVA_HOME: C:/Program Files/Pylo/MCreator/jdk/jre
(c)  (Microsoft Corp.), 2009. ‚
I:\MCreator + Exploracraft\Exploracraft>gradlew -Dorg.gradle.java.home="C:/Program Files/Pylo/MCreator/jdk/jre" -Dorg.gradle.parallel=true -Dorg.gradle.jvmargs="-Xms625m -Xmx1048m" runClient --offline 
Parallel execution is an incubating feature.
FAILURE: Build failed with an exception.
* Where:
Build file 'I:\MCreator + Exploracraft\Exploracraft\build.gradle' line: 10
* What went wrong:
A problem occurred evaluating root project 'Exploracraft'.
> Failed to apply plugin [id 'net.minecraftforge.gradle.forge']
   > java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1
* 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
BUILD FAILED in 0s
I:\MCreator + Exploracraft\Exploracraft>
Task completed with return code 0 in 1221 milliseconds

https://mcreator.net/wiki…
Sun, 10/13/2019 - 10:32

https://mcreator.net/wiki/gradle-setup-errors#wiki-index-11

The solution to this problem and many other problems can be found in our knowledge base: https://mcreator.net/support/knowledgebase Please check the knowledge base before opening a new topic on the issue which has a known fix.