Disable forge version limit

From 1.8.2 changelog:

• Added Minecraft Forge with version tag as mod dependency when exporting

In MCreator 1.8.2 we have added Minecraft Forge version tag as a dependency as many users used MCreator with different versions Minecraft Forge than with the one MCreator used to compile mods. This caused many crashes and errors due to version mismatches. We added this dependency to resolve this issue.

MCreator uses Minecraft Forge 2768 from version 1.8.1 onwards (https://mcreator.net/changelog). We always use the latest recommended version by the Minecraft Forge developers which is 2768 at the time of writing (http://files.minecraftforge.net/).

We could add an option to exclude this requirement in 1.8.3, but if there is not enough demand we prefer not to for the reasons given above.

We had a good reason to do this, as we got way too many bug reports with crashes related to Forge incompatibility.

If your other mods don't support this version, they are the same part of the issue as MCreator mods.

There is no option to disable this check in 1.8.2, at least not a simple way. You can do this manually, though.

You only need to do this when you want to export your mod:

One way is to change this part of the code from file forge\src\main\java\mod\mcreator\yourmodid .java (replace yourmodid with your actual modid):

@Mod(modid = yourmodid.MODID, version = yourmodid.VERSION, dependencies = "required-after:forge@[14.23.5.2768]")

to

@Mod(modid = yourmodid.MODID, version = yourmodid.VERSION)

Then you need to run build without MCreator overwriting your files, which you do by going to console tab and pressing console icon in the toolbar (below gears icon). When a popup opens, leave default option (build) and press OK. Wait for Gradle to build your customized code. If you would just recompile the mod, MCreator would overwrite your change, so you need to run manual gradle build as instructed above.

After the build is complete, go to forge\build\libs  and copy file modid-1.0.jar somewhere else and rename it to the desired jar name of your manually exported mod.

We will consider adding an option to do this from inside MCreator in workspace settings.

We will add an option to disable this check in MCreator 1.8.3 in workspace settings. I am closing this ticket.

You have a workaround written a few lines above. If you don't understand it, you are better off using default settings as we won't give you any support if you decide to use unsupported forge versions.

MCreator 1.8.3 will support this without changing the code. And if you don't understand the code you shouldn't be changing this anyways most likely.