In the world of software management there exists a dreaded place called “dependency hell.” The bigger your system grows and the more packages you integrate into your software, the more likely you are to find yourself, one day, in this pit of despair. It would be easier, if you could define all or some versions of the containing mods of a modpack and be able to revert the mods to its original versions. Seablock is a very popular example and the old big seablock forum thread viewtopic.php?f=190&t=43759 was full of problems, because people installed the pack with not matching versions of the mods.Ĭurrently its easier to provide a big zip file of mods as modpack Often some mod changes, do some experimental changes or introduce a new bug and then the modpack is broken, if you install the latest versions. If you have a big modpack with dozens or hundeds of mods, its very hard to distribute a working compilation.

This would imply, that all mods had to follow those principle, which seems a bit unrealistic, but that could be established. This should not replace the current functionality, because you sometimes want the latest version and not the original version.Īdditionally, as ssilk proposed, you could consider npm standards for “backward compatible bug fixes”, which can be installed safely instead of the original mod version. Here, you should alternatively be able to resync all (or some) mods to the original versions of the savefile. So the savefile can act as modpack, but it always installs the newest version or keeps the currently installed version, no matter if the version in the savefile is different. If you have a savefile, you are already able to sync to the mod selection of the savefile. Not sure, if something would have to be done here. However, the modpack mod does not need to be correct, because the containing mods work for themselves. Note: the Modpack mod is red in this case, because the dependencies are not correct, because the fixed dependency is not fulfilled.

via an additional button in Mods -> Manage screen for the modpack mod. If you have a newer version of the mods installed, you should also have the ability to revert the modpack to the original mod versions. If you install the modpack mod, the specific version of the dependency mod should get installed instead of the newest version. Code: Select all ScienceCostTweakerM = 1.1.1

Factorio latest version modpacks