This is needed so badly it hurts. I am a modpack developer and tester. As I get mods or run tests against mods - things break. Sometimes I need to remove mods that are causing problems. This is where things get tricky. The CurseforgeOverwolf Desktop Application often removes dependencies for an otherwise working mod. During testing on 100s of accounts I find either curseforge automatically adds things or automatically removes things. We need a middle ground so here is my proposal. https://curseforge-ideas.overwolf.com/ideas/CF-I-2484

Quote from "Guest": Aside from the language you are using, that sounds like it just an inconvenience. If that's the case why not just keep a list of all the dependencies that multiple mods, and whenever you turn off a mod just delete from the mod folder manually instead. I don't think that they are able to program in such a fine thing you are asking for. it's like asking a computer to distinguish a one cherry in a cranberry basket.

Also asking for things there's always a please in the request, and a thank you sometimes but not always expected or needed.

I have to disagree. This is invalid. Curseforge already has a dependecy system curated by mod authors. Its just seems to me as a modpack maker that the app treats all these dependent/dependecies relations as 1:1 when they are often n:1 for library mods or 1:n for addons. If curse can install dependencies for mods automatically it should also be able to keep those that are need.
The only difference it that the process of removing depencecies can not just use the same logic/api-calls (?) as the one for installing. It would have to check the collective dependencies of all mods in the pack first (maybe in a per modpack cache) to see if there are other mods in the list that also needs this before removing the depending mod. Since curse only checks for missing dependencies on installation, and not on removal of another mod.

I am aware that this idea is not written in the best tone but i can say that the issue described here is my biggest gripe with the CF-App atm. I am workign on a large pack and my modlist is so long I am afraid of disabling/deleting any mods now through the app. It is easier/safer for me to close it. rename the files manually to ".disabled" start the app again. Start minecraft and let me tell by forge if I disabled too much.
Removing apps vie "export profile" and keeping a list of which mods to untick in the export list. This way I avoid CF removing still wanted mods.

I also don't know is this is the only post that has been opened regarding this but I hope this will bee seen regardless.

It's not hard to do, it's just few line to add, if a mod needs it or not. IF usage is thought in first days of any programming course or class. I learned about it and it would not require that much time to add such a feature. It's just few lines of code nothing huge

Aside from the language you are using, that sounds like it just an inconvenience. If that's the case why not just keep a list of all the dependencies that multiple mods, and whenever you turn off a mod just delete from the mod folder manually instead. I don't think that they are able to program in such a fine thing you are asking for. it's like asking a computer to distinguish a one cherry in a cranberry basket.

Also asking for things there's always a please in the request, and a thank you sometimes but not always expected or needed.

language