Good Naming and versioning for LL mods

[Uhuru N'Uru]

There is one naming convention for all NMM mod archives I approve of, that is the mods page code must be included in the archive.
This means even though they are named erratically, all the mod files can be found easily on your system and you can always add the code to the end of
http://www.nexusmods.com/skyrim/mods/
 
to find the mod page as easily.
 
LoversLab has  a similar functionality, though the full mod address includes the name like so
http://www.loverslab.com/topic/16623-skyrim-sexlab-sex-animation-framework-v1602-hotfix-2-updated-sep-1st-2015/
 
My experiments show that actually, only the dash after the number is required, like so
http://www.loverslab.com/topic/16623-
 
This will take you to the download page without needing the name, as you can see by checking the links (Site contracts the long first one for viewing only). It also works for the support page, in fact it works for the entire LL site, that I've tried.
 
So this enables a similar convention for LL mods, we only have to start using it, no site changes required for this.
 
I would also suggest in combination with this change, standardised naming and versioning structures should be encouraged.
This can be used instead of site codes, but is more complicated with multi-part mods
The examples I give below are one option among many, the basic principles of clearly stating the mods intent and relationship to all the other parts of the mod are the main goal.
 
Spoiler tagged the naming example, to which I must simply add "Next,"

First we start with the mods name, it should be the Download Page name which should start with any abbreviation that's commomly used.
TiaM - This is a Mod

Next, I add a category, Core is the main mod and other titles like Addon, Patch, (Nexus: Main, Option), etc. Used as appropriate.
TiaM - This is a Mod - Core
 
Next, comes the main Submod, the file is this or changes this in some way. the core mod and individual addons, etc.
If this is the core mod and has an abbreviation defined in the mod name, which are often the same, then the abbreviation can then be used alone.
TiaM - This is a Mod - Core - TiaM
 
Next (I can see a big "Next" below this), comes the Version of the mod here I'd recommend a modding requirement focused system, something like this;

First Number means a new start is required, these should rarely change due to that requirement.

Second Number means a major change, requiring updates to at lest one dependant mod or submod.

Third Number is for minor changes, bug fixes and changes to existing content that require, no other changes to other mods or submods.

Alpha/Beta can be used to indicate releases for testing, not playing.

TiaM - This is a Mod - Core - TiaM v1.2.12 Beta
 
Next (The big one you saw coming), comes any optional and alternate changes to the submods, these are not usually mods themselves, unless alternatives to the main sub mod.
The main submod is always the first alternative listed and seperating the plugins that are changable into separate submods, makes switching and merging easier for more advanced multi-profile modding, at least using Mod Organizer's priority and profiles system.

Alt-# means a direct file replacement, these are usually indicated in FoMod's and other installers using a bullet system, but the key requirement is only one alternatives can be used.

Opt-# means you can choose as many of the numbered optional mods, as you want, these add additional files and are usually indicated in FoMod's and other installers using a tick box system, but the key requirement is any and all optionals can be used.

Name the variants name is also required to tell you what the numbers represent.

Combining the two selective choices, means even the most complicated FoMods, can be easilly installed as separate mods

In the simple example used I show a two tiered selection for clarity, no limit exists on the number of tiers that are used.

This is the case for an optional component with three alternatives for that one optional choice.

So for the TiaM example, I chose to show the second listed option and the third alternative choice for that option;

TiaM - This is a Mod - Core - TiaM v1.2.12 Beta - Opt-2 Alt-3 Added Content Variant
 
Next (Still more to come), is whether the Mod has an installer, noted by the type FoMod. BaIn, etc. Though usually, when used, installers include all the variants, it's used instead of the variants section in most cases, but not always, so it's listed here in those cases. Showing an installer is used is vital if Installers are used with any multi-profile system, different profiles can have different requirements, the FoMod must be reinstalled in these cases. The Alternative is to separate the Installer into separate mods, easier than most would think, most installers are already split into the appropriate folders. Sometimes rearrangement is required, but mostly renaming the folders and moving them to the mod folder is all that's required. Then of course they are no longer an installer, but by simply activating each submod as required, it makes using them in mult-profile systems much easier;
TiaM - This is a Mod - Core - TiaM v1.2.12 Beta - Opt-2 Alt-3 Added Content Variant - FoMod
 
Next (No, there's even more after this), is the date of release, if unknown the last file mades date is used, again shouldn't be required but some mods are updated as the same version.
Occaisonally this is the only indication the files are different. No name or version number has changed;
TiaM - This is a Mod - Core - TiaM v1.2.12 Beta - Opt-2 Alt-3 Added Content Variant - FoMod [15-12-23]
 
Next (Will this never end) comes the author(s) name(s);
TiaM - This is a Mod - Core - TiaM v1.2.12 Beta - Opt-2 Alt-3 Added Content Variant - FoMod [15-12-23] by Uhuru N'Uru
 
 
Next (is that the last one I see below), comes all the requirements for that file listed separated by a + sign;
TiaM - This is a Mod - Core - TiaM v1.2.12 Beta - Opt-2 Alt-3 Added Content Variant - FoMod [15-12-23] by Uhuru N'Uru {R+TiaM Core}
 
Next (Finally, done with the "Next" thing), comes the site page number
For the Nexus I just use the number, for LL I use S to indicate the Support Forum page and D to indicate the Dowload page, additionally the requirements can have the mods site number for the requirement, usually I omit the number when its the same mod;
TiaM - This is a Mod - Core - TiaM v1.2.12 Beta - Opt-2 Alt-3 Added Content Variant - FoMod [15-12-23] by Uhuru N'Uru {R+TiaM Core=D9999}=S9999=D9999

 

I contract the information for the Mod name, usually when only the latest version is being used omiiting the version. The mod for the above file would be named;

TiaM - This is a Mod - Core - TiaM - Opt-2 Alt-3 Added Content Variant - FoMod

 

That takes much longer to explain/learn than it does to use it. Everything is optional, but I've found each one is required at some point, with an heavily modded multi-profile setup. I repackage most mods for my requirements and find this naming strucure is required, for me to make sense of the many mod files I have. Some are for specific profiles, but most are organised for easy multi-profile management. To MO a mod is a folder in MO's own Mods folder. That can be used to organize mods for ease of use in MO's multi-profile priority lists, by separating the optional parts from the core files that all parts need.
 
Such complicated management takes more time to setup, so splitting rapidly changing mods may not be worth it, most are established and rarely change though, these I find worth the effort, up front. Reaping the benefits when I rapidly switch profiles, ready to play, without having to update FoMod's to match the new setup, when required. I also use profile specific Bashed Patches, SkSE changes, merge patches, both TES5Edit's general patch without the levelling sections (Bashed Patch does those better) and Mator's TES5Edit mod merging script, though now he has the Merge Plugins standalone mod merger and Mator Smash, a bashed Patch replacement, I've never tried either of them yet.
 

Original Bashed Pratch Standalone replacer, the correct latest version

[WIP] Mator Smash - Works in Progress - AFK Mods

Later thread
[WIP] Mator Smash - Beta Testing - Works in Progress - AFK Mods

 

Leads to the file, which I've only just found and is the latest version, this appears to be a TES5Edit script, but I've not even read the page properly yet.

This is what I get for posting without RTFM, this is the older mod  the above standalone is the latest version
Mator Smash - a TES5Edit script by matortheeternal - Beta testing - Skyrim Mod Talk - The Nexus Forums

 

The mod merging standalone
[WIP] Merge Plugins Standalone {PUBLIC BETA}
 

Whatever naming structure is set as the standard, it must be optional. With at most, only the mods site codes being required.
The above is my own naming structure, the standard should emphasise clear and precise naming for ease of modding is the goal, not following my method or any other specific method. The examples should be just that, examples of good naming, not hard rules.

 

The site codes system can be used with or without good naming practise, it requires no site changes to impliment and would make finding linked files much easier.