Mcreator ошибка workspace setup failed

First time i installed mcreator and when creating my workspace this error occurred:

Executing 
    Gradle task: eclipse

Build 
    info: MCreator 2021.1.18117, forge-1.16.5, 64-bit, 8124 MB, Windows 10, 
    JVM 1.8.0_275, JAVA_HOME: C:Program FilesPyloMCreatorjdk

org.gradle.tooling.GradleConnectionException: 
    Could not execute build using connection to Gradle distribution 
    ‘https://services.gradle.org/distributions/gradle-6.8.1-all.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.launcher.daemon.client.DaemonConnectionException: Could not 
    receive a message from the daemon.

 
      at org.gradle.launcher.daemon.client.DaemonClientConnection.receive(
DaemonClientConnection.java:83
)

 
      at org.gradle.launcher.daemon.client.DaemonClient.executeBuild(
DaemonClient.java:167
)

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

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

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

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

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

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

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

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

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

 
      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:144
)

 
      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

Caused 
    by: org.gradle.internal.remote.internal.MessageIOException: Could not read 
    message from ‘/127.0.0.1:56471’.

 
      at org.gradle.internal.remote.internal.inet.SocketConnection.receive(
SocketConnection.java:94
)

 
      at org.gradle.launcher.daemon.client.DaemonClientConnection.receive(
DaemonClientConnection.java:77
)

 
      … 27 more

Caused 
    by: com.esotericsoftware.kryo.KryoException: java.io.IOException: Kurulan 
    bir bağlantı, ana makinenizdeki yazılım tarafından iptal edildi

 
      at com.esotericsoftware.kryo.io.Input.fill(
Input.java:148
)

 
      at com.esotericsoftware.kryo.io.Input.require(
Input.java:178
)

 
      at com.esotericsoftware.kryo.io.Input.readVarInt(
Input.java:355
)

 
      at com.esotericsoftware.kryo.io.Input.readInt(
Input.java:350
)

 
      at org.gradle.internal.serialize.kryo.KryoBackedDecoder.readSmallInt(
KryoBackedDecoder.java:127
)

 
      at 
    org.gradle.internal.serialize.DefaultSerializerRegistry$TaggedTypeSerializer.read(
DefaultSerializerRegistry.java:142
)

 
      at 
    org.gradle.internal.serialize.Serializers$StatefulSerializerAdapter$1.read(
Serializers.java:36
)

 
      at org.gradle.internal.remote.internal.inet.SocketConnection.receive(
SocketConnection.java:81
)

 
      … 28 more

Caused 
    by: java.io.IOException: Kurulan bir bağlantı, ana makinenizdeki yazılım 
    tarafından iptal edildi

 
      at sun.nio.ch.SocketDispatcher.read0(Native Method)

 
      at sun.nio.ch.SocketDispatcher.read(
SocketDispatcher.java:43
)

 
      at sun.nio.ch.IOUtil.readIntoNativeBuffer(
IOUtil.java:223
)

 
      at sun.nio.ch.IOUtil.read(
IOUtil.java:192
)

 
      at sun.nio.ch.SocketChannelImpl.read(
SocketChannelImpl.java:379
)

 
      at 
    org.gradle.internal.remote.internal.inet.SocketConnection$SocketInputStream.read(
SocketConnection.java:196
)

 
      at com.esotericsoftware.kryo.io.Input.fill(
Input.java:146
)

 
      … 35 more

TASK 
    EXECUTION FAILED

Task 
    completed in 4 seconds

Issue description

Every single old workspace I load, and new workspace I create, the workspace setup never fails to fail! And always fails on «Setting up gradle project…» The logs will probably help, but I tried everything — deleting the caches folder, deleting the whole gradle folder, deleting MCreator itself! Every solution I tried hadn’t worked, so while I did check the Github Issues, the MCreator forum and knoledge base, almost every one said to delete the gradle folder. Thank you!
Here’s a handy screenshot if you need it:

How to reproduce this issue?

On startup, I just created a new forge workspace. So, not very reproduceable (which is actually a word).

Operating system

Windows

Details

MCreator version: 2022.3
Generator type: forge-1.19.2

Example workspace

I mean, this is a completely new workspace that I just created and can’t open, but…
caw.zip

Logs

Executing Gradle task: eclipse
Build info: MCreator 2022.3.48217, forge-1.19.2, 64-bit, 7880 MB, Windows 11, JVM 17.0.3, JAVA_HOME: C:Users[username]MCreatorjdk, started on: 2023-01-16-11:04:23

org.gradle.tooling.GradleConnectionException: Could not install Gradle distribution from ‘https://services.gradle.org/distributions/gradle-7.5-bin.zip’.
at org.gradle.tooling.internal.consumer.DistributionFactory$ZippedDistribution.getToolingImplementationClasspath(DistributionFactory.java:135) at org.gradle.tooling.internal.consumer.loader.CachingToolingImplementationLoader.create(CachingToolingImplementationLoader.java:41) at org.gradle.tooling.internal.consumer.loader.SynchronizedToolingImplementationLoader.create(SynchronizedToolingImplementationLoader.java:44) at org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.onStartAction(LazyConsumerActionExecutor.java:160) at org.gradle.tooling.internal.consumer.connection.LazyConsumerActionExecutor.run(LazyConsumerActionExecutor.java:142) 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) at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64) at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56) at java.base/java.lang.Thread.run(Thread.java:833) Caused by: java.lang.RuntimeException: Timeout of 120000 reached waiting for exclusive access to file: C:Users[username].mcreatorgradlewrapperdistsgradle-7.5-binf1w0cc9nuo0eivz97x2xlu9svgradle-7.5-bin.zip
at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:65) at org.gradle.wrapper.Install.createDist(Install.java:48) at org.gradle.tooling.internal.consumer.DistributionInstaller.install(DistributionInstaller.java:73) at org.gradle.tooling.internal.consumer.DistributionFactory$ZippedDistribution.getToolingImplementationClasspath(DistributionFactory.java:129) … 14 more

TASK EXECUTION FAILED
Task completed in 2 minutes

Issue tracker rule checks (please read carefully)

• I have checked that my problem is not already reported
• I have checked that my problem is not covered on Knowledge Base or on MCreator’s Wiki
• I have checked that my written content does not violate the publishing guidelines

It can happen that you get gradle errors during the setup of MCreator or even later when suddenly builds stop working. Most of these errors are related to file permissions, firewalls and other OS elements that block MCreator from operating properly. To find the solution for your case, check the error log in the Console tab and look for error messages similar to the titles on this page and if you find one of these, go to the section under this title to look for the solution.

The most common solution

In most cases all Gradle errors are caused by one of these:

• Firewall or antivirus blocking MCreator
• Slow internet connection
• Your ISP blocking certain websites
• Too slow VPN or VPN with blocked domains that MCreator needs to access
• Any other software blocking access to download repository

The most common errors from Gradle are caused by firewalls or antivirus software. If you have any issues, we recommend you to temporarily turn off this software and try again. If this works, add MCreator as an exception to your firewall or antivirus or reconfigure the software properly to not block programs such as MCreator.

It can also happen that the servers from which Gradle downloads files (Minecraft servers, Minecraft Forge repo, Maven repository) are down and you might just need to try again later in such cases.

In some cases of unstable or slow connections, running the setup multiple times and when it fails with errors related to the internet connection (timeout errors, failed to connect, failed to GET, HEAD, …) clicking re-run the setup multiple times resolves the issue as eventually, all files get properly downloaded.

The second most common solution

In some cases, Gradle caches that make sure the build process does not take too long can get corrupted. In such a case, go to:

<your user home folder>/.mcreator/gradle

In this folder, there is a folder called caches. Delete this folder and open MCreator again. Next build will take a bit longer as caches need to be rebuilt. If you can not delete all files in this folder (which is necessary), reboot the computer first to remove any potential file locks.

If this is not enough to make things work, delete the entire gradle folder, not just caches, and try again.

If even this fails, try to delete the entire <your user home folder>/.mcreator/gradle folder, create a new workspace with the same generator version as the version of the workspace failing, after the setup of this new workspace is done, open your current workspace, and click Build & run -> Build workspace, then Build & run -> Reload gradle project and then Build & run -> Regenerate code and build.

Common error types

Could not get unknown property ‘runClient’ for root project ‘forge’

The first thing to check is to do The second most common solution described above.

Another solution is to make sure MCreator can write to the folder where the workspace is stored.

If none of this helps, do The second most common solution and reinstall MCreator before opening it again.

ValidatorException: PKIX path building failed

Example of the error log in the Console tab:

Download https://jcenter.bintray.com/commons-codec/commons-codec/1.6/commons-codec-1.6.jar
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
   at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
   at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
   at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
   at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
   at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1509)
   at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
   at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
   at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
   at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
   at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)

