Workspace is not being Imported 1.8.0 --> 1.8.1

Not applicable
Issue description

Hey, When I Import my big mod Workspace, it is stuck on Loading Mods

Please help!

Issue comments

I will most likely release a hotfix for 1.8.1. The workspace you provided is severely corrupted. I will try to make MCreator able to import such workspaces but keep in mind that some mod elements and/or their settings might not get imported.

I would suggest you to try to export the workspace again and to try to import it again for the first attempt to fix this.

I will try export some workspace and import them, if it still don't work what do I do?

Also if the Workspace is corrupted, can you un-corrupt it?

No, you can un-corrupt it, but I am working on making MCreator handle what has been left of the workspace. In your case, just some definitions are missing.

If exporting again won't help, I will release a patch update for 1.8.1 with a fix for this bug.

Ok How to un-corrupt it?

Definitions missings to be added, Sorry if I ask you too many question but you are the only person that have answers to all MCreator problems


Well you are the best Dev/Moderator/Owner existing! Continue to do great job! :D

I told you can't uncorrupt it. I will try to make MCreator accept your workspace and make it usable when importing and release a patch for this. Stay tuned as I will notify you here when the patch is ready.

I said you could try to export it again, this time uncorrupted, but if the workspace is corrupted before the export process starts, this can't help. I have managed to improve importer to handle your workspace and properly import it. After I do some testing I will release patch and notify you and you will be able to import your workspace :)

I have released a patch that supports corrupted workspaces like yours and imports them.

UPDATE (7.11. 19:47 CET)

We have released a patch update which fixes some minor bugs, improves import compatibility for broken workspaces and adds some minor UI improvements. If you would like to have these improvements and have downloaded MCreator 1.8.1 before this notice was posted, you can download and install MCreator again to get them. If you downloaded MCreator after the time of this notice, you don't have to do anything.

Good Job, The Mod Loading can be done but still a little problem, All my Textures are imported properly but I have only 233/883

Mod Element that has been imported... that's a problematic because only my 233 mod elements were made on MCreator for 1.11.2 and the remaining in 1.8.0... Well then I return back on MCreator 1.8.0 to Export Workspace again and it said someone new

Gradle Task Fail With this console report

Executing gradle command: clean build
Build info: MCreator 1.8.0, 64-bit, 8061 MB, Windows 10, JVM 1.8.0_172
C:\Pylo\MCreator180\forge>gradlew -Dorg.gradle.daemon=false -Dorg.gradle.parallel=false -Dorg.gradle.jvmargs="-Xms625m -Xmx2048m" clean build 
Etag download for fa…
Etag download for failed with code 400
FAILURE: Build failed with an exception.
* Where:
Build file 'C:\Pylo\MCreator180\forge\build.gradle' line: 10
* What went wrong:
A problem occurred evaluating root project 'forge'.
> Failed to apply plugin [id 'net.minecraftforge.gradle.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.
Total time: 9.609 secs
Task completed with return code 0 in 10407 milliseconds

I don't understand this Problem... I don't to recreate allllll my procedures and recipes and other items and blocks

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.