Hi, V.
A couple of things. First, thanks for the Fort Ferrion patch. And not just for the patch, but for bringing Fort Ferrion to my attention. I remember someone, probably a couple years back, commenting on how many really good mods they were made aware of by noting which were getting UL patches. Same thing has occurred with me.
Second thing has to do with another mod by Edolsian (same author who did Gaelendryll as well as Fort Ferrion). The mod is Ruins of Tarnesia. It gets a lot of praise in its Nexus comments by some, while at the same time others are noting the huge number of dirty edits as well as the many wild edits. Dirty edits I can deal with thanks to TES4edit, but I just don't think I have the skills to recognize, let alone correct, wild edits. Is this perhaps easier to do than I and the typical experienced but non techie mod user may believe?
Also... please confirm my assumption that a UL patch would never be provided for any mod containing wild edits. Or... is their such a thing as truly insignificant wild edits?
Of course a patch would be provided for mods containing wild edits. Most mods contain at least a few wild edits, Fort Ferrion contains a few (about 30 to 35), on top of the 4,430 identical to master records (out of 5,476 records) but I still patched it. A thorough session with TES4Edit on Fort Ferrion will reduce the record count from 5,476 down to 1,011, reducing file size from 3.2mb to 142kb. Leaving the wild edits in would result in a slightly larger file size. However the wild edits in Fort Ferrion were minor so it wouldn't matter if they were left in.
If a mod clearly breaks vital parts of the original game, I may choose not to patch it, but it is rare that I come across a mod containing wild edits that serious.
I do not recommend that people start trying to remove wild edits unless they're willing to take the time to understand everything they see in TES4Edit. What you might think to be a wild edit could easily be a genuine edit, and you have to learn to identify whether it is genuine or wild. Some are exceedingly obvious, such as in Fort Ferrion, where several vanilla interior cells used to contain water height of -2147483648, but Fort Ferrion removes the water height entry. This is harmless as a water height of -2147483648 is technically no water, but the CS keeps slipping in -2147483648 instead for some reason (which makes Fort Ferrion unusual in that it accidentally removes an accidental water height entry, normally it's the other way around, accidentally adding in the water height to a cell without water).
Nothing else is edited in these interior cells (once you have removed the identical to master records) so these interior cells can be removed from the ESP, removing the wild edit.
Then there's the other kind of wild edit, where the edit is genuine but misplaced. Take for example the two vanilla containers edited by Fort Ferrion. The mod adds new clutter to these two containers - but these containers are used all over the game and by other mods so this additional clutter would appear everywhere (one item is a potion to cure vampirism, which is meant to be a rare item). So this wants removing from the mod - except that these edits are intentional as the modder has used these containers in the Fort Ferrion interiors. To resolve, the Form IDs to these two containers need changing so that they match Fort Ferrion.esp instead of Oblivion.esm, making them unique to the mod (then change their Editor IDs too to please the CS - else it will inform you it has added DUPLICATE to the end of the Editor IDs which doesn't really matter but looks untidy to me). Changing the Form IDs will remove the additional clutter from the containers across the entire gaming world, but will still keep them for the Fort itself as every reference of these containers by the mod will now be using the new containers with the altered Form IDs.
Unless you know for certain what the edit in a specific record would do in-game, you cannot know for certain whether it's a genuine edit or not, and whether you should remove it or change its Form ID instead. It is easy to recognise, but only if you take the time to understand what you're looking at before you start to remove records.