[Bug] Uninstalling many mods as auto-installed

[Seralyn]

Background

• Operating System: Windows 10 x64 (legal, fwiw)
• CKAN Version: 1.28.0
• KSP Version: 1.10.1.2939

Have you made any manual changes to your GameData folder (i.e., not via CKAN)?
Yes, but not for over a month and my issue started out of the blue just now.

Problem

Describe the bug
When I click to install a new mod and move to the Changeset tab, it CKAN tries to remove all of my installed mods. I am not new to CKAN, so this is highly unexpected behavior.

Steps to reproduce
Have CKAN installed.
Have some mods installed.
Try to install a new mod.

Expected behavior
Only the newly selected mod will try to install itself (and potential dependencies).

Screenshots (if applicable)

(in this screenshot, I have all of my currently installed mods already clicked, as they are when CKAN loads. I click the checkmark on one mod that I want to install and click changeset, and this is what I see.

CKAN error code (if applicable):

PLACE CODE HERE !

[HebaruSan]

Are all of those mods actually marked as auto-installed in the mod list?

[HebaruSan]

Here's a guess... possibly a Duplicate of #3007? Did you install these via a .ckan metapackage in a CKAN version prior to v1.27.2?

[Seralyn]

After reading these comments, I unclicked everything that had the "auto-installed" checkbox ticked and it seems to have fixed my issue! To answer your original question, though @HebaruSan , if it is true that this is part of some sort of metapackage, I can only say that it was not with my knowledge. I installed the game through Steam, and played on that file for quite some time, and only recently made a clone of my game so that my partner could play a stock version through Steam. Perhaps the process of cloning is rlated to metapackages? I clearly have no idea about that, but anyway, unclicked auto-installed, whatever that does, seems to have fixed my issue. Thank you!!

[HebaruSan]

if it is true that this is part of some sort of metapackage, I can only say that it was not with my knowledge

I guess I should have said "modpack" there. Did you install these mods by using the "Install from ckan..." option to install someone's mod list? Maybe that was how you cloned it?

[Seralyn]

Ah, I see! No, and I honestly didn't even know there were modpacks out there floating around. All mods I have installed involves me scrolling through what's compatible with my game version on CKAN, seeing what seems interesting, and clicking the checkbox on the farthest left side, and then going to changeset and hitting "apply". I've never even noticed the "Install from .ckan" until you've just now shown me.

[HebaruSan]

It's conceivable that we have a rogue mechanism whereby modules can erroneously be marked as auto-installed, but the user's problem is resolved and we don't have enough clues to investigate further. Closing for now; if this happens again, we can try to delve deeper.