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
- Reload Gradle project
- 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:
- 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
- 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.
Issue description
Gradle project setup Fail
How to reproduce this issue?
Started up MCreator (first time), made new workspace, and it failed on setting up the Gradle project. I’ve looked through lots of solutions and followed the steps but nothing fixed it, I reinstalled gradle, MCreator, and whitelisted it on my antivirus and firewall. Nothing seems to work, and I was looking forward to using this application to make mods.
Operating system
Windows
Details
2021.3, forge 1.17.1 37.1.1
Example workspace
extra_foods.zip
Logs
Executing Gradle task: eclipse
Build info: MCreator 2021.3.54000, forge-1.17.1, 64-bit, 16303 MB, Windows 10, JVM 16.0.2, JAVA_HOME: C:Program FilesPyloMCreatorjdk
FAILURE: Build failed with an exception.
- What went wrong:
A problem occurred configuring root project ‘extra_foods’.
Could not resolve all artifacts for configuration ‘:classpath’.
Could not download fastutil-8.3.1.jar (it.unimi.dsi:fastutil:8.3.1)
Could not get resource ‘https://maven.minecraftforge.net/it/unimi/dsi/fastutil/8.3.1/fastutil-8.3.1.jar’.
Tag mismatch!
- Try:
Run with —stacktrace option to get the stack trace. Run with —info or —debug option to get more log output. Run with —scan to get full insights. - Get more help at https://help.gradle.org
BUILD FAILED in 5s
BUILD FAILED
Task completed in 5 seconds
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
-
#2
Проблема в этом:
FAILURE: Build failed with an exception. * Where: Build file 'C:PyloMCreator176forgebuild.gradle' line: 10 * What went wrong: A problem occurred evaluating root project 'forge'. > Failed to apply plugin [id 'net.minecraftforge.gradle.forge'] >
-
#3
И как-же её решить, я так-то бум-бум
-
#5
Пожалуйста, помогите мне а не пишите всякую фигню по типу — Mcreator гамно, делай моды сам. Я прошу вас помочь а не порофлить.
-
#6
Как же так! Возникла проблема с волшебной палочкой? И не знаешь как её чинить? Вот почему эльфы не любят магию.
Удали градл и возьми новый где-нибудь
-
#7
Либо я тупой, либо mcreator тупой, но до переустановки системы всё без градла работало.
Даже версия MCreator была одинакова.
-
#8
Не хочу обидеть но и ты тупой и МКруыторрр тупой.
-
#9
Либо я тупой, либо mcreator тупой
Я бы не исключал возможность обоих условий выдать истину…
-
#10
Не знаю как, но путём переустановки mcreator мод компилируется но ошибку ещё выдаёт.
И эт, самое, Xcom, обоснуй причину оскорбления.
(после второй попытки компиляции, ошибка исчезла, уряяяяя)
-
#11
И эт, самое, Xcom, обоснуй причину оскорбления
Это не оскорбление, это мой личный ответ на твой вопрос.
-
#12
Это не оскорбление, это мой личный ответ на твой вопрос.
Ну вообще это не ответ, ответил мне Resistance Dog.
-
#13
Я ответил на данный «вопрос«:
Либо я тупой, либо mcreator тупой
Bất cứ khi nào tôi muốn tạo một không gian làm việc mới hoặc tải một không gian làm việc, tôi gặp lỗi sau:
Thực thi
nhiệm vụ Gradle: eclipse
Thông tin bản dựng : MCreator 2021.1.16710, forge-1.16.5, 64-bit, 8070 MB, Windows 10,
JVM 1.8.0_275, JAVA_HOME: C: Program Files Pylo MCreator jdk
Tác vụ: downloadMcpConfig
Nhiệm vụ: extractSrg UP-TO-DATE
Tác vụ: createSrgToMcp UP-TO-DATE
Nhiệm vụ: tải xuốngMCMeta UP-TO-DATE
Sao chép
đối tượng cục bộ: 32 / 32577f37afeff9997b55c3d5fa5316db0ded0071 Nội dung:
minecraft / lang / ru_ru.json
minecraft / lang / ru_ru.json
Hash không thành công.
Tác vụ: downloadAssets FAILED
THẤT BẠI:
Xây dựng không thành công với một ngoại lệ.
- Đã
xảy ra sự cố:
Không thực thi được
tác vụ ‘: downloadAssets’.
Không tải được nội dung: minecraft / lang / ru_ru.json
Không thể tải xuống hoặc xác thực một số nội dung, hãy thử chạy lại tác vụ.
- Hãy thử:
Chạy
với tùy chọn —stacktrace để lấy dấu vết ngăn xếp. Chạy với
tùy chọn —info hoặc —debug để nhận được nhiều đầu ra nhật ký hơn. Chạy với —scan để có được
thông tin chi tiết đầy đủ .
- Nhận thêm trợ giúp tại https://help.gradle.org
Các
tính năng Gradle không dùng nữa đã được sử dụng trong bản dựng này, khiến nó không tương thích với
Gradle 7.0.
Sử dụng
‘- tất cả chế độ cảnh báo’ để hiển thị các cảnh báo không dùng nữa.
Xem
https://docs.gradle.org/6.8.1/userguide/command_line_interface.html#sec…
XÂY DỰNG
THẤT BẠI trong 11 giây
5
nhiệm vụ có thể hành động: 2 thực thi, 3 cập nhật
XÂY DỰNG
THẤT BẠI
Nhiệm vụ
hoàn thành sau 11 giây
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
- Reload Gradle project
- 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:
- 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
- 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.