Editing mods in SSEdit for use preference

[Tulsa299]

User* preference rather.

Say I have two mods that both edit, say, Nazeem and also edit every other npc

Mod-1

Mod-2 (last in the load order)

And say I want Nazeem from mod-1 to take priority and "be let through" mod-2

Would opening SEEedit and deleting the reference to Nazeem from mod-2 from within the NPC (actor) section achieve this result without adverse affect?

I know there are better ways of achieving this, forget that.

My knowledge of SEEdit and it's terminology are not so great, so please forgive any derps :wink:

Thanks.

Edited March 2, 2017 by Tulsa299

[zilav]

Yes.

[PeterMartyr]

No you make merge Patch, then if use Wrye Bash, you Update your Bash Patch, & Ghost the Patch you just made.

 

Wow what hornet nest you opened, by asking simple question. But to keep simple ModA ModB PatchC Copy the Records From ModA into the PatchC, so it over writes ModB. Then you can reinstall Mod A & B without losing your PatchC.

 

Next set the LOOT user meta data for these three esp, so it sort them correctly.

 

Good luck, we learn by our mistakes.

 

If you use Wrye Bash &&& use it correctly? Skip the LOOT bit, you don't need it.

[Tulsa299]

Perfect answer, thank you.

I don't use LOOT, I prefer manual ordering.
My basic method is, SSE>MergedPatch>Delete level list/levelednpcs (or something to that effect)>save> Wyre> rebuild patch only having merge mods and level list ticked.

Just for the sake of knowledge, why do we ghost the merged patch? Am I right in assuming ghosting within Wrye is equal to deactivating the merged patch before opening Wrye, essentially ignoring it?

Thanks again for the help, I'll be sure to pass it on :)

[Deleted3897072User]

Assuming that this is just for private use and assuming that nothing elsewhere in ModB relies on the changes it makes, I would have said "yes" although If you ever update ModB, you would have to remember to do it again.

Edited March 2, 2017 by OldMansBeard