Bash, Merge, and Smash - Some Basic Questions

[TygerxEyes]

Greetings Folks,

 

I have hit that point where many mod users cross that line of too many plug-ins and I need to move to the next level. Overall, I have figured out a good deal of information on building large lists and plug-in load orders and have no real problems with running a decent volume of mods without a hitch. Unfortunately, because MO2 (and no mod managers I have used have a running count of installed plugins (NOTE: Vortex Development Team - I would love to see a small set of windows at the top or bottom of the plug-in list that keeps running totals of "Total Plug-Ins" and "Active Plug-Ins" and.... if you really wanted to get fancy "color coded warnings as you approach limits - green, yellow, red, and bold red"), I failed to notice that hit the limit a few times (rolling eyes at myself).

 

In any case, I am now looking at the next level decisions. With updates and additions to various mods, I am walking through my list on a spread sheet to figure out plug-in counts, gather necessary plug-ins (first group to merge-smash) which end-up accounting for a fair amount of plug-ins, look at mods which are no longer necessary due to inclusion-integration into other mods, thinking hard about whether smaller mods with small immersion changes are essential enough to warrant +1 Plug-In, and so on. I am also looking to better understand the options for merging and/or bash-smashing mods.

With regard to merging and smashing, I believe that Merge Plug-Ins and Mator Smash serve somewhat different purposes despite overlapping. As I noted, I plan to begin with smaller goals: (1) Plug-In Collections, (2) Less Complicated Groups (Arthmoor's Addition-Expansion Cities, JK's Cities (as I use only some), Followers (especially the more straightforward), and (3) Small Functional Mods Which Do Not Overlap Functions.

When I was reviewing Merge Plug-Ins and Mator Smash (just calling it Smash for here forward) and even Wyre Bash (if it serves different purpose than Smash), I though that Merged Plug-Ins were better for smaller internal subtests vs collective smashing of vast majority of mods into one esp... but I was wondering a few things:

(1) Merge Plug-Ins (in the instructional videos) is show to work on small subtests which can be individually named and result in numerous sets within a given mod list. Initially, I thought that Smash (and Wyre Bash) were used to make one massive Bash-Smash file and only one Bash or Smash should be done for a given mod list (or profile). I was, however, watching video today on Smash (early one) that had Smash merging a smaller subset to files and naming it - which lead me to wonder - if you can merge smaller subtests of files with Smash like merge and have several Smash merge collections within a given mod list.

(2) Obviously, I was wondering what the differences are and under what circumstances you would use one versus the other (generally speaking) - Merged Plug-Ins, Smash (and even W-Bash if it is not replaced by Smash).

(3) Given my current goal is not a MASS SMASH, of as many files as possible... but to merge collections of files (all patches, like groups [armors, weapons, towns, followers, and smaller mods with different functions that will not conflict and tend to be later loads with no specific demands as to what goes before or after them in mod lists) as doing so should net me 40-70 open plug-in slots which should be fine to wrap-up list... which what is the common wisdom on what things should be merged and/or smashed-bashed.

I know that my request is a little open that's fine because I am looking for answer to help me as I think about things before I ask more specific questions.

Thank-you, in advance, for wisdom, time, and effort in regards to my question and the help you might provide which I hope will help others as well.

~Tyger~