ebkr
[FEATURE REQUEST] - Binary Search for Debugging
The Problem
You just spent a couple of hours compiling your 150-strong modlist for Risk of Rain 2, and you're ready to play. Unfortunately, you launch the game, and it fails to boot to the menu. This sucks. How do you remedy this?
The Solution
A binary search will solve your problem. Disable half of the mods and check to see if the issue is still present. If the issue is still present, repeat the process on the currently enabled mods. If it isn't, repeat the process on the disabled mods. Do this until you find what specific mod is causing the problem.
The Problem with the Solution
Manual binary searches suck.
- Large modlists mean you're taking several minutes just to enable or disable individual mods.
- Large modlists can take a long time to boot, meaning each test takes a certain amount of time to run.
- Keeping track of which mods you have and have not tested is a nightmare.
- Deciding which "half" of the mods to test is rather difficult when you have to worry about dependencies - and makes keeping track of these things all the more cumbersome.
This is something a computer should be able to help with.
My Suggestion
Implement an assisted binary search, similar to git bisect. Let the mod manager disable half of the mods for you, and launch the game for you to test. When you're done testing, you report if the error is still present, and the manager will enable and disable mods accordingly, keeping track of what has and hasn't been tested in order to make the process vastly more efficient.
