![]() ![]() It can handle plugins that include scripts. Using this capability of TES5Edit is quite different than using the Merge Plugins mod described above since here TES5Edit is being using to create a set of merged records that only include records for which the mods being merged have conflicting entries while above it was merging entire mods when the mods had no conflicts. These tags can be assigned manually in Wrye Bash, by using the BASH tags sutodetection script for 圎dit, and (when implemented) automatically assigned to a mod when LOOT is used. In performing this task it uses Bash tags (for more details on the tags see here) to help determine which mod's records should have precedence when there is a conflict. ![]() For example, if one mod changes an NPC skill level to 50 and another mod changes the same skill to 60, the bashed patch will choose one of these changes or use a compromise value based on both (e.g., 55). In addition to resolving conflicts in leveled lists, Wrye Bash can also automatically resolve some non-leveled list record types when two mods change the same subrecord. Like the 圎dit Merge Patch discussed below, for records that are part of 'leveled lists' it can properly handle situations when one mod changes a subrecord and another mod changes a different subrecord and also when when two or mods change the same subrecord. The data record merging used in the bashed patch handles several types of conflicts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |