Minecraft Forge 1.19.2 Java Edition/Datapack Generator

Published by _Spectrall on
Supported MCreator versions
2023.3
2023.4
2024.1
2024.2
Tags / plugin type
Generator
Minecraft Forge 1.19.2 Java Edition/Datapack Generator
Downloads:
8718
Upvotes: 47
About the plugin

 

MCreator generator plugin for Minecraft Forge 1.19.2 Java Edition mods/Datapack.

How to install

Please check https://mcreator.net/wiki/understand-plugins#toc-index-1 for installation guide.

Info

This Generator is built over the old official generator, but this one is NOT official, and is not being maintained by the MCreator Team.

 

NOTE: 

  • From MCreator 2024.2 the folders where the textures are contained have changed: Blocks -> Block, Items -> Item, this change is necessary to have the functionality to refer to vanilla Minecraft textures

More documentation on generators

Check MCreator's wiki for more documentation: How to make new generator

My Other Generators:

- Minecraft Forge 1.12.2 Java Edition Generator

- Minecraft Forge 1.14.4 Java Edition/Datapack Generator

- Minecraft Forge 1.15.2 Java Edition/Datapack Generator

- Minecraft Forge 1.16.5 Java Edition/Datapack Generator

- Minecraft Forge 1.17.1 Java Edition/Datapack Generator

- Minecraft Forge 1.18.2 Java Edition/Datapack Generator

- Minecraft Forge 1.19.4 Java Edition/Datapack Generator

- Minecraft NeoForge 1.20.4 Java Edition/Datapack Generator

My Other Plugin:

- Shaders Utils

Why should i use this generator?

If you are using this version of minecraft, you will have many more features than those present in MCreator 2023.2, the generator will have full support so if there are any bugs they will be fixed etc. (unlike 2023.2 which is no longer supported). The generator also has a lot of backports (from new versions of MCreator to this one) regarding bug fixes on the generator. If you want to export your mod for multiple versions this generator is for you!

Contributing

You are welcome to support this project by opening pull requests.

Changelog

NOTE: Plugin versions that use versions older than MCreator 2024.2 will no longer be supported

V1.5.2 - 1.19.2 (2024.2)

- Bug Fix (Custom Tabs were ignored)

V1.5.1 - 1.19.2 (2024.2)

- Bug Fix

V1.5 - 1.19.2 (2024.2)

- MCreator 2024.2 Support!

- FG Bump

- Bug Fixes

- Improvements

V1.4.3 - 1.19.2 (2024.1)

- Bug Fix

V1.3.5 - 1.19.2 (2023.4)

- Bug Fix

V1.0.6 - 1.19.2 (2023.3)

- FG (Forge) Bump

Project members
Lead developer
License
GNU General Public License version 3 (GPLv3)

Plugin downloads
V1.0.6 - 1.19.2 (2023.3) [Latest for MCreator 2023.3] - generator-1.19.2-1.0.6-2023.3.zip Uploaded on: 10/05/2023 - 14:23   File size: 668.8 KB
V1.3.5 - 1.19.2 (2023.4) [Latest for MCreator 2023.4] - generator-1.19.2-1.3.5-2023.4.zip Uploaded on: 04/12/2024 - 16:57   File size: 687.63 KB
V1.4.3 - 1.19.2 (2024.1) [Latest for MCreator 2024.1] - generator-1.19.2-1.4.3-2024.1.zip Uploaded on: 05/14/2024 - 13:44   File size: 658.01 KB
V1.5.2 - 1.19.2 (2024.2) [Latest for MCreator 2024.2] [Recommended] - generator-1.19.2-1.5.2-2024.2.zip Uploaded on: 07/25/2024 - 18:58   File size: 732.4 KB

Comments

When compiling it says [ModName]ModBiome doesn't exist and proceeds to not let me fix it.

error MCreatorWorkspaces\faraway_additions\src\main\java\net\mcreator\farawayadditions\FarawayAdditionsMod.java:64: error: package FarawayAdditionsModBiomes does not exist
FarawayAdditionsModBiomes.REGISTRY.register(bus);

can you load the old version 2023.2 for 1.19.2 please. Unfortunately, I don’t see this extension for this version

Hi ! So the generator had an issue in 2023.4 generating the init > ModEntities files and some other init stuff. From my testing it was sucessfully fixed, but it's still bugged for the ModBiomes file, with the same issue (file not generating)

I confirm this bug, but I have no idea how to fix it, from what I've noticed it seems to depend on MCreator and not on the plugin (since the files don't give errors), it happened to me when I brought the workspace I use to test the my generators to 1.19.2, then by porting it to another version and subsequently again to 1.19.2 the bug was resolved (this is why I assume that it is not linked to the plugin)