I decided to have a look at something that has always irked me: the warnings that the CK spits out just from loading the esm master files alone. Skyrim already caused some, and each DLC adds to the pile. (I have not really had a look at Skyrim for a year or so, but I recently purchased the TES Anthology from a local retailer's going-out-of-business sale, so I thought I might give the DLCs a spin.)

Thus, I have been writing a C++ based command-line tool to directly modify Skyrim.esm, Dawnguard.esm, HearthFires.esm, and Dragonborn.esm in such a way, that the editor warnings are eliminated. This involves stuff like re-ordering INFO records, deleting some sub-records, adding some others, and changing the content of a few, as well as finally re-adjusting world cell offsets after all the changes (in case somebody was wondering about that).

I am not entirely sure whether it would make sense to eventually release this or not, as I wonder if there might really be any interest towards such a thing, or whether anything similar already exists. Also, my coding, although it does the trick, may not exactly be neat or very presentable, as I have absolutely zero professional experience in such matters. Still, this does make it worthwhile to click through the CK editor warnings, once they are more closely related to plugins (or their interaction with the masters) rather than the masters themselves.

At any rate, I have now covered almost all the issues, and it seems to work perfectly. Still, two remain, and concerning them I would very much appreciate a second opinion:

1. The First open issue concerns Dawnguard:

MASTERFILE: Unable to find Package Target Reference (00000000) on owner object "DLC1VQ02SeranaPullLever".

This would fundamentally be a very straightforward thing to fix. However, I do not wish to research the correct fix prior to playing the DLC. I wonder, if anybody might be able to tell me right away, whether Serana is ever in a position to pull a lever and fails to do so, and what that lever might be, or whether this is just a dead-end scenario, which never has the opportunity to be played out.

2. The Second open issue concerns Hearthfires:

MASTERFILE: Missing sibling 010162A0 found in story manager node WIChangeLocationNode' 000A39C6under parent node 'Change Location Event' (0001320E).

It seems to me, that in the Story Manager various Branch/Quest nodes are chained together (via SNAM subrecords) to create a prioritized (in this case) sequence of possible actions to be triggered by an Event node. In vanilla Skyrim, the sequence in this case begins with 'QuestNode' [SMBN:00090028] and ends with 'BQBranchNodeSHARES' [SMBN:000CBA9F].

Hearthfires adds a new item 'BYOHHouseChangeLocationNode' [SMQN:0100308C] to the end of the sequence. It also seems to have, what might be a dirty edit to 'WIChangeLocationNode' [SMBN:000A39C6], which appears to break the chain in two parts:
- from 'QuestNode' [SMBN:00090028] to 'WIChangeLocationThiefNode' [SMQN:00023F1B], and
- from 'WIChangeLocationNode' [SMBN:000A39C6] to 'BYOHHouseChangeLocationNode' [SMQN:0100308C].
My impression is, that the mutual ordring of these two chain halves is now undetermined, and at least the CK shows the second part taking precedence over the first part, which I suspect is not intended.

I strongly suspect, that the correct thing to do here is to eliminate the apparent dirty edit and to re-connect the chain as it was originally (apart from the new item at the end). Still, I would be curious to hear, if anybody playing the game may have thought, that when the player's location changes, Hearthfires-related things seem to happen slightly too frequently relative to some other possible happenings. (By the way, loading Dawnguard after Hearthfires would apparently fix this, as it duplicates the original version of the relevant record.)

P.S.
These two issues are not covered by UDGP or UHFP, and I guess they might potentially also be of interest to the USKP team, unless they gaming-wise are non-issues, which could also be the case, and I just wouldn't know about it yet.