Unfortunately, there was no reliable fix for Legacy. A few days later, a new renewed version that mandated the use of this Forge version was released, fixing the vulnerability once and for all. Soon thereafter, the Minecraft Forge team released a fix for Forge for Minecraft 1.16.5 (version 1.16.5-36.2.20), and the current release of Renewed worked on it no problem. The move to 1.16 was justified, for in late December 2021, a security hole (Log4J) was discovered in Minecraft. ![]() Furthermore, the code changes between 1.15 and 1.16 were expected to be minor (in reality, they were quite major), so updating to future versions of Minecraft may be easier. In a nutshell, the mod is being updated to 1.15 because it currently runs on a version of Minecraft that dates back to mid-2014, for which Forge has long since ended support, and which may therefore stop working at some point for reasons beyond our control (though we do hope not). That, and some newfound appreciation for the newer versions. Luckily I managed to fix them by updating to newer versions of the support software, but it did make me think about what would happen if support for some aspect of 1.7.10 forge/gradle were ever withdrawn in a way that wasn't fixable. However, in 2020, he changed his mind on the matter, as seen in a comment on the mod's Facebook page when asked why he moved to 1.15:Ī few mishaps with 1.7.10 forge/gradle which temporarily made it impossible to build the mod, and had us worried that it might spell the end of development for the mod. 4 Will it be compatible with 1.7.10 worlds?įor many long years, Mevans, the developer of the mod, had been reluctant to move the mod to a newer version of Minecraft, as seen in a blog post in 2015, and his long-running forum thread.3 What gameplay features will be added?.2 Why does it take so long to update the mod?.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |