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.
