Automatic binary exclusion method

Origin of idea

Personal experience of using AutoIt and understanding that the process of binary excluding method could be automated.

Suggestion/proposed solution?

Community would greatly benefit from some form of (automatic, ideally) binary exclusion method. When the game starts, it waits for a log to be shown. Ctrl+F12 to get logs if needed, then exit from the game → then RimSort asks were there any errors. If yes, then it turns off half of mods (or mod groups one by one that a logically connected depending on what they mod in the game), then asks again was the problem fixed or not (yes, no; the previous problem was solved, but another one happened). If the problem was solved → profit, it could filter it further finding that one that causes problems. If not, it runs another pack of mods, asks again, allows to copy-paste logs in every iteration to further investigation.

Would be supercool, if having this functionality could be automated with software like AutoIt (it allows making screenshots, copying text, clicking in a specific screen locations where you see a particluar image, like a button, and whatnot). So, in the end user could run it, come back after hour and get a fully working game knowing what mod caused the problem. With such automation it could go even further and try to generate a world, a map, waiting for errors on these steps.

Sounds too good you may think, but it's actually doable and not some kind of voodoo magic. I have automated many stuff with it in pretty complex programs. For example, you can simulate clicking mouse in a specific part of a screen just by having a small screenshot of how that button, let's say, should look like.

By the end of a day, it could even add a rule to the base when some problematic modconfig pattern shows itself.

Would donate real money if such feature is made.

To go even further, there could be a mod that gathers needed data specifically for RimSort, so when the game closes RimSort would know all the paths for logs, no need for uploading.

Alternatives considered

Doing all this by hand is crazy, especially with huge modlists. You have to remember what you have excluded the last time etc.

Additional context

No response

Code of Conduct

I agree to follow this project's Code of Conduct

Duplicate Issue Check

I've checked for similar issues and didn't find anything

Wiki/FAQ Check

I've checked the Wiki for a solution and didn't find a solution

The issue names no source files, tests, or entry points to inspect. First define the binary-exclusion workflow, game/log integration, user prompts, and automation boundaries with maintainers; done would require an agreed, tested design that can identify problematic mods from repeated runs.