Please confirm the following.
What parts of Modrinth is your feature request related too?
Modrinth App
Is your suggested feature related to a problem? Please describe.
Instances crashing from a certain singular mod
Describe the solution you'd like
This is a pretty unimportant feature but I think it'd be really cool to see and would be nice for modpack devs. Essentially the idea is this:
Add a feature that uses a binary search of enabling and disabling mods to pinpoint mods causing the instance to crash. So if the instance is crashing the system would disable half the mods, then if the instance doesn't crash with half of the mods disabled then it would enable half of the disabled mods, then if it crashed again we now know that the problem mod has to be one of the ones we enabled, and this cycle continues until the jar file is pointed out and it can be like "potential problem area here". I do this exact thing manually all the time to figure out what is crashing a pack on start up and whilst it's a niche feature it'd be cool to have.
Describe alternatives you've considered
No response
Additional context
No response
Please confirm the following.
What parts of Modrinth is your feature request related too?
Modrinth App
Is your suggested feature related to a problem? Please describe.
Instances crashing from a certain singular mod
Describe the solution you'd like
This is a pretty unimportant feature but I think it'd be really cool to see and would be nice for modpack devs. Essentially the idea is this:
Add a feature that uses a binary search of enabling and disabling mods to pinpoint mods causing the instance to crash. So if the instance is crashing the system would disable half the mods, then if the instance doesn't crash with half of the mods disabled then it would enable half of the disabled mods, then if it crashed again we now know that the problem mod has to be one of the ones we enabled, and this cycle continues until the jar file is pointed out and it can be like "potential problem area here". I do this exact thing manually all the time to figure out what is crashing a pack on start up and whilst it's a niche feature it'd be cool to have.
Describe alternatives you've considered
No response
Additional context
No response