

When Forge reimplemented this, modding under 1.8 become much easier, so slowly people started moving over and you had a steady supply of mods building up for 1.8+. In the beginning, Forge was hesitant to do anything about this, and kept telling developers to just use Mojang's system, but eventually they realised just how bad the situation was and reimplemented the dynamic model factories that 1.7.10 and previous used. 1.8's model format was horrendous, many mods required hundreds, if not thousands of JSON files just for simple block and item models, and larger mods with complex model factories, like Buildcraft, would have been inflated to tens of gigabytes in size due to how many JSON files were required. The problem with 1.8 primarily was the new model format. Cross-mod interaction and the ability to modify mods bloomed under 1.7.10, which is what caused the surge in mod packs for 1.7.10.


This lead to the modding ecosystem to mature a whole lot, causing 1.7.10 to become possibly the most stable modding experience in Minecraft's history. (#spoiler) = neat! (/rose) = ( full list)ĭue to the controversy surrounding 1.8 in regards to modding, many developers refused to update to 1.8 and instead stuck with 1.7.10, which caused 1.7.10 to stick around as a relevant version for modding for far longer than usual. News Builds Gameplay Maps Tutorials Redstone Command Blocks FanArt Comment Formatting Use the wiki or community support for questions that can be answered there.Explain your suggestions with a text post.Don't promote illegal or unethical practices.Don’t advertise servers or communities.Trails & Tales 1.20 FAQ | Login/Stolen Account Problems | Technical Problems On /r/Minecraft
