Add a mod to the \Mydocuments\ARMA 3\ folder using the @mod name convention. Go into ARMA3 and under the Expansions menu - Enable the above mod. Add and enable a few more mods the same way.
Create, Play and Save a few missions that use these mods (this step might not be necessary). Exit ARMA3. Restart ARMA3 and disable a few mods. Exit ARMA3. Go back into ARMA3 and check the Expansions list - the mods that were disabled are still listed under Expansiosn and are shown as enabled. Exit ARMA3. Remove all the @mod folders under \Mydocuments\ARMA 3\. Start ARMA 3 and go to Expansions - most uninstalled mods are still listed and shown as active!
Now double click on or enable one of the mods in the list - the mod shows that you have enabled it even though it does not exist in the \Mydocuments\ARMA 3\ folder! So I assume ARMA 3 is caching these mod files somewhere and that's what is causing part of this problem and perhaps is creating other issues we don't know about.
Given that many users run upwards of 15 mods in ARMA3 these issues need to be resolved urgently. In particular duplicate mod listing and incorrect mod status under the Expansions menu.
In addition we need a robust mod compatibility 'on load or startup' test to prevent mods breaking ARMA3 during the start up process.
I'm sure some well meaning community member is going to say - don't use the Expansions menu rather use the startup option -mod - well my considered response is - Nuts!
Why should we always have to find 'work arounds' for ARMA 3 bugs. Why can't they just fix the damn things!
Hence this ticket.