Please consider a merged REGS Patch for your next update. Something that Fixes NSutR, RR, Riften NavFull, 3DNPC, & STEP Extended. Throw in SRLE as well and you give us back 4 ESP slots. If you are feeling ultra generous, a link to a merge of all the ETaC patches would save us upwards of another dozen slots... Please have pity on us poor ESP capped souls.
Yes, I've done it a few times myself. I'm suggesting a central, managed, known good merge by the experts so that hundreds (thousands?) of people don't need to reinvent the wheel themselves.
I actually prefer doing those kinds of things myself, so I know full well what's in them. (And who to blame if there's a SNAFU... :D )
Its kinda easy to predict if there will be a good merge or a bad merge.
Yes, there are some unknowns but hey, when in doubt "Check for Errors"
Mator has implemented a system but hardly anyone uses it. I was talking with him the other day and he's like "You know you could report successful merges, right?". Little did I know, he had a .jar that would submit successful merges. Well, that is over simplified but there is definitely a system.
The most difficult part about merging, in my opinion, is remembering what needs to be patched after a merge.
I would not classify steveley's suggested merge as (very) "easy".
Most of those patches include NavMesh overrides, and so after merging them, the NavMesh Info (NAVI) record needs to be deleted from the merged patch, and rebuilt in CK.
But loading the merged patch in CK requires temporarily changing all of its masters into false-flagged .esp plugins (so set as a master, but still with the .esp file extension so the merged patch recognizes them.) This is because CK will only load one .esp plugin - everything else has to be a master.
Once you've got that all set up, you load the merged plugin in CK, and then save it. To be on the safe side, I also add the .bsa files of any of those master plugins in CK's .ini file, but CJ has already said this is not necessary if you are only rebuilding the NAVI record.
Not re-building the NavMesh will result in problems with NavMesh connections and "doors" from one cell to another.
This has already be brought up in this thread (start reading from my post here.), and is highlighted in one of missjennabee's very informative forum thread stickies for ETaC.
I don't want to scare people off, but if you're getting these patches to fix conflicting NavMeshes between mods, and then don't rebuild the NavMesh Info record, you're kind of shooting yourself in the foot.
Edited by keithinhanoi, 15 April 2015 - 04:47 AM.