
The first snapshot of the year 2025 is here. We are entering it strong with support for the latest Minecraft version and many new interesting features!
3 Minecraft versions?
As we often do when porting to a new Minecraft version, the 1st MCreator 2025.1 snapshot supports Minecraft 1.20.1, Minecraft 1.21.1, and Minecraft 1.21.4 at the same time. In the next snapshots and in the full release, we will only support two versions.
Minecraft 1.21.4 tags warning
Starting Minecraft 1.21.4, tags are much more sensitive. Referencing tags that don't exist in your workspace (e.g. from external mods) will cause the game to crash. Similarly, tags that reference elements from another mod and if those elements don't exist, such tag will not load. In practice, this means that mods may need to have the mod your mod is extending present in the development environment too. To do that, you can put additional mods into run/mods folder.
What about Minecraft 1.20.1?
Full versions of MCreator only support two versions. This time, we have decided to drop support for 1.20.1 in the full release. While the snapshot still supports it, the full release won't.
The reason for this is that later versions contain functionality and systems that allow us to add new features that won't work in 1.20.1. This means such features can't be added until we don't drop the support for older versions. Another reason is that we can't fully properly maintain that many versions at once with the current developer resources.
The good news for all modders who want to stay on 1.20.1 is that we will provide an official plugin for Minecraft 1.20.1 for MCreator 2025.1!
Snapshot changelog
This is a full changelog of this snapshot with more notable changes highlighted with bold text.
- Updated bundled Java to version OpenJDK 21.0.5
- Updated NeoForge for 1.21.1 to 21.1.92
- Added user code block to access transformer files
- Added option to edit ordering of certain entry lists in the software
- Added some new tags to the add common tags tool
- Improved performance and reliability of Gradle project loading
- Added support for multiline procedure-based tooltips in custom GUIs
- Added a context menu item to the Blockly editor to clean up unused blocks
- Added option to make both opaque and translucent particle types have emissive light rendering
- Greatly improved procedure mod element generated code clarity and performance
- Added Minecraft resource pack generator for 1.21.4
- Added base support for NeoForge 1.21.4
- Added Minecraft data pack generator base for 1.21.4
- [A 1.21.x] Added new Minecraft blocks, items, and entities to data lists
- [DP 1.21.4] Added support for: functions, damage types, loot tables, tags, structures, advancements, advancement triggers, recipes, enchantments, dimensions, biomes, worldgen features
- [NF 1.21.4] Added support for: custom code, functions, damage types, loot tables, tags, structures, sounds, advancements, advancement triggers, recipes, enchantments, villager trades, biomes, paintings, game rules, attributes, potion items, villager professions, variables, global triggers, commands, worldgen features, key bindings, creative tabs, armor, JSON models, Java models, OBJ models, item extensions, dimensions, particles, overlays, GUIs, projectiles, living entities, AI tasks, Java animations, tools, potion effects, blocks, fluids, plants, procedures, items
- [NF 1.21.4] Custom projectile Java models now support basic animations
- [Bugfix, A 1.21.x] Custom blocks did not load correctly in some cases
- [Bugfix, A 1.21.x] Custom blocks did not appear in the creative mode item selector
- [Bugfix] On 4K screens, MCreator window size was not correct for list elements in some cases
- [Bugfix] Old mods.toml and mcmod.info files were not removed when switching to the NeoForge generator
- [Bugfix] Sprite GUI mod element component with equal width and height could glitch the UI editor
- [Bugfix] Filter in resource pack editor file browser stopped working in some cases
- [Bugfix] Projectiles with non-default bounding box size did not collide correctly in some cases
- [Bugfix] It was possible to import armor textures with an empty name
- [Bugfix] Some other minor fixes and improvements
Snapshot release notes
- Removed "at every position carved by carvers" placement. Existing uses of this placement in feature mod elements will be converted to "with uniform height distribution" placement.
- Removed lit particle type. Instead, there is now a checkbox to allow any particle type to have emissive light rendering. Existing particle mod elements will be converted automatically.
- Cured by milk and by totem potion effect properties were removed and are now always enabled by default
- Get fuel power of item procedure block now requires world dependency
- Enchantability can no longer be 0 for armor and tools. Existing elements will have 0 values converted to 1 automatically.
- [1.21.4] Certain procedure triggers and procedure blocks now only run on the server side
A download of the snapshot is possible on the Download page under the Snapshot downloads section.
Make sure to test the snapshot out so we can fix any potential bugs you find out. Leave a comment with your feedback on the update below. Stay tuned and keep on modding!
Comments
MCreator, I beg of you, please fix (or help me to figure out what I am doing wrong) the biome glitch! I try to make a new biome in the Nether, Overworld, and Cavea, PLUS my custom dimensions, but only one generates! Also, an End Biome generator would be awesome, thank you! And, when will Forge go to 1.21.4?
To fix the biomes, please see https://mcreator.net/wiki/how-make-biome#toc-index-8. We can't fix this because this is the new de-facto system in the game itself, you just need to make sure to use it correctly. Overlapping biome parameter points will result in only one of the overlapping biomes to generate.
And thus, the wheel of progress leaves me in the dust again..
I do hope that some people port some of the newer features to versions with 1.20.1, and/or there is a place I'm able to ask questions for that version without being stonewalled like I've seen happen to many of the questions I look up on here.
But the main issue is how it's just a stone wall of "This version is not supported"
This is software, not a game. It's reasonable to assume that people may stick behind to lower versions due to it accommodating to their needs more, or the mods that are available on the version they're on, or not wanting to deal with the issues that may arise while porting to a newer version. (which is admittedly a lot more minimal with newer updates)
I'm glad you stuck with 1.20.1 for the time you did. but the constant blind march of progress is just, tedious to keep up with, especially as someone who works on a longer term mod instead of intermittent small-medium projects.
Since we can't maintain all the versions going back with the growing list of "old versions" every time a new one pops out, this is not feasible. This is why plugins were added, so the community can develop plugins for older versions if there is an incentive. Bear in mind MCreator is an open-source community project, so how much we can support and develop relies heavily on how much support there is from the community in all shapes and forms
good morning my dear friends, I would just like to say before moving to the final 2025.1 version, that it seems to me that the option of create plant is broken, (when it comes to aquatic plants), someone can tell me if they noticed this too or it's just me who can't use the program (it can be too)
Hey MCreator devs, could you please add the ability to have sprites, and not just images, at 1x scale and not just 2x?