HadToRegister Posted December 12, 2018 Share Posted December 12, 2018 OK, This mod for Skyrim SE called Riverside Shack It installs fine, however, if you install the 3.01 update which only consists of the updated ESP, instead of treating it as a patch, it thinks that 3.01 is the entire mod, and sits it right on top of the old mod in the Mod Tab, so you end up with the Version Dropdown in the Version Column, rather than treating it as a patch and showing both the 3.0 archive in the mods tab, and the 3.01 archive in the mods tab.What then happens is, you install 3.0 for all of the files (BSA and seq) and esps, then you pick 3.01 from the version dropdown, and it replaces 3.0 esp and removes all of the corresponding files with the 3.01 update esp without any of the files (BSA and SEQ) that need to go with itWhat I did to get around this was to add the word "PATCH" in the name of the 3.01 update file archive, and force Vortex to see 3.0 as the mod, and 3.01 as a separate patch.Then, I was able to install the mod (esp, Bsa and Seq), and update just the esp with the 3.01 archive.I'm sure that there are other mods out there that are having this happen as well, and I was wondering what is needed for Vortex to be able to tell a patch or update from an entire mod?tl;dr Vortex mistakenly thought that an update (3.01) was instead an entirely new version of the mod and stacked them on top of each other in the Mod Tab, and assigned them version numbers, which made installing the update/patch impossible without Vortex removing the 3.0 files, so the archive name of the 3.01 needed to be changed so it, and the original mod would show up separately in Vortex so I could then get the "File Conflict" message in order to tell the patch to LOAD AFTER the original. Link to comment Share on other sites More sharing options...
zeknapain Posted December 12, 2018 Share Posted December 12, 2018 That's really usefull for the future. Thanks Link to comment Share on other sites More sharing options...
AugustaCalidia Posted December 13, 2018 Share Posted December 13, 2018 OK, This mod for Skyrim SE called Riverside Shack It installs fine, however, if you install the 3.01 update which only consists of the updated ESP, instead of treating it as a patch, it thinks that 3.01 is the entire mod, and sits it right on top of the old mod in the Mod Tab, so you end up with the Version Dropdown in the Version Column, rather than treating it as a patch and showing both the 3.0 archive in the mods tab, and the 3.01 archive in the mods tab. What then happens is, you install 3.0 for all of the files (BSA and seq) and esps, then you pick 3.01 from the version dropdown, and it replaces 3.0 esp and removes all of the corresponding files with the 3.01 update esp without any of the files (BSA and SEQ) that need to go with it What I did to get around this was to add the word "PATCH" in the name of the 3.01 update file archive, and force Vortex to see 3.0 as the mod, and 3.01 as a separate patch. Then, I was able to install the mod (esp, Bsa and Seq), and update just the esp with the 3.01 archive. I'm sure that there are other mods out there that are having this happen as well, and I was wondering what is needed for Vortex to be able to tell a patch or update from an entire mod? tl;dr Vortex mistakenly thought that an update (3.01) was instead an entirely new version of the mod and stacked them on top of each other in the Mod Tab, and assigned them version numbers, which made installing the update/patch impossible without Vortex removing the 3.0 files, so the archive name of the 3.01 needed to be changed so it, and the original mod would show up separately in Vortex so I could then get the "File Conflict" message in order to tell the patch to LOAD AFTER the original. What if you unpacked both mod archives and then repackaged 3.0, substituting the 3.01 update .esp for the 3.0 .esp? Would that create any problems for Vortex? You could note in the mod details pane that the repackaged mod is v. 3.01. Link to comment Share on other sites More sharing options...
HadToRegister Posted December 13, 2018 Author Share Posted December 13, 2018 What if you unpacked both mod archives and then repackaged 3.0, substituting the 3.01 update .esp for the 3.0 .esp? Would that create any problems for Vortex? Why do that when I can achieve the same effect without all that work by just simply making sure that the file name of the archive is different enough that Vortex treats them as separate entities?By just right-click, picking "rename" and adding "patch" to the archive name. Link to comment Share on other sites More sharing options...
AugustaCalidia Posted December 13, 2018 Share Posted December 13, 2018 What if you unpacked both mod archives and then repackaged 3.0, substituting the 3.01 update .esp for the 3.0 .esp? Would that create any problems for Vortex? Why do that when I can achieve the same effect without all that work by just simply making sure that the file name of the archive is different enough that Vortex treats them as separate entities?By just right-click, picking "rename" and adding "patch" to the archive name. Oh, I agree with you that your approach is the simpler and easier, and I would certainly use it. I was just curious to find out if you thought merging the mods would cause any special problems for Vortex. If not, then there is at least one small thing in its favor, viz., it reduces by one the number of plugins. Link to comment Share on other sites More sharing options...
HadToRegister Posted December 13, 2018 Author Share Posted December 13, 2018 What if you unpacked both mod archives and then repackaged 3.0, substituting the 3.01 update .esp for the 3.0 .esp? Would that create any problems for Vortex? Why do that when I can achieve the same effect without all that work by just simply making sure that the file name of the archive is different enough that Vortex treats them as separate entities?By just right-click, picking "rename" and adding "patch" to the archive name. Oh, I agree with you that your approach is the simpler and easier, and I would certainly use it. I was just curious to find out if you thought merging the mods would cause any special problems for Vortex. If not, then there is at least one small thing in its favor, viz., it reduces by one the number of plugins. It doesn't add/reduce the number of plugins, because of the way Vortex handles the plugins. My load order doesn't have two "RiversideShack.esp" in it.Vortex knows if it finds a conflict between two different versions of "RiversideShack.esp (3.0) and "RiversideShack.esp" (3.01) that when it finds a conflict between the two, and you tell vortex to load "RiversideShack.esp(3.01) AFTER RiversideShack.esp(3.0) it will virtually overwrite version 3.0 with version 3.01, so only ONE RiversideShack esp will show up in your load order (It's a more elegant version of NMM's "Do you want to overwrite this file?" thing) IE: If I downloaded a mod that started at version 1.0 of the ESP, and it had 4 new versions of the ESP that I had to download, after resolving the Conflicts between Esp 1.0, 1.1, 1.2, 1.3, 1.4, by telling vortex to... Load Esp 1.1 after Esp 1.0Esp 1.2 after Esp 1.1Esp 1.3 after Esp 1.2Esp 1.4 after Esp 1.3 I would still end up with only ONE ESP for that mod in my Data folder, and it would be Esp 1.4 because Vortex knows that I only need one ESP for that mod, so if I looked in my Data folder I wouldn't see 5 esps all named RiversideShack.esp Link to comment Share on other sites More sharing options...
AugustaCalidia Posted December 13, 2018 Share Posted December 13, 2018 It doesn't add/reduce the number of plugins, because of the way Vortex handles the plugins. I stand corrected. Thank you for your helpful explanation. Link to comment Share on other sites More sharing options...
Pickysaurus Posted December 13, 2018 Share Posted December 13, 2018 This is interesting feedback, Vortex usually treats Update and Main files as separate entries. Might be worth sending some feedback via the app itself describing this issue. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.