Modded Minecraft Basics: Difference between revisions
→A Brief History of Modded MC: The 1.8 debacle.
m (→M: mixin) |
(→A Brief History of Modded MC: The 1.8 debacle.) |
||
Line 37:
One of the new problems that arose from this new frontier was a duplication of content. Many large mods added new ores, ingots and other resources to vanilla, but wouldn't be capable of using another mod's version. Understandably having four different copper or tin ingots was not only a headache for players (which of these did I need to make the wrench again?) but a problem with world generation too, as it could make resources far too abundant. Ore Dictionary was Forge's solution to this, both a backend API and several in-game items[https://ftbwiki.org/Forge_Lexicon_(OmniTools)] that allowed manual conversion or behaved as a universal tool. A similar classification system was eventually folded into vanilla as Tags in 1.13 [https://minecraft.wiki/w/Tag]. A new age of modding rode in with 1.4, one where modpacks proliferated, and became increasingly bigger, more complex and better integrated. Version clumping became more noticeable - mods and modpacks began to cluster around specific versions of MC, including 1.7.10. This was often prompted by either a longer-than-usual delay between vanilla releases or a disastrous release that broke major parts of the game, such as 1.8.
So many mods and modpacks cluster around 1.7.10 because Minecraft 1.8 fundamentally changed how block rendering and coordinates were handled by the base game. Each block now required an individual file for each state it could be in; for blocks that previously updated dynamically to react to their contents (like tanks and pipes) this resulted in an astronomical number of permutations that were simply not viable to build and ship. This killed a lot of development inertia and stagnated the modding community as many beloved mods simply could not be updated or were abandoned. Pack makers had to choose between staying on 1.7.10 or give up the last viable version of a core mod for their projects - most chose to stick with 1.7.10. With no modding API and frequent codebase rewrites, official versions break mods regularly like 1.8 did, making modders justifiably reluctant to update their work to the most recent version when it's going to be made useless in short order.
This is one of the main reasons why GT:NH isn't updated for modern MC, and has no plans to do so - the base game is so fundamentally different it would require reworking the last decade of code from the ground up, for minimal improvements and a massive loss of familiarity with the current codebase. Instead the opposite approach has been taken; pulling features and mods from modern builds and backporting them to 1.7.10, which is how GT:NH runs on modern Java and has features that were not historically available at the time.
* [https://hub.packtpub.com/brief-history-minecraft-modding/ A Brief History of Minecraft Modding - Packt]
Line 42 ⟶ 46:
* [https://www.reddit.com/r/feedthebeast/comments/i91rfa/history_of_modded_minecraft/ History of Modded Minecraft - Reddit]
* [https://www.youtube.com/watch?v=GuOyXgxAjys Mods that Changed Minecraft Forever - YouTube]
* [https://www.youtube.com/watch?v=OvKx0zOCNEo The Day Modded Minecraft Almost Died]
== Instances ==
| |||