You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem description
Something I find myself doing annoyingly-often, as a large-modlist player, is manually preforming a binary-search through the active mods, in an attempt to determine which one is {slow,bugged,incompatible}.
A huge, huge quality-of-life boost would be if I could do this inside Rimworld, without exporting the modlist to a file, manually commenting-out half of the YAML, loading that modlist … export, comment-or-uncomment half of that half … rinse, wash, repeat.
Describe the solution
I'd love to see the Mod Manager include a feature a bit like git bisect, though simplified:
Button to "Enable Bisection-Debugging"
Bottom half of the modlist is disabled
Pop-up informs user, asks them to start a game / load a save, determine if the bug/slowdown is still occurring
Next time Mod Manager is opened, pop-up asks them whether bug/slowdown still occured, with the options:
A. "Problem disappeared" - tell user you're re-enabling half of the remaining modlist, mark all the previously-still-enabled mods as 'not-the-cause'
B. "Problem still occurring" - tell user you're disabling half of the remaining modlist; mark all the previously-disabled mods as 'not-the-cause'
Highlight all 'not-the-cause' mods in green in the modlist, return to 2
The text was updated successfully, but these errors were encountered:
Problem description
Something I find myself doing annoyingly-often, as a large-modlist player, is manually preforming a binary-search through the active mods, in an attempt to determine which one is {slow,bugged,incompatible}.
A huge, huge quality-of-life boost would be if I could do this inside Rimworld, without exporting the modlist to a file, manually commenting-out half of the YAML, loading that modlist … export, comment-or-uncomment half of that half … rinse, wash, repeat.
Describe the solution
I'd love to see the Mod Manager include a feature a bit like
git bisect
, though simplified:A. "Problem disappeared" - tell user you're re-enabling half of the remaining modlist, mark all the previously-still-enabled mods as 'not-the-cause'
B. "Problem still occurring" - tell user you're disabling half of the remaining modlist; mark all the previously-disabled mods as 'not-the-cause'
The text was updated successfully, but these errors were encountered: