I'm trying to recover from damage caused by TESVSnip. I got version control working in the CK and I'm busy consolidating lots of esps into an esm

I am having a problem however. Suppose I have an esp that depends on several masters, and suppose I check a record from that esp into my nice clean ESM. I get a warning saying that if I proceed, my new ESM will acquire the dependencies of the ESP. Which is to say if the esp depends X.esm and Y. esm, after checking in, my new esm also depends on X and Y.

I hope that made sense. I may need to use diagrams.

Anyway, this seems to happen, even if the record I'm copying has no relation with X.esm or Y.esm. And I'm getting endless warnings about masters depending on multiple masters in the CK, and needless dependencies for my mod.

Any ideas how to stop it? I could remove the deps with TESVSnip, of course, but that's partly how I got into this mess...

To remove a master with CK: File > Data > Parent Masters > Unwanted Master > Del > OK > Save

Fantastic, thank you!

It would have been a while before I found that one by myself

[edit]

You know, I could have sworn I tried that already. Just goes to show...

[edit]

I take 'em out and they come right on back. Damn this is frustrating...