fix: item db duplicate handling is stable over insertion order#272
fix: item db duplicate handling is stable over insertion order#272BrknRobot wants to merge 3 commits intoamtep:mainfrom
Conversation
241e33b to
435c913
Compare
435c913 to
f2fed22
Compare
|
The insertion order is carefully controlled to override items in the right order. Do you have an example of where it's wrong? Because that needs to be looked at. |
|
I'm just noticing now that all the examples I have are tutorial steps. Not sure if that's due to an issue there specifically or if it's more broad, but vanilla doesn't have duplicates across files in other spots Run 1 Run 2 Run 1 Run 2 |
|
vic3 coat of arms and ck3 accessory variations have cross file duplicates but don't seem to be affected actually. I see coa has some custom logic for duplicates, but I'm not seeing why accessory variations are unaffected |
|
Possibly the difference is that tutorial steps get added as a subitem |
|
It seems that processing subitems in loc order stabilises the tutorial step duplicate reports |
Okay :) But what do you think of doing the same for other users of dup_error? Every FileHandler has one. |
Previously, the particular duplicate stored in the item db depended on insertion order.
Now, item
Locs are compared during db insertion to ensure the stored entry is the last one in the load order.The resulting reports should be stable in cases of a single duplicate. More than that may report duplicate differences in which location overwrote which, but always result in the correct final item overwriting all others