New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Skyrim/SkyrimSE] Quests/QNAM in SMQN shouldn't show as benign conflict #1016
Comments
I've had a chance to test this now. The conclusions are mixed: For LE, everything works as expected. There is no need for the patch .esp file. This was a fresh install of LE with no mods as I had long since uninstalled it and needed to get it back. For SE, the patch .esp file is necessary and I'm able to duplicate your results exactly. There is only one thing I did to both of these before using the scripts - I changed the call to Debug.Trace instead of Debug.Notification because I've had instances where those notifications are not reliable. So it appears as though Bethesda did something in an SE update at some point which has removed the runtime merging of the QNAM group. I've checked my current game load order and this issue would only have affected a minor node between the Bruma mod and the Dawnguard DLC for follower commentary. So it also seems that somewhere along the way Bethesda also quietly resolved the conflicts the files used to have with each other, which was what prompted the original LE testing to begin with. |
Thanks for testing. So the conclusion is: leave as is for LE, but consider it a normal conflict for SE? |
Yes, that's what I'd go with. |
Thanks for testing. As for LE, I will give another try if you don't mind, the more tests the better. This time, I will remove all mods, and even SKSE itself, I think I'll just fully uninstall the game in Steam (and make sure that it really removed it) and install it again, as to be on the same scenario than you. If Debug.Notification is unreliable, I will instead use something else, but personally I prefer something that can be observed in game itself, I think I will try giving a different fixed amount of money to the player in each hold. Even if for X reasons, the message the game does that gold has been added were also unreliable, the amount of gold in the player should be updated. I'll report the results later. If for whatever chance, they don't match, I will add a second test case with the updated scripts. Edit: on a second thought, instead of giving player gold (which can be problematic to count if you test multiple holds), I will giving the player exactly 1 arrow in each hold. but a different type of arrow in each hold. That should make the test less prone to mistakes. |
… benign conflict (cherry picked from commit 9588db3)
should be fixed with commits above, will be in 4.x.4e |
What is the version of xEdit you are using?
SSEEdit/TESVEdit 4.0.4
Describe the bug
Quests and QNAM shouldn't show as benign conflict (see screenshot below) in TESVEdit/SSEEdit because these don't merge at runtime.
(see attached test case in additional content that proves that they don't merge at runtime)
To reproduce
Have three mods, 1, 2, 3, with 2&3 overriding a SMQN from 1 (as shown in screenshot)
Test case attachment provided in additional context.
Expected behavior
They should appear as bad conflict, as the changes in mod 3 override the content in mod 2, making mod 2 not work. In an ancient version of the program (3.2.1), these would actually display as conflict. 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.
Screenshots
Additional context
The theory about QNAM and Quests in SMQN merging at runtime seem to have been originated here: https://www.afkmods.com/index.php?/topic/3940-skyrim-tes5edit-records-that-merge-at-runtime/
And in concrete from this part:
"SMQN - QNAM [Quest Count, Quests] 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."
This page is also linked in https://tes5edit.github.io/docs/5-conflict-detection-and-resolution.html#RecordsThatMergeAtRuntime
So it is my guess, and please correct me if I'm wrong, that the change of behaviour at some point of SSEEdit life (somewhere after 3.2.1) may have been done because of that information.
Now don't get me wrong. The information in the afkmods page seem to be correct... except that bit in concrete, which doesn't match the results in game of my tests. Since I don't expect to deny a information that has been around for 8 years and expect you to believe me out of the blue, I provided a detailed test case. I should also say that I originally encountred this issue in a real mod (not of mine). The test case is meant to be run in game. I provided two versions, one for Skyrim SE and other for the classic Skyrim. I tried to made them as simple as possible. They don't overwrite any vanilla or dlc content.
I also posted the test case in afkmods, but it seem these days people rarely use the forums and no one has tried it, so I'm posting this here too, since it affects xEdit aswell.
The test case shouldn't steal you more than 15-20 minutes of time. I'd appreciate if any of you could give it a try whenever you have some spare time. The .txt in the zip has the info about how to run the mods/tests that confirm issue.
If there is something not well expressed (sorry for that, english is not my mother language), or if you notice something strange in the tests, or you want me to test some other scenario, let me know.
SMQN Test Case.zip
The text was updated successfully, but these errors were encountered: