Content of the article: "Clarification of Conflict Resolution Patches"
Not new to modding Bethesda games but new to using a huge number of mods that will almost surely have problematic conflicts (author compatibility patches aside), and therefore require more intervention than just optimizing load order. So I've been doing research into this topic and am trying to get a better sense of what each tool actually does. In particular, when seeing things like "make a
My question, that is ultimately rhetorical, is this: Why are records in plugins handled in such a matter that conflicts are registered at the record level, instead of via a comparison of each and every attribute of said record regardless of node depth? It makes sense if the exact same attribute of a record is modified (i.e. starting level of NPC) that this creates a conflict that can't be resolved automatically since its impossible to have the change from each mod in effect at the same time. But for changes to parts of a record that are not direct clashes it seems silly that the engine will throw out all previous changes to the record just because a later patch changes something else.
More or less the example always given is something like Mod A changes the location of a light, but Mod B changes the brightness, without a compatibility patch only the change of the plugin that loads last will take effect? Why? The idiomatic approach and what users would want 95% of the times (I can see some specific situations where you'd want to throw out the contents of the old record, but there should just be specific flags for achieving this in a plugin, like Delev, instead of it being the default) is to just keep both changes to the record, position and brightness, since they aren't within direct conflict. The same issue is present for leveled lists and all other records.
The question is rhetorical because that decision was made by Bethesda and so we can't know for sure why they made it that way, neither can we do anything about it without heavily modifying the engine?
So, my actual question is: Going off this premise, are there tools that scan over every individual change of a record recursively and automatically build a compatibility patch for all loaded plugins that sets all modified records to a version that combines all unique changes made by mods higher in the load order, leaving only singular direct value conflicts (most likely using the original conflict winner for those values) to be handled by the user in xEdit since those literally cannot be automatically resolved?
Is this what Bashed Patches (for records that Wrye Bash handles) and Smashed Patches (for more or less all records) do?
- Wrye Bash and Mator Smash
- Question about creating patches with xEdit
- Perk tree edits don’t appear in game.
© Post "Clarification of Conflict Resolution Patches" for game The Elder Scrolls.
Top 7 NEW Games of June 2020
Quite a few exciting games are releasing for PC, PS4, Xbox One, and Nintendo in June. Here's what to keep an eye on.
Top 10 NEW Open World Games of 2020
Video games with open worlds continue to roll out in 2020 on PC, PS4, Xbox One, Nintendo Switch, and beyond. Here are some to look forward to!
Top 10 Best New Upcoming Games 2020-2021
The best selection of games which will be released in 2020 and 2021 for PS4, PS5, Xbox One, Xbox Series X, Google Stadia and PC - and you can watch in amazing UHD 4K and 60FPS with latest updates about all of the games in this list!