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. But in case of unchanged mod setups this is annoying, especially as my children are not as familiar with mods or WCM as I am.TL: DR Vortex uses LOOT which had changed it's system a year or so ago. Which is obvios expected as other mods may get deployed. Witcher Game and Witcher Test or Witcher Son or Witcher Daughter, the merged files are not vailde anymore and WCM deletes the merged file.
Is it possible to store the Witcher Script Merger merged files? When I switch to another profile, e.g.
whenever I test a mod or switch to another profile. Is it possible to implement something that forces the load order in the same order as I setup the deploy order? Not by drag and drop the mod, maybe just by clicking a button? That would be great and closer to my wish to automate some processes, e.g. The result of this approach was a deploy order I preferred and pretty much what I needed as load order. By doing that an popup opens asking to set something like "must load before / after", "requires" or "in conflict with". But the deploy order can also be set by drag and drop the dependencies. Setting the deploy order in case of conficting mods is okay. And I might understand what confused me and what still gives me an headache. This is the one I saw a video on youtube. I just read the Managing_File_Conflicts guide. I've attached a document about the ttings file. The game loads the mods using the "Priority" property, where a mod X with Priority=1 gets "priority" over a mod Y with Priority=500 in which case, if mod X and mod Y are conflicting in any way, mod X has priority and will win the conflict. Load order on the other hand is completely different - Vortex uses the ttings file to define the order in which the game should attempt to load the mods that were deployed by Vortex. As a side note, W3 has a script merging tool which can be used to avoid these conflicts altogether. The conflict editor is basically what is used to decide the "deploy order" so that the wanted files end up in the game's mods directory. So if you have mod X and mod Y both of which are attempting to modify the same file, you can choose whether mod X loads after mod Y which will guarantee that mod X's file wins the conflict, or the other way around. As far as file conflicts are concerned, the conflicting file that gets deployed last will win the conflict. Basically when 2 mods have conflicting files, our conflict editor will allow the user to decide which mod file wins the conflict. Hey so what I think you were reading on Google and on the forums refers to our conflict manager.
0 kommentar(er)
