mcreator constaltly throwing gradle error and no help i can find fixes it

Started by Vortex64 on Sat, 04/24/2021 - 08:16

Topic category: Help with MCreator software

Last seen on 08:02, 6. Jun 2021
Joined Apr 2021
Points:

User statistics:

  • Modifications:
  • Forum topics:
  • Wiki pages:
  • Tracker tickets:
  • MCreator plugins:
  • Comments:
mcreator constaltly throwing gradle error and no help i can find fixes it
Sat, 04/24/2021 - 08:16

Hello!

I keep attempting to make a forge mod using mcreator but whenever I open or attempt to make a mod mcreator keeps throwing this error

Executing
    Gradle task: eclipse

Build
    info: MCreator 2020.5.47520, forge-1.15.2, 64-bit, 32615 MB, Windows 10,
    JVM 1.8.0_265, JAVA_HOME: C:\Program Files\Pylo\MCreator\jdk

org.gradle.tooling.GradleConnectionException:
    Could not execute build using connection to Gradle distribution
    'https://services.gradle.org/distributions/gradle-4.10.3-bin.zip'.

 
      at org.gradle.tooling.internal.consumer.ExceptionTransformer.transform(
ExceptionTransformer.java:55
)

 
      at org.gradle.tooling.internal.consumer.ExceptionTransformer.transform(
ExceptionTransformer.java:29
)

 
      at org.gradle.tooling.internal.consumer.ResultHandlerAdapter.onFailure(
ResultHandlerAdapter.java:43
)

 
      at
    org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor$1$1.run(
DefaultAsyncConsumerActionExecutor.java:69
)

 
      at
    org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(
ExecutorPolicy.java:64
)

 
      at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(
ManagedExecutorImpl.java:48
)

 
      at java.util.concurrent.ThreadPoolExecutor.runWorker(
ThreadPoolExecutor.java:1149
)

 
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:624
)

 
      at
    org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(
ThreadFactoryImpl.java:56
)

 
      at java.lang.Thread.run(
Thread.java:748
)

Caused
    by: org.gradle.api.GradleException: Unable to start the daemon process.

This
    problem might be caused by incorrect configuration of the daemon.

For
    example, an unrecognized jvm option is used.

Please
    refer to the user guide chapter on the daemon at
    https://docs.gradle.org/4.10.3/userguide/gradle_daemon.html

Please
    read the following process output to find out more:

-----------------------

 
      at org.gradle.launcher.daemon.client.DaemonGreeter.parseDaemonOutput(
DaemonGreeter.java:35
)

 
      at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startProcess(
DefaultDaemonStarter.java:160
)

 
      at org.gradle.launcher.daemon.client.DefaultDaemonStarter.startDaemon(
DefaultDaemonStarter.java:136
)

 
      at
    org.gradle.launcher.daemon.client.DefaultDaemonConnector.doStartDaemon(
DefaultDaemonConnector.java:212
)

 
      at org.gradle.launcher.daemon.client.DefaultDaemonConnector.startDaemon(
DefaultDaemonConnector.java:206
)

 
      at org.gradle.launcher.daemon.client.DefaultDaemonConnector.connect(
DefaultDaemonConnector.java:130
)

 
      at org.gradle.launcher.daemon.client.DaemonClient.execute(
DaemonClient.java:139
)

 
      at org.gradle.launcher.daemon.client.DaemonClient.execute(
DaemonClient.java:93
)

 
      at
    org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(
DaemonBuildActionExecuter.java:60
)

 
      at
    org.gradle.tooling.internal.provider.DaemonBuildActionExecuter.execute(
DaemonBuildActionExecuter.java:41
)

 
      at
    org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(
LoggingBridgingBuildActionExecuter.java:58
)

 
      at
    org.gradle.tooling.internal.provider.LoggingBridgingBuildActionExecuter.execute(
LoggingBridgingBuildActionExecuter.java:37
)

 
      at org.gradle.tooling.internal.provider.ProviderConnection.run(
ProviderConnection.java:180
)

 
      at org.gradle.tooling.internal.provider.ProviderConnection.run(
ProviderConnection.java:124
)

 
      at org.gradle.tooling.internal.provider.DefaultConnection.getModel(
DefaultConnection.java:208
)

 
      at
    org.gradle.tooling.internal.consumer.connection.CancellableModelBuilderBackedModelProducer.produceModel(
CancellableModelBuilderBackedModelProducer.java:54
)

 
      at
    org.gradle.tooling.internal.consumer.connection.PluginClasspathInjectionSupportedCheckModelProducer.produceModel(
PluginClasspathInjectionSupportedCheckModelProducer.java:38
)

 
      at
    org.gradle.tooling.internal.consumer.connection.AbstractConsumerConnection.run(
AbstractConsumerConnection.java:64
)

 
      at
    org.gradle.tooling.internal.consumer.connection.ParameterValidatingConsumerConnection.run(
ParameterValidatingConsumerConnection.java:49
)

 
      at org.gradle.tooling.internal.consumer.DefaultBuildLauncher$1.run(
DefaultBuildLauncher.java:97
)

 
      at org.gradle.tooling.internal.consumer.DefaultBuildLauncher$1.run(
DefaultBuildLauncher.java:89
)

 
      at
    org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.run(
LazyConsumerActionExecutor.java:130
)

 
      at
    org.gradle.tooling.internal.consumer.connection.CancellableConsumerActionExecutor.run(
CancellableConsumerActionExecutor.java:45
)

 
      at
    org.gradle.tooling.internal.consumer.connection.ProgressLoggingConsumerActionExecutor.run(
ProgressLoggingConsumerActionExecutor.java:61
)

 
      at
    org.gradle.tooling.internal.consumer.connection.RethrowingErrorsConsumerActionExecutor.run(
RethrowingErrorsConsumerActionExecutor.java:38
)

 
      at
    org.gradle.tooling.internal.consumer.async.DefaultAsyncConsumerActionExecutor$1$1.run(
DefaultAsyncConsumerActionExecutor.java:67
)

 
      ... 6 more

TASK
    EXECUTION FAILED

Task
    completed in 1215 milliseconds

I was wondering if anyone here knew how to fix it

The solution to this problem…
Sat, 04/24/2021 - 08:33

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.