Topic category: Feature requests and ideas for MCreator
TLDR: If I set my Workspace Prefernces > Mod Version to something like “1.0.0-beta1” it says “1.0.01” in Minecraft and I don’t think that makes sense.
An explanation of the problem:
In MCreator, you cannot set a mod or addon (idk about resource/data packs) version to something with a letter in it and have it keep that. Just to be clear, it’ll stay there in the MCreator GUI, but, when MCreator generates the mod code, the letters get stripped meaning that they don’t show in game. This is very annoying for beta versions, where I don’t want to have to settle for entering “1.3.0.beta1” and getting “1.3.0.1” in Minecraft when what I wanted to make in the first place was “1.3.0-beta1”.
It’s been like this for a while:
Back in late 2020 to early 2021 when I first started using MCreator and knew incredibly little about Minecraft modding, I tried making a mod with a versioning system something like (I don’t fully rmember back to then) where the last letter would represent the beta. (Ex. 1.0.0a is the first beta, 1.0.0e is the fifth, 1.0.0 is the full release) and found out that in the game, the letters get striped out to always just say “1.0.0”.
It still happens:
As of 2025.3 w/ NeoForge 1.21.8, it’s still the same and it’s not in the 2026.1 changelog as changed. Honestly, I’m just curious what the reasoning behind this restriction is because I feel it to be so arbitrary.
This is by design of mod loader. I recommend investigating this page: https://docs.neoforged.net/docs/gettingstarted/versioning/
I understand the practicality of SemVer. Almost all my projects have used a version of it. However, I think it makes less intuitive to make “1.3.0.1” or “1.3.0” show up as the version for the 1st beta build for 1.3.0, when you could have “1.3.0-beta1”.
I did read through the NeoForge documentation you provided and it doesn’t seem to explain to me why having version text suffixes is necessarily a problem. It does even provide an example in the Extended SemVer section of Create using a letter in it’s version as a hotfix: 0.5.1f.
I understand for newer users, it may be simpler to absolutely force a (admittedly quite good) recommended versioning system, but I don’t see why more experienced users shouldn’t be allowed to put “1.8.0-beta” or something like that in their versions.
If someone is interested in adding support for those edge cases, PR is welcome.
However we need to be carefuly as NF is very picky and restrictions were imposed because games were crashing due to users using incompatible version numbers