Regardless of whether the plugins are enabled or not, launching Skyrim LE through steam then navigating to the Data Files option in the launcher menu displays all plugins as activated. This is the bug.
Using the launcher to unselect the high res texture packs (that were enabled with ammo) our files become this:
DLCList.txt
Dawnguard.esm
Dragonborn.esm
HearthFires.esm
HighResTexturePack01.esp
HighResTexturePack02.esp
HighResTexturePack03.esp
plugins.txt
# This file is used by Skyrim to keep track of your downloaded content.
# Please do not modify this file.
Dawnguard.esm
Dragonborn.esm
HearthFires.esm
Plugins.txt
*Dawnguard.esm
*Dragonborn.esm
*HearthFires.esm
*HighResTexturePack01.esp
*HighResTexturePack02.esp
*HighResTexturePack03.esp
SteamModList.txt
Ammo can solve this by:
de-duplicating plugins.txt
If a plugin that's in DLCList.txt is disabled, it should not be written to Plugins.txt at all, or it will be automatically loaded.
If a plugin is in both Plugins.txt and DLCList.txt, it should be considered "enabled" even if it doesn't begin with an asterisk.
Ammo should not write to DLCList.txt for any reason, but it will still need to read from it.
Ammo did not de-duplicate the
Plugins.txt
andplugins.txt
, but it should be responsible for this.ls /home/cyberrumor/.local/share/Steam/steamapps/compatdata/72850/pfx/drive_c/users/steamuser/AppData/Local/Skyrim
With all DLC disabled through ammo, file contents are the following:
With all DLC enabled through ammo, file contents are the following:
Regardless of whether the plugins are enabled or not, launching Skyrim LE through steam then navigating to the Data Files option in the launcher menu displays all plugins as activated. This is the bug.
Using the launcher to unselect the high res texture packs (that were enabled with ammo) our files become this:
Ammo can solve this by: