I fully understand that it's not an easy work to develop such a powerful and advanced mod, but, as a mod developer who is in in charge of Mekanism-Extra mod, as well as many other developers, met a trouble during coding.
I wanna add more tiers, chemical types, language, ores and so on. Unfortunately, every class in Melanism code is like enum (e.g. mekanism.api.chemical.ChemicalType) or even just an enum (e.g. mekanism.common.resource.OreTypemekanism.common.resource.OreBlockType
). This gives me lots of trouble since i can't keep the same with mekanism easily. So I sincerely hope that you can avoid or even stop using enums to give other developers more convenience.
Steps to reproduce
No response
Minecraft version
1.20.x or earlier (No longer being developed)
NeoForge version
47.2.32
Mekanism version
Older
Other relevant versions
No response
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
Issue description
I fully understand that it's not an easy work to develop such a powerful and advanced mod, but, as a mod developer who is in in charge of Mekanism-Extra mod, as well as many other developers, met a trouble during coding. I wanna add more tiers, chemical types, language, ores and so on. Unfortunately, every class in Melanism code is like enum (e.g.
mekanism.api.chemical.ChemicalType) or even just an enum (e.g.mekanism.common.resource.OreTypemekanism.common.resource.OreBlockType). This gives me lots of trouble since i can't keep the same with mekanism easily. So I sincerely hope that you can avoid or even stop using enums to give other developers more convenience.Steps to reproduce
No response
Minecraft version
1.20.x or earlier (No longer being developed)
NeoForge version
47.2.32
Mekanism version
Older
Other relevant versions
No response
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
No response