The most common cause for this issue is Antivirus with any advanced SSL or HTTPS security turned on. Such Antiviruses can alter certificates and cause Gradle to no properly recognize them. This can be caused by a firewall too.

Could not resolve all dependencies for configuration ‘:classpath’.

Example of the error log in the Console tab:

:decompileMc FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':decompileMc'.
> Could not resolve all dependencies for configuration ':forgeGradleMcDeps'.
> Could not resolve com.paulscode:codecjorbis:20101023.
Required by:
com.yourname.modid:forge:1.0
> Could not resolve com.paulscode:codecjorbis:20101023.

This issue is resolved by The most common solution described above.

java.util.zip.ZipException: error in opening zip file

Example of the error log in the Console tab:

Exception in thread "main" java.util.zip.ZipException: error in opening zip file
   at java.util.zip.ZipFile.open(Native Method)
   at java.util.zip.ZipFile.(ZipFile.java:219)
   at java.util.zip.ZipFile.(ZipFile.java:149)
   at java.util.zip.ZipFile.(ZipFile.java:163)
   at org.gradle.wrapper.Install.unzip(Install.java:159)
   at org.gradle.wrapper.Install.access$500(Install.java:26)
   at org.gradle.wrapper.Install$1.call(Install.java:69)
   at org.gradle.wrapper.Install$1.call(Install.java:46)
   at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:65)
   at org.gradle.wrapper.Install.createDist(Install.java:46)
   at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:126)
   at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)

This issue is resolved by The second most common solution described above (but delete the entire gradle folder, not just the folder caches in it). You might need to restart your computer before opening MCreator again too.

Timeout of 120000 reached waiting for exclusive access to file

Example of the error log in the Console tab:

Exception in thread "main" java.lang.RuntimeException: Timeout of 120000 reached waiting for exclusive access to file: C:Users<username>.mcreatorgradlewrapperdistsgradle-2.14-bin76oc0mnc3ieqtsukq90mp0rxkgradle-2.14-bin.zip
at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:61)
at org.gradle.wrapper.Install.createDist(Install.java:46)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:126)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)

Close MCreator and reboot your computer. Then read and do The second most common solution described above (but delete the entire gradle folder, not just the folder caches in it).

Could not connect to the Gradle daemon

Example of the error log in the Console tab:

FAILURE: Build failed with an exception.
* What went wrong:
Could not connect to the Gradle daemon.
Daemon uid: c7aac9bf-603e-4d48-8300-1ff078fbd044 with diagnostics:
Daemon pid: 600
  log file: C:UsersAloe.mcreatorgradledaemon2.14daemon-600.out.log
----- Last  20 lines from daemon log file - daemon-600.out.log -----

In most cases, this error can be fixed by rebooting MCreator. If this does not help, do The second most common solution described above.

Failed to load native library ‘native-platform.dll’ for Windows 10 amd64

Example of the error log in the Console tab:

FAILURE: Build failed with an exception.
* What went wrong:
Failed to load native library 'native-platform.dll' for Windows 10 amd64.
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

Go to:

<your user home folder>/.mcreator/gradle

In this folder, there is a folder called native. Delete this folder and open MCreator again. If this does not help, try reinstalling Minecraft on your computer and check your graphics card drivers (update them if there are updates).

org.lwjgl.LWJGLException: Pixel format not accelerated

Example of the error log in the Console tab:

[14:01:14] [main/ERROR]: Couldn't set pixel format
org.lwjgl.LWJGLException: Pixel format not accelerated
   at org.lwjgl.opengl.WindowsPeerInfo.nChoosePixelFormat(Native Method) ~[lwjgl-2.9.4-nightly-20150209.jar:?]
   at org.lwjgl.opengl.WindowsPeerInfo.choosePixelFormat(WindowsPeerInfo.java:52) ~[lwjgl-2.9.4-nightly-20150209.jar:?]
   at org.lwjgl.opengl.WindowsDisplay.createWindow(WindowsDisplay.java:247) ~[lwjgl-2.9.4-nightly-20150209.jar:?]
   at org.lwjgl.opengl.Display.createWindow(Display.java:306) ~[lwjgl-2.9.4-nightly-20150209.jar:?]
   at org.lwjgl.opengl.Display.create(Display.java:848) ~[lwjgl-2.9.4-nightly-20150209.jar:?]
   at org.lwjgl.opengl.Display.create(Display.java:757) ~[lwjgl-2.9.4-nightly-20150209.jar:?]
   at net.minecraft.client.Minecraft.createDisplay(Minecraft.java:624) [Minecraft.class:?]
   at net.minecraft.client.Minecraft.init(Minecraft.java:457) [Minecraft.class:?]
   at net.minecraft.client.Minecraft.run(Minecraft.java:377) [Minecraft.class:?]
   at net.minecraft.client.main.Main.main(SourceFile:123) [Main.class:?]

This error usually means that you have an unsupported graphics card for Minecraft our outdated graphics card drivers. These pages could help:

• https://help.mojang.com/customer/en/portal/articles/928791-problematic-frame-or-pixel-format-not-accelerated
• http://hopper.minecraft.net/help/pixel-format-not-accelerated/
• https://github.com/tryashtar/minecraft-bugs/issues/279
• https://answers.microsoft.com/en-us/windows/forum/windows_8-gaming/minecraft-pixel-format-not-accelerated-after-win/cc02d21d-4039-412c-8b8b-84b10b32e872?auth=1

Sometimes reinstallation of Minecraft can help too.

Expected BEGIN_OBJECT but was STRING at line 1 column 1

Example of the error log in the Console tab:

FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring root project '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.

This issue is resolved by The second most common solution described above (but delete the entire gradle folder, not just the folder caches in it). You might need to restart your computer before opening MCreator again too.

Gradle task compileJava FAILED with errors of type «Override is not a repeatable annotation type»

In some cases, links to the libraries from the Gradle build system can get lost and MCreator builds will stop working. Especially some mod elements such as GUIs and dimensions are prone to this happening. When this happens, the following solution usually fixes this error:

Go to the Build & run menu and click the following two options in the given order

1. Reload Gradle project
2. Regenerate code and build

Wait for the workspace code to be regenerated and the error should be gone.

Gradle task compileJava FAILED with 100 errors of type «cannot find symbol»

This issue is resolved by The second most common solution described at the top of this page. After applying the solution, run the build again.

Error occurred during initialization of VM: Picked up _JAVA_OPTIONS

This error indicates there is an override for JAVA_OPTIONS defined somewhere. There are multiple possible places:

1. Check your computer environment variables (system and user) and if there is a parameter _JAVA_OPTIONS or JAVA_OPTIONS present, remove it from the list
2. It was reported that Razer Synapse software can override this parameter and cause compatibility problems. In this case, consider disabling or uninstalling this software

If these two do not help, make sure you are using a 64-bit version of MCreator if your computer is 64-bit, as this may cause such a problem too.

This may not be what you want to hear, but I would recommend not using mcreator, as it is a awful program with tons of bugs, among many other things (such as being a much less powerful tool that plain forge).

On top of that, you probably won’t get help as people who know how to fix these errors do not use mcreator (also many errors might be due to pylo)

From the error log, it seems that the error is probably not your fault, so you should report this to pylo.

I can’t tell you how to fix it, but if you were to show me the code (if you can do that) I probably could.

It appears that it is unable to find the class objects for your various coins «error: cannot find symbol mcreator_money … symbol: class mcreator_money», etc.

I don’t know what your reason for using mcreator is (whether it be lack of java knowledge, lack of confidence in java skills, uncertainty that despite knowledge of java minecraft modding might be really confusing), but regardless, I would strongly recommend downloading the forge mdk (available here), and following tutorials to get started, and referencing them or minecraft’s source code, or asking for help on the forums if you get stuck.

This may not be what you want to hear, but I would recommend not using mcreator, as it is a awful program with tons of bugs, among many other things (such as being a much less powerful tool that plain forge).

On top of that, you probably won’t get help as people who know how to fix these errors do not use mcreator (also many errors might be due to pylo)

From the error log, it seems that the error is probably not your fault, so you should report this to pylo.

I can’t tell you how to fix it, but if you were to show me the code (if you can do that) I probably could.

It appears that it is unable to find the class objects for your various coins «error: cannot find symbol mcreator_money … symbol: class mcreator_money», etc.

I don’t know what your reason for using mcreator is (whether it be lack of java knowledge, lack of confidence in java skills, uncertainty that despite knowledge of java minecraft modding might be really confusing), but regardless, I would strongly recommend downloading the forge mdk (available here), and following tutorials to get started, and referencing them or minecraft’s source code, or asking for help on the forums if you get stuck.