
ConfigManager not initialized before calls that use settings
bmwalter68 opened this issue ยท 0 comments
In the mod preInit ConfigHandler.init() is called after Mods.init() and VersionChecker.execute(), both of which allow overriding their settings. Always checking for new versions isn't terrible, but RR defaults to using FMP relocators if FMP is installed, which breaks worlds that added FMP after installing RR. (See issues #287, #215, #145)
Confirmed by rolling my own custom build that moving the ConfigHandler.init() call before Mods.init() and VersionChecker.execute() the defaults can be overridden and I can load my worlds where FMP was installed after RR.
As an aside, I noticed that the last few versions have internally been identified as 1.1.21 even though the jar is named as 1.1.25... Something may have gone sideways in your build.gradle
Thanks for RR!