Armours, keywords, and workflow approach.

[McRutt]

Hey all, I would love some advice on what to do in my current situation:

 

I am working through my collection of armour and clothing mods for a new modlist, applying new masters and keywords to them. After changing the masters mod by mod in SE Edit, for around 100 of them, and being aware I had another 900 odd to go, I have to wonder if there is a better way.

 

Currently I'm working on keyword functionality for SL Aroused, OSL Aroused, Advanced Nudity Detection, Bimbos of Skyrim, and Outfit Recognition Framework.

 

In the future I would like to apply some kind of functionality to a degradation mod (Currently have VSU degradation, but I'm led to understand there are problems with that approach), the functions and sub-mods of Slave Enforcer Standalone 2, and get my head around applying functionality from devious devices to some armour mods (Predators' mods. Don't understand why they don't come out of the box with these functions as an option but oh well).

 

As I understand it; in my case with the amount of armour mods I have; it would be much easier to merge the armour mods together, change the masters, then summarily apply keywords as necessary; the caveat being that merging can cause problems with spids or other distribution mods because a merge changes records. 

Now, I have never merged armour mods together, being a modder of the .esl age. I have never experienced the problems of a merge firsthand. 

 

So my question is: Am I right? Should I be merging my armour mods because that's going to be easier long term than changing masters 900+ times (Not to mention the time saved in labelling thousands of items with the 'erotic armour' keyword at once). If I am right, what do I need to know to iron out the issues with distributions or any other problems that crop up as a result of a merge? 

 

If I'm wrong, is there a better way than having to slog through so many armour mods?

 

[LlenneiasWard]

use KID, Keyword Item Distributor. learn the syntax through inis and you won't ever need to touch any ESPs. hassle-free and easy to change, generally.

[McRutt]

30 minutes ago, LlenneiasWard said:

use KID, Keyword Item Distributor. learn the syntax through inis and you won't ever need to touch any ESPs. hassle-free and easy to change, generally.

That's a million times worse than what I currently do. 

 

Can you imagine lines and lines and lines of text in .txt files attributing keywords to thousands of individual pieces not even in a database format. Who would do such a thing? Why would they do such a thing?