chanchan05 Posted October 17, 2018 Share Posted October 17, 2018  I was using the bashed patch as an example of Vortex sometimes getting things wrong. In fact, LOOT sorts this correctly while Vortex does not. That would be really strange, as Vortex USES Loot to do the sorting. Can you elaborate on that?  No tool is unfallible of course, and I know for a fact that Vortex has bugs (I keep reporting them). But some things are just not caused by bugs but more likely by some misunderstanding of how things are supposed to work. Which can be seen here in the forum all of the time. Found it strange too when I noticed it. I was rebuilding my bashed patch when I noticed that it didn't have scarcity in it anymore. Didn't think much of it, just moved it in Wrye Bash and carried on. I added a couple of mods (building my list for a new playthrough) and noticed that scarcity again moved out to under bashed patch, despite these being mods that have been bashable since forever (and was sorted by LOOT correctly prior to me moving to Vortex). So I just made a rule in Vortex and carried on. Link to comment Share on other sites More sharing options...
Grestorn Posted October 17, 2018 Share Posted October 17, 2018 You know that the userrules for LOOT and Vortex are stored independently? So if you create a rule in LOOT, Vortex won't see it and vice-versa. Same goes for groups and group assignments. That could be the cause behind your observations. Link to comment Share on other sites More sharing options...
chanchan05 Posted October 17, 2018 Share Posted October 17, 2018 You know that the userrules for LOOT and Vortex are stored independently? So if you create a rule in LOOT, Vortex won't see it and vice-versa. Same goes for groups and group assignments. That could be the cause behind your observations. No it isn't, because I never had a user rule in LOOT to put Scarcity above the Bashed patch. It did that on its own. I was forced to make that rule when I shifted to Vortex because Vortex kept on moving the patch above Scarcity, which AFAIK is wrong because Scarcity outside the Bashed patch would probably wreck havoc (plus this makes it that building the patch does not see the Scarcity modules). The mod author also states that the Scarcity plugins should be included in the Bashed Patch so that it would be compatible with all edits to leveled lists by other mods. Link to comment Share on other sites More sharing options...
Pickysaurus Posted October 17, 2018 Share Posted October 17, 2018 You know that the userrules for LOOT and Vortex are stored independently? So if you create a rule in LOOT, Vortex won't see it and vice-versa. Same goes for groups and group assignments. That could be the cause behind your observations. No it isn't, because I never had a user rule in LOOT to put Scarcity above the Bashed patch. It did that on its own. I was forced to make that rule when I shifted to Vortex because Vortex kept on moving the patch above Scarcity, which AFAIK is wrong because Scarcity outside the Bashed patch would probably wreck havoc (plus this makes it that building the patch does not see the Scarcity modules). The mod author also states that the Scarcity plugins should be included in the Bashed Patch so that it would be compatible with all edits to leveled lists by other mods. The way I got around this was with a LOOT group called scarcity linked between "Leveled List Modifiers" and "Dynamic Patches". With the bashed patch being in the later. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.