![]() Bees and their hives can be found in Middle-earth.Most of the content in 1.16 and earlier post-1.7 versions will be present in some form in the mod. Updating this mod will follow much the same path as the mod's initial creation, but will proceed considerably faster. ![]() Again, we cannot overemphasise how complex some parts of this mod are, and how many areas of the game it interfaces with. Attempting to directly update the whole codebase would mean fixing hundreds of thousands (yes!) of compile errors before the mod could even start, let alone checking for bugs. Furthermore, this mod interfaces with almost all parts of the game, in many complex ways. As has been said a lot over the past few years, updating it to a newer version is no small or easy task. However this does mean that adding a new Block or Item, for instance, shares nothing in common with the respective 1.7.10 code.Īnd the Lord of the Rings Mod is an enormous mod. Most of these are for the best - it is much cleaner codebase. Since 1.7.10, the changes to the game's code have been enormous and far-reaching, some rewriting the very deepest of its workings. In case anybody is curious, the estimations made for the Mod to be translated 1:1 would be about 4 Lord of the Rings trilogies worth of characters, but then all of it is math equations, and if 1 answer is wrong, the entire thing fails.Īnd then imagine you are basically translating math homework worth of 4 LOTR collections, which you have already made once. The entire workings of the mod are essentially nothing more than a giant set of mathematical equations. Why does it take so long to update the mod? While it is possible that a third-party mod will be released that patches the security issue in 1.7.10, it is not a given, so players have been urged to stay off Legacy servers for the time being. Forge stated they do not intend to fix this version, because the fix they were able to apply to 1.18 down to 1.12 would not work for 1.7-1.11, 1.7.10 has been unsupported for years now. Server owners were advised to shut down their severs immediately (even private ones), else they ran a serious risk of having the host machine hacked. Therefore, players were advised against connecting to any Legacy LOTR Mod servers, else they ran the risk of having their computer hacked, personal details stolen, and worse. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |