![]() ![]() Go to Mod Manager's "Show Settings," where it should trigger the debug log error.Įven running just Core, Royalty, Harmony, HugsLib, and Mod Manager lets me reproduce the error on my end. Colony Manager allows you to make colonists do the more tedious parts of managing a colony, making sure youre never out of vital resources again.Right after freshly loading the game (not clicking "Mods" first since doing that prevents the problem somehow), go to "Options".Color a mod and then quit to OS, and start the game up again.It also doesn't happen when I haven't changed any mod's color yet.Īll my 250 mods retain the colors I assigned them through my unhealthy display of OCD. As creating mod lists for importing mods is IMO Mod Manager's single most important feature, In 1.4 it is unusable to me. It doesn't happen when "Mods" in the main menu had been opened prior, only when going straight Options > Mod Settings > Mod Manager's Show Settings after freshly loading the game. This mod is nightmare-level buggy in this iteration Among other things that plague it for ages, in 1.4 it saves mod lists only partially while randomly removing mods from them upon list load. It has a wide reaching selection of features: sorting mods, searching mod files, downloading mods through steamCMD, coloring mods, exporting mod packs, optimizing. It has some great features that streamline the process of modding the game. ![]() The debug log triggered after checking Mod Manager's settings from "Mod Settings" inside "Options." Then, all settings and mod colors saved by Mod Manager had reverted to default values (all mods are white again). What is RimPy: RimPy is an application made in Python to assist in setting up mods for RimWorld externally. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |