Что делать если mcreator выдает ошибку

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, restart the computer first. Then (without opening MCreator after the reboot), 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 (but restart the computer again first), 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.

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.

Gradle setup and build errors

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:

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 /.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:

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:

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:

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:

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:

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:

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:

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

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:

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.

Источник

И так начнём с того, что все ошибки указанные ниже, были обнаружены на версии 1.4.5 для версии Minecraft’a 1.7.2! Кстати всё что выделено коричнево-оранжевым цветом будет внизу описано более подробно!
Приступим:
Ошибки во время установки , скорее всего связаны с в Вашей криворукостью!
Решение:
Попробуйте переустановить minecraft! Он обязательно должен лежать в папке .minecraft!
Проверти подходит ли версия программы к версии minecraft’a!
Попробуйте установить forge или его переустановить!
Поудаляйте моды!
Ошибки во время создания или загрузки текстур блоковвещей!
Решение:
Народный способ: просто напросто пересоздать текстуру! Возможно текстура которая сделана не с помощью MCreator’a, в формате Jpg — решить это можно легко! Откройте вашу текстуру в любом ГрафРедакторе и сохраните в формате PNG !
Слишком большой размер — либо много весит, либо слишком большая. Первое решается так — открываете в ГР текстуру и сохраняете в худшем качестве (photoshop)!
Ну с большим размером (пикселы) думаю всё понятно! Советую делать текстуры для первого раза в размере 16х16 пикс.
Вылет при создании мода.
Пока нет решения.
Извиняюсь, но тут я бессилен!
Ошибки во время рекомпляции мода
Решение
Возможно в вашем моде присутствуют не поддерживаемые символы !
Или в вашем моде не стыковка, например во время создания event’a вы сделали помарку! Обращайте на это больше внимания!
Фиолетово- чёрные текстуры после создания мода !
Решение
Формат jpg (рассказывалось ранее)!
Возможно у вас текстуры не сохранились в архиве, у меня была эта ошибка и решил я её как ни странно быстро! После того как вы загрузили текстуру, её копия должна лежать в папке, а как её открыть написано ниже! После того как мы её открыли видим те текстуры (в папках Block, Item, и ещё какая ) копируем все эти три папки в архив с нашим модом (там должен быть такой же путь как и у папки с нашими текстурами)!

Тот самый низ что был вверху!
ГрафРедактор или Графический редактор — это paint, photoshop и.т.д!
ГР — сокращение Графического редактора!
Рекомпляция — это создание вашего мод, ход данного действия можно отследить сдесь:

После синих «Букв» идут красные, а потом зелёные, то значит всё чики-пуки
Поддерживаемые символы — это все знаки препинания и цифры, а также только английский язык! А как перевести ваш мод на Русский язык, я расскажу в следующем гайде!
Ну вот и всё ребяты! Вот вам ссылка что-бы скачать MCREATOR!
P.S Указывайте что я пропустил и оцените мой труд. Писал статью где то минут 20!

Источник

Что делать если mcreator выдает ошибку

Gradle setup and build errors

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:

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 /.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:

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:

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:

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:

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:

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:

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:

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

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:

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.

Donate to MCreator

By donating to developers you can speed up development, as with more resources, we can dedicate more time to MCreator. It is a free project made by developers working on it in their free time.

GeckoLib + MCreator | Ошибка при установке.

Столкнулся с проблемой загрузки GeckoLib в программу MCreator .

При компиляции или после перегенерации кода выскакивает ошибка:

По инструкции и гайдам требуется скачать плагин — Feder’s Geckolib 2.0.0 Plugin | MCreator и поместить его в папку plagins
после зайти во вкладку » Рабочее пространство/Настройки рабочего пространства. /Внешние API » и поставить галочку на против пункта GeckoLib API .

После чего по «сюжету» мы перегенерируем код.

Но тут же в консоли выскакивает ошибка

Все эти ссылки не работают.
На форумах пусто.
В интернете ничего нет.
Дальше forge_grable путь не сходится.

В чем может быть проблема? Есть ли те, кого всё работает? Какую версию Mc вы используете и может ли скинуть архивом папку bernie с всем содержимым?
Буду очень признателен.

Problems With MCreator? (Fix Tutorial)(OLD, MIGHT NOT HELP ANYMORE)

Hey, i tried making a mod for 1.7.10 version 1.7.3 everything goes well at first but when i try and launch the game it just crashed before the menu screen pops up, its a custom model with custom textures btw.

did not work in 1.12.2 either

Executing gradle command: cleanCache clean setupDecompWorkspace —refresh-dependencies
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:PyloMCreator176>cd forge
C:PyloMCreator176forge>SET «JAVA_HOME=C:PyloMCreator176jdk32»
C:PyloMCreator176forge>SET JAVA_EXE=%JAVA_HOME%binjava.exe
C:PyloMCreator176forge>SET PATH=%JAVA_HOME%bin;%PATH%
C:PyloMCreator176forge>gradlew -Dorg.gradle.jvmargs=»-Xms512m -Xmx1024m» cleanCache clean setupDecompWorkspace —refresh-dependencies
This mapping ‘snapshot_20170624’ was designed for MC 1.12! Use at your own peril.
#################################################
ForgeGradle 2.3-SNAPSHOT-583d1ba
github.com/MinecraftForge/ForgeGradle
#################################################
Powered by MCP unknown
modcoderpack.com
by: Searge, ProfMobius, Fesh0r,
R4wk, ZeuX, IngisKahn, bspkrs
#################################################
:cleanCache
:clean
:deobfCompileDummyTask
:deobfProvidedDummyTask
:getVersionJson
:extractUserdev
:extractDependencyATs SKIPPED
:extractMcpData
:extractMcpMappings
:genSrgs
:downloadClient
:downloadServer
:splitServerJar
:mergeJars
:deobfMcSRG
Applying SpecialSource.
Applying Exceptor.
:decompileMc
Error occurred during initialization of VM
Could not reserve enough space for 3145728KB object heap
:decompileMc FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ‘:decompileMc’.
> Process ‘command ‘C:PyloMCreator176jdk32binjava.exe» finished with non-zero exit value 1
* Try:
Run with —stacktrace option to get the stack trace. Run with —info or —debug option to get more log output.
BUILD FAILED
Total time: 2 mins 38.748 secs
C:PyloMCreator176forge>
Task completed with return code 0 in 161306 milliseconds

I have this error on Mcreator.
(This report is from the console)
for some reason the «test game» doesn’t load and sends me this report:
here it is:

Что делать если mcreator выдает ошибку

Дело в том что вылазит ошибка на Testing status of code.В чём проблема ? Очень долго в интернете рылся так и не нашел ответ на свою проблему. Может как то эту программу заменить на другую подобную можно? если да то какую)

Моя задача переделать мир на более читерский.типа
заранее спасибо всем откликнувшимся

———
я всё правильно написал гражданин ya can ru, я говорю про обычную игру Minecraft! В программе mccreator абсолютно ничего нельзя сделать в мультиплеере, это только для синглплеера. Проблема так и не решилась. Спасибо всем кто помогал!

[color=gray][size=9]Редактировалось 6 раз(а), последний 2014-02-04 19:03:31[/size][/color]

Источник

[Разное] Как исправить некоторые ошибки в MCreator?

И так начнём с того, что все ошибки указанные ниже, были обнаружены на версии 1.4.5 для версии Minecraft’a 1.7.2! Кстати всё что выделено коричнево-оранжевым цветом будет внизу описано более подробно!
Приступим:
Ошибки во время установки , скорее всего связаны с в Вашей криворукостью!
Решение:
Попробуйте переустановить minecraft! Он обязательно должен лежать в папке .minecraft!
Проверти подходит ли версия программы к версии minecraft’a!
Попробуйте установить forge или его переустановить!
Поудаляйте моды!
Ошибки во время создания или загрузки текстур блоковвещей!
Решение:
Народный способ: просто напросто пересоздать текстуру! Возможно текстура которая сделана не с помощью MCreator’a, в формате Jpg — решить это можно легко! Откройте вашу текстуру в любом ГрафРедакторе и сохраните в формате PNG !
Слишком большой размер — либо много весит, либо слишком большая. Первое решается так — открываете в ГР текстуру и сохраняете в худшем качестве (photoshop)!
Ну с большим размером (пикселы) думаю всё понятно! Советую делать текстуры для первого раза в размере 16х16 пикс.
Вылет при создании мода.
Пока нет решения.
Извиняюсь, но тут я бессилен!
Ошибки во время рекомпляции мода
Решение
Возможно в вашем моде присутствуют не поддерживаемые символы !
Или в вашем моде не стыковка, например во время создания event’a вы сделали помарку! Обращайте на это больше внимания!
Фиолетово- чёрные текстуры после создания мода !
Решение
Формат jpg (рассказывалось ранее)!
Возможно у вас текстуры не сохранились в архиве, у меня была эта ошибка и решил я её как ни странно быстро! После того как вы загрузили текстуру, её копия должна лежать в папке, а как её открыть написано ниже! После того как мы её открыли видим те текстуры (в папках Block, Item, и ещё какая ) копируем все эти три папки в архив с нашим модом (там должен быть такой же путь как и у папки с нашими текстурами)!

Тот самый низ что был вверху!
ГрафРедактор или Графический редактор — это paint, photoshop и.т.д!
ГР — сокращение Графического редактора!
Рекомпляция — это создание вашего мод, ход данного действия можно отследить сдесь:

После синих «Букв» идут красные, а потом зелёные, то значит всё чики-пуки
Поддерживаемые символы — это все знаки препинания и цифры, а также только английский язык! А как перевести ваш мод на Русский язык, я расскажу в следующем гайде!
Ну вот и всё ребяты! Вот вам ссылка что-бы скачать MCREATOR!
P.S Указывайте что я пропустил и оцените мой труд. Писал статью где то минут 20!

Источник

Почему не работает mcreator

#1 | 3 декабря 2014 — 21:03

ЯndomTrash

Звание: Бабка на лавке

#2 | 4 декабря 2014 — 08:31

Makara

#3 | 4 декабря 2014 — 10:50

MegaZerg

Звание: Резиновый дедушка 🙂

#4 | 4 декабря 2014 — 11:08

Makara

#5 | 5 декабря 2014 — 15:50

MrGrib

Звание: Пользователь, просто пользователь

#6 | 5 декабря 2014 — 16:36

Kakulinina

Звание: Активный человек

Где ты, моя идеальная сборка:)

#7 | 11 декабря 2014 — 13:33

max2003jetix

Просто хорошие люди

0% кубиков.
Епицентр горящих задниц Тык
Хватит заливать на ЯД и ДФ. Официальные ссылки плес.
240/420/123/123,4

#8 | 11 декабря 2014 — 14:01

Kakulinina

Звание: Активный человек

Где ты, моя идеальная сборка:)

#9 | 11 декабря 2014 — 16:18

Kakulinina

Звание: Активный человек

Где ты, моя идеальная сборка:)

#10 | 13 декабря 2014 — 18:27

I_RADEN_I

#11 | 30 января 2015 — 19:13

max2003jetix

Просто хорошие люди

0% кубиков.
Епицентр горящих задниц Тык
Хватит заливать на ЯД и ДФ. Официальные ссылки плес.
240/420/123/123,4

#12 | 30 января 2015 — 23:29

gamaleev0071

#13 | 12 февраля 2015 — 14:18

Creeper_2x2

Звание: Пользователь, просто пользователь

теперь мне плевать на всё: ПЫТАЮсь роботАть в MineIMator Demo 5 Update

#14 | 29 мая 2015 — 13:27

Статистика форума

Сейчас онлайн: 29

Администраторы | Главные редакторы | Модератор | Дедушки | Журналисты | HENTAI BOY | Goldфаги | Журналисты-олдфаги | ТруЪ Олдфаги-с | ТруЪ Плагинщик | Олдфаги | true Художник | Модератор бездны | Картоделы | XXXL ПХЛ | Просто хорошие люди | Посетители | Новички

Источник

Тема: MCreator

Опции темы

Поиск по теме

Отображение

MCreator

Хочу создать свой мод но после экспорта ничего не создается!Англисский я зную ужасно! Скрины всего https://imgur.com/a/cmCFI

нНа последнем скрине ясно видно чте ничего не создалось!

На предпоследнем скрине я нажал на I agree

Ты пробовал его компилировать и запускать на виртуалке, которая предоставляется самим MCreator?

И, если я правильно понимаю, то на последнем скрине показано исключительно директория с assets’aми. Если я не ошибаюсь, ты не там мод готовый ищешь.

Последний раз редактировалось MercuryANEZ; 05.03.2018 в 14:28 .

Где его искать тогда? И куда создавать? Я программирование не каплю не знаю можно подробнее

Дело не в этом. Есть директория (в народе называют «Папкой»), в которой лежит твой jar-ник с модом. И он недалеко от твоего MCreator’a , в этом я уверен.

Лично я, если и пишу моды, то делаю это сам. MCreator’ом не пользовался и не планирую

МОжете пожалуйста какой то гайд так как я ничего не понял? МНенужен гайд а не

Так как я ничего не понял!

Открываешь значит ты MCreator.
Создал значит ты пару предметов, UI и ещё чего-нибудь в своём моде.
Не буду углубляться. Просто скажу, что тебе, прежде чем мод копировать и т.д. — нужно его протестировать. Тем самым программа, а именно MCreator соберёт мод по файлам.

После этого, ты видишь, как открывается виртуальное окно с майнкрафтом. Ты проверяешь всю работоспособность.

После этого ты закрываешь окно виртуального майна. Нажимаешь Export. Он тебе должен в папку сгенерировать файл. Он имеет расширение .jar (КАК УЗНАТЬ — САМ НАЙДЁШЬ, ЭТО УЖЕ ПЕРЕБОР).
Он имеет название твоего мода (как ты его называл). Пример : testmod.jar.

Доступнее уже некуда. Если не понял это — лучше вообще не берись за мододелание. Хотя если ты их «пишешь» через MCreator — тебя даже мододелом не назовёшь. Все классы инициализаций мода имеют префикс mcreator: .
Так что оно будет палиться, что мод явно не твой.

Кстать можно ещё чем открывать файл class а то когда я его блокнотом открываю у меня какие то карючки

Во-первых: что за class-файл и где ты его нашёл?

Если ты открыл архив, нашёл там класс мода — ты хоть головой об стену бейся, а открыть не сможешь через блокнот и даже Notepad.

Как бы сделал я (возможно есть и другие способы, но я о них не знаю) : если я угадал, и ты пытался просмотреть файлы другого мода, то :
А) Не делай этого. Как минимум, потому что ты ничего не поймёшь там. Там и шаблоны функций, и классы инициализаций есть. Я сам не всё досконально понимаю в исходника мода.
В) Не факт, что мод имеет открытый код. В некоторых модах используется обфускация кода. Это вызвано нежеланием разработка, чтобы его мод кто-то переписывал под себя.
С) Этот мод нужно импортировать в какую-нибудь IDE для Java. К примеру, самая простая и доступная — это Eclipse. Скачиваешь пакеты Eclipse Java IDE, импортирует в неё архив мода, а там уже и видно будет. Но, скорее всего, ты упрешься в пункт А или В.

Погоди, в смысле «чем открывать»? Если ты пытаешься открыть свой мод, который сделал, то ты можешь это сделать прямо в MCreator’e. Там даже есть вкладка «Open Source Code» или «View Source Code». Там должен быть такой тёмный интерфейс с цветовым выделением элементов класса, чем-то напоминать будет интерфейс CLion.

Последний раз редактировалось Jekach28; 06.03.2018 в 08:26 .

Источник

MCreator Problems

• Modifications:
• Forum topics:
• Wiki pages:
• Tracker tickets:
• MCreator plugins:
• Comments:

For not making a topic for every problem that I have with mcreator, here is a topic for all my future problems.

Problem 1 S — Textures are saying Bye-bye

I had a black-out when I was recompiling my mod. The day after all the textures in the inventory were gone.

So I decided to reinstall MCreator for trying to fix the problem.

When I try to install it, an error appears. The installation folder is different from the old mcreator folder (I wrote C:PyloMCreator175new).

The bug is when Mcreator is downloading extra files, and not in the installer.

Code of the install error: Uh sorry. For copying the destination folder, I’ve deleted the code. Now I need to wait MCreator installation.

EDIT: Error code:
Executing gradle command: cleanCache clean setupDecompWorkspace —refresh-dependencies
Microsoft Windows [Versione 10.0.15063]
(c) 2017 Microsoft Corporation. Tutti i diritti sono riservati.
C:PyloMCreator175new>cd forge
C:PyloMCreator175newforge>SET «JAVA_HOME=C:PyloMCreator175newjdk32»
C:PyloMCreator175newforge>SET JAVA_EXE=%JAVA_HOME%binjava.exe
C:PyloMCreator175newforge>SET PATH=%JAVA_HOME%bin;%PATH%
C:PyloMCreator175newforge>gradlew -Dorg.gradle.jvmargs=»-Xms512m -Xmx1024m» cleanCache clean setupDecompWorkspace —refresh-dependencies
This mapping ‘snapshot_20161220’ was designed for MC 1.11! Use at your own peril.
#################################################
ForgeGradle 2.2-SNAPSHOT-eb2e450
https://github.com/MinecraftForge/ForgeGradle
#################################################
Powered by MCP unknown
http://modcoderpack.com
by: Searge, ProfMobius, Fesh0r,
R4wk, ZeuX, IngisKahn, bspkrs
#################################################
:cleanCache
:clean UP-TO-DATE
:deobfCompileDummyTask
:deobfProvidedDummyTask
:getVersionJson
:extractUserdev
:extractDependencyATs SKIPPED
:extractMcpData
:extractMcpMappings
:genSrgs
:downloadClient
:downloadServer
:splitServerJar
:mergeJars
:deobfMcSRG
Applying SpecialSource.
Applying Exceptor.
:decompileMc
Error occurred during initialization of VM
Could not reserve enough space for 3145728KB object heap
:decompileMc FAILED
FAILURE: Build failed with an exception.
BUILD FAILED
* WhatExecution faiTotal time: 2 mins 17.607 secs
led for task ‘:decompileMc’.
went wrong:
> Process ‘command ‘C:PyloMCreator175newjdk32binjava.exe» finished with non-zero exit value 1
* Try:
Run with —stacktrace option to get the stack trace. Run with —info or —debug option to get more log output.
C:PyloMCreator175newforge>
Task completed with return code 0 in 138098 milliseconds EDIT 2: it was only a Firewall problem

Problem 2 S — The Darkstone Lamp is Evil

I’ve made a thing like a redstone lamp and I’ve made 2 blocks for it. In the first I made a redstone on event that makes the 2nd block and in the 2nd I made a redstone off event that makes the first. The recompilation sayed that the 2nd block was bugged (it sayed something eith else and if). I can’t code, but I went to the error and I’ve tried to edit it by simply closing the code to mcreator, copying the @override etc. part of the first in the 2nd,deleting the old @override of the 2nd, sobstituiting the > in the power part with an = and changing the id of the block to make. Now it says an abnormal error.

Problem 3 S — The Barrel thinks that is a wood container

I’ve a 3d model problem: I’ve made a barrel. It can be filled with water and later used to make juices. The empty barrel works fine, the problem is in all the filled barrels (water barrel, cherry juice barrel, etc.). It should use two textures :the wood texture and the texture of the water/juice. It uses the wood texture for everything. So the water is. A wood block. I’ve tried to make a new nit animated texture for water, but it still doesn’t work. The texture 0 is wood planks and the texture 2 water/cherry juice.

lol «waater instead of water»

Code of the Barrel:

import net.minecraftforge.fml.relauncher.SideOnly;
import net.minecraftforge.fml.relauncher.Side;
import net.minecraftforge.fml.common.registry.GameRegistry;
import net.minecraftforge.fml.common.event.FMLServerStartingEvent;
import net.minecraftforge.fml.common.event.FMLPreInitializationEvent;
import net.minecraftforge.fml.common.event.FMLInitializationEvent;

import net.minecraft.world.World;
import net.minecraft.world.IBlockAccess;
import net.minecraft.util.math.BlockPos;
import net.minecraft.util.math.AxisAlignedBB;
import net.minecraft.util.EnumHand;
import net.minecraft.util.EnumFacing;
import net.minecraft.util.BlockRenderLayer;
import net.minecraft.item.ItemStack;
import net.minecraft.item.ItemBlock;
import net.minecraft.item.Item;
import net.minecraft.entity.player.EntityPlayer;
import net.minecraft.client.renderer.block.model.ModelResourceLocation;
import net.minecraft.client.Minecraft;
import net.minecraft.block.state.IBlockState;
import net.minecraft.block.material.Material;
import net.minecraft.block.SoundType;
import net.minecraft.block.Block;

public class mcreator_filledbarrel <

public static BlockFilledbarrel block;

public static Object instance;

public int addFuel(ItemStack fuel) <
return 0;
>

public void serverLoad(FMLServerStartingEvent event) <
>

public void preInit(FMLPreInitializationEvent event) <
block.setRegistryName(«filledbarrel»);
GameRegistry.register(block);
GameRegistry.register(new ItemBlock(block).setRegistryName(block.getRegistryName()));
>

public void registerRenderers() <
>

public void load(FMLInitializationEvent event) <
if (event.getSide() == Side.CLIENT) <
Minecraft.getMinecraft().getRenderItem().getItemModelMesher()
.register(Item.getItemFromBlock(block), 0, new ModelResourceLocation(«testenvironmentmod:filledbarrel», «inventory»));
>
>

block = (BlockFilledbarrel) (new BlockFilledbarrel().setHardness(2.0F).setResistance(10.0F).setLightLevel(0.0F)
.setUnlocalizedName(«Filledbarrel»).setLightOpacity(0).setCreativeTab(mcreator_raolblocks.tab));
block.setHarvestLevel(«axe», 0);
>

public void generateSurface(World world, Random random, int chunkX, int chunkZ) <
>

public void generateNether(World world, Random random, int chunkX, int chunkZ) <
>

static class BlockFilledbarrel extends Block <

int a1 = 0, a2 = 0, a3 = 0, a4 = 0, a5 = 0, a6 = 0;

boolean red = false;

protected BlockFilledbarrel() <
super(Material.WOOD);

@Override
public void onBlockAdded(World world, BlockPos pos, IBlockState state) <
int i = pos.getX();
int j = pos.getY();
int k = pos.getZ();
world.scheduleUpdate(new BlockPos(i, j, k), this, this.tickRate(world));

@Override
public int getWeakPower(IBlockState blockState, IBlockAccess blockAccess, BlockPos pos, EnumFacing side) <
return red ? 15 : 0;
>

@Override
public int getStrongPower(IBlockState blockState, IBlockAccess blockAccess, BlockPos pos, EnumFacing side) <
return red ? 15 : 0;
>

@Override
public boolean onBlockActivated(World world, BlockPos pos, IBlockState state, EntityPlayer entity, EnumHand hand, EnumFacing side,
float hitX, float hitY, float hitZ) <
int i = pos.getX();
int j = pos.getY();
int k = pos.getZ();
if (entity.inventory.getCurrentItem() != null && entity.inventory.getCurrentItem().getItem() == mcreator_emptyglass.block) <

if (true) <
if (entity instanceof EntityPlayer)
((EntityPlayer) entity).inventory.clearMatchingItems(mcreator_emptyglass.block, -1, 1, null);
>

if (true) <
if (entity instanceof EntityPlayer)
((EntityPlayer) entity).inventory.addItemStackToInventory(new ItemStack(mcreator_waterglass.block, 1));
>

if (true) <
world.setBlockState(new BlockPos(i, j, k), mcreator_emptybarrel.block.getDefaultState(), 3);
>

if (entity.inventory.getCurrentItem() != null && entity.inventory.getCurrentItem().getItem() == mcreator_cherryerryerry.block) <

if (true) <
if (entity instanceof EntityPlayer)
((EntityPlayer) entity).inventory.clearMatchingItems(mcreator_cherryerryerry.block, -1, 1, null);
>

if (true) <
world.setBlockState(new BlockPos(i, j, k), mcreator_cherrybarrel.block.getDefaultState(), 3);
>

@Override
public boolean isOpaqueCube(IBlockState state) <
return false;
>

@SideOnly(Side.CLIENT)
@Override
public BlockRenderLayer getBlockLayer() <
return BlockRenderLayer.CUTOUT;
>

@Override
public AxisAlignedBB getBoundingBox(IBlockState state, IBlockAccess source, BlockPos pos) <
return new AxisAlignedBB(0.0D, 0.0D, 0.0D, 1.0D, 1.0D, 1.0D);
>

@Override
public int tickRate(World world) <
return 10;
>

@Override
public int quantityDropped(Random par1Random) <
return 1;
>

@Override
public Item getItemDropped(IBlockState state, Random par2Random, int par3) <
return new ItemStack(mcreator_emptybarrel.block).getItem();
>
>
>

Problem 4 S — Minecraft doesn’t want to start

When I try to do RunClient, an unknown error appears. (I’ve Just Enough Items in the mods folder, but it worked before in the runclient)

Источник

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.

Issue description

I’ve updated to the official release of MCreator 2023.1 today, and rebuilt my project, but every time I now try to generate or load a world with the datapack containing the mod’s generation resourced, I get the message «Datapack Generation Failed» in-game.
Everything has worked perfectly in the official 2022.3 release, and the only thing I did was update.
My guess is that it has to do with structures and biomes, because all the overworld biomes I made that were not set to generate in caves did not place anything over the surface, and none of the structures generated.

Here’s a link to a document containing the log:
https://docs.google.com/document/d/1uxWm69padhoisqpZJB0FYMC1gc7kipMpj846Ijv0OnM/edit?usp=sharing

For the time being, I am going to revert back to 2022.3.

How to reproduce this issue?

Step 1: Make a few biomes and structures in MCreator 2022.3
Step 2: Update to 2023.1
Step 3: Compile and start the game
Step 4: Attempt to generate a new world.

Operating system

Windows

Details

MCreator version: [2023.1 / branch:master]
Generator type: [forge-1.19.2]

Example workspace

Could not reproduce bug in minimal workspace.
Download to full workspace:
https://www.mediafire.com/file/oc249o8022kg61j/FullBackup202200348217.zip/file

Logs

No response

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