Что делать если 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 (Microsoft Defender can cause problems too) 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 the 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.

How to add needed folders to Microsoft Defender exclusions?

To do this, do the following steps:

Search for «Virus & threat protection» within the Windows start menu

Click «Virus & threat protection settings»
Click «Add an exclusion» and select «Folder» from the drop-down menu

/.mcreator/
/MCreatorWorkspaces
Any other folder where you store your MCreator workspaces

Keep in mind this will not only reduce the amount of problems with Gradle, but will also increase the build and workspace setup times significantly. Keep in mind that this will make those folders not be scanned so make sure to check them manually with manual scan from time to time to be sure there are no threats located in those folders.

You can also add folder exclusions using the command line if you prefer this approach. Keep in mind this approach is more advanced and complex. Run the command line as administrator and use the following command with the selected folder path:

powershell -inputformat none -outputformat none -NonInteractive -Command Add-MpPreference -ExclusionPath «*»

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:

In this folder, there is a folder called caches. Delete this folder and open MCreator again. The 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 /.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.