
via the API," reads the long post announcing the policy change. There isn't a need to worry about having plugin A directly after plugin B, if the twenty plugins in between don't conflict with either plugins."Instead of permanently removing a file, mod authors can now choose to archive it which will move it into a file archive and make it impossible to download directly unless specifically requested e.g. Using XEdit, you can isolate the plugins that needs to be actually moved and then shove some, to most, of them to a later loading group. Some people apparently take severe issue of the one extra click though, not exactly sure why). You can quickly add a rule by dragging the dependency icon from Plugin A to Plugin B, then click Add. However, that's not exactly true (and the extra work that does exist mainly comes down to moving a plugin to another group vs drag and drop. With that being said, if you're used to doing manual load ordering, you may be thinking that the system that Vortex is doing will cause you a lot of work. Want to place all of the mods together (because there are a ton of updates/add-on plugins)? Create a group and add all of them to it, then do individual rules.

Want to add a patch? Move it to a group after the main mod. Want to use a weightless mod? Just place it in a group after all of the armour, weapon, and mods that add items. Keeping this in mind, when working with the load order system in Vortex, you want to shove things into the groups towards the end of the web. etc.īecause of this, it makes sense that plugins in Group A would be placed before Group B. As this is based off of priority though, 2 beats 1, 3 beats 2. In this context, since something is pointing to something else, you're telling Group A to "look to" Group B.ĭo you remember doing connect the dots as a kid? As you're in the Plugins section of Vortex, and each name has an arrow pointing to another name. If you've clicked the "Manage Groups" button in Vortex, it should've opened up a window that looks like a web. Now, however, there is the inclusion of groups. This is just an extension of what LOOT had in the past, which was to load Plugin A after B. So with the individual plugins, you can tell Plugin A to Load After/Load Before Plugin B. LOOT changed how it worked in the past so that it now involves "Groups" in the priority order. I'm guessing you're referring to Vortex using LOOT to do the order?

XEdit helps greatly in reducing the amount of work you have to do by helping you focus on the plugins that conflict and not worry about the XX plugins in between that doesn't actually matter. Group Priority > Individual Rules, so move things around in groups before adding rules. TL: DR Vortex uses LOOT which had changed it's system a year or so ago.
