"SMQN - QNAM subrecord: Data contained within the QNAM subrecord will merge at runtime as demonstrated by numerous mods which share these nodes to add quests to the lists which all function together properly." The theory about QNAM and Quests in SMQN merging at runtime seem to have been originated here: It is my understanding that this behaviour was changed on the hypothesis that QNAM and quest merge at runtime, but test case proves that mod 3 destroys the functionality of mod 2 and that a patch that resolves the conflict is necessary for them to work together. In an ancient version of the program (3.2.1), these would actually display as conflict. They should appear as bad conflict, as the changes in mod 3 override the content in mod 2, making mod 2 not work. Test case attachment provided in additional context. Have three mods, 1, 2, 3, with 2&3 overriding a SMQN from 1 (as shown in screenshot) (see attached test case in additional content that proves that they don't merge at runtime) Quests and QNAM shouldn't show as benign conflict (see screenshot below) in TESVEdit/SSEEdit because these don't merge at runtime.
What is the version of 圎dit you are using?
0 kommentar(er)
