Help shape the future of CurseForge!

@Team Overwolf for debugging purposes, you might need to disable all mods, then start to re-enable few by few until the issue happens and hence you find the problematic mod. or the other way around, by disabling few by few mods until the issue is gone and hence again you find the problematic mod, then you have to enable everything you disabled in the process one by one, which is tedious.

the second use case is when you have some disabled mods for whatever reasons, and you want to enable them, it can be tedious to navigate the mod list to find the mods you disabled, which you most likely don't remember the names and amount, a enable all feature would save time.

@itsmeowdev the enable/disable button for individual mods is already present, you don't have to delete mods anymore, I'm only requesting a global enable/disable.

I think the poster was requesting it as a convenience feature. Instead of clicking hundreds of mods "Disable", "Disable", etc. They want a button to do it all at once so they can properly diagnose issues with mods in packs, which often involves adding/removing mods until you find the problem causer. They are also requesting the presence of an "Enable/Disable" button in the first place- I think this would be useful. You can remove/disable a mod from a pack without actually removing it in order to test.

Often, when updating mods, packmakers can run into unexpected crashes- and if you update a lot of mods at the same time, you won't know which ones could be culprit. Hence, enable/disable instead of the current solution which would be to delete the mod.

If you disable all mods, won't it just be Vanilla? we'd appreciate more details here to understand the use cases and if we should perhaps offer a different solution for the symptoms of the problem.