Topic category: Help with MCreator software
Hi Folks,
in my free time, I‘m working with MCreator 2022.1 on a Minecraft: Java Edition Mod for the MCreator x CurseForge ModJam. I’ve already published my mod for 1.16.5, 1.17.1 and 1.18.2, and I also want to publish the mod for 1.14.4 that users with older PC hardware where the newest Minecraft versions won‘t run can play my mod. For the 1.14.4 generator, I used @Klemen‘s plugin and I changed some things that the plugin does also work with MCreator 2022.1. Then, I‘ve exported a .zip file from my workspace and after importing it, I clicked on the workspace settings symbol and changed the mod generator from Minecraft Forge 1.18.2-40.0.24 to Minecraft Forge 1.14.4-28.2.26. But then, some errors are occurring in the 1.14.4 workspace and I can‘t fix most of them because I‘m not good in Java. I hope that I can find someone here for helping me with my 1.14.4 workspace in MCreator 2022.1. I‘m going to work on the workspace today at 12.30 p.m. If this topic isn‘t in the right forum, please move it to the right forum!
Sincerely yours,
Atten007😊
I assume this may be happening because you can't use newer features for older generators. So if you used even one feature that wasn't available on 2020.5 (the last one 1.14.4 generator was fully working for), then your Gradle can return errors.
Hi @Toma400,
yes, my gradle is returning errors! For example, when I‘m creating a new workspace in MCreator 2022.1.12711 and adding a biome with the both TestBlock1 and the TestBlock2 to it, my gradle returns the error „Package TestBlock1 couldn’t be found“. This is really annoying and I found out, that I can fix this by modifying the biome.definition.yaml file, but I also found out that the 1.14.4 generator saves some of the mod elements to the /MCreatorWorkspaces/Workspacename/elements/ folder and not to the right folder /MCreatorWorkspaces/Workspacename/src/main/net/MCreator/Modname/Type and this lets occur the „Package TestBlock1 couldn’t be found“ error. How can I fix this and how can I make it so that MCreator 2022.1 saves and moves all the mod elements from the /Elements/ folder to the/src/Main/net/MCreator/Modname/Type folder?
Sincerely yours,
Atten007😊
It may be nice when I can have a instruction for this because I also want to publish my mod „Envirocraft“ for Minecraft Forge 1.14.4.
And when I‘m choosing the 1.12.2-14.23.5.2855 generator, the same errors are occurring when my mod is compiling...
Well, if I have to be honest, I'm afraid you may have chosen wrong way to use 1.14 (and 1.12 now) plugins.
I mean, MCR has changed quite a lot since 2021.1 snapshot (version for which 1.14 generator was made for) and there's probably way more things to change in generator to make it run for 2022.1, than only requirements for version. Well, it may be even impossible, since 2022.1 uses totally different Java which is not supported by neither 1.12 nor 1.14.
This is one of the answers why MCreator does not support these versions of Minecraft anymore, even in passive meaning of support.
Not sure what to tell you - I have literally no clue how to handle this, or if this is even possible. If I want to have mod for several versions, I usually start from lowest MCreator version (in case of 1.14: 2020.5) and after making complete mod, I just copy workspace and update it to higher versions, fixing things that may have errors. Support for 1.14 is quite tough anyway, though.
Yes, but I want to make the mod for different Minecraft versions with the most recent Mcreator version 2022.1. But after changing to the right folder, the same errors are still occurring… and this makes me very angry when I’m working with Mcreator…😡🤬
I understand you. I'm just stating that this is not really a possible thing. And errors are obvious outcome, as I explained earlier.
Yes, that’s right… I’m trying it with 2020.6…
How do you have MCreator in 1.18.2? If I have the one in 1.17 and 1.16.5, what do I do to have the 1.18.2?