mod metadata

[Searcher7]

I'm certain this must have been discussed SOMEWHERE, but I can't find anything related to TES, or Skyrim in particular.

 

Problem: Successful Mod installation (IMHO) is problematic at best. Currently, it seems that more-or-less intelligent "mod managers" are the preferred solution. Different "installer" mechanisms (and logic) are used amongst the different mod managers making mod management even more confusing to new/casual gamers, who experience the most problems with mods.

 

Idea: Put the install requirements with a mod itself via a "standardized" mod metadata file. A mod manager/mod utility could parse that file and automate the install and/or require user input.

 

For instance, mod dependencies could be enforced, or at least presented to the user, during installs ("This mod requires DLCxxxx or XXXX.esp..."). Post facto requirements (ie, FNIS generator) could be automated to ensure completion. INI files could be updated/replaced with required entries (ie, ENB). From the number of "problem" threads on places like Nexus, it is obvious that some install information beyond correct directory structure and load order (even THAT is problematic) is needed for today's complex mod installs. In particular, things like STEP recommended mod adjustments could be implemented automatically with a package metadata file.

 

I'm an old-school, manual mod installer. 7-zip is my goto installer for manually downloaded mods and I actually peruse README files. I cannot say what should be included in a metadata file; mod authors would need to come to some agreement as to what information an auto-installer would need to successfully install their mods. Something as simple as an HTA utility could populate an XML file, for instance, with the agreed upon metadata prior to mod release.

 

Thoughts?

 

EDIT - Spelling errors

[DoubleYou]

Isn't this exactly what fomods do?

[Aiyen]

Yeah?

 

I would not say that its the mod managers etc. that have problems, rather it is the "new/casual" players who think its as easy as the Steam workshop tries to make it look. But the reality is that it is not! You have to think and do a bit of work to alter the game.

Almost all mods have clear requirements, and compatibility sections (up to a point), but it requires that people actually read them.

[Searcher7]

Isn't this exactly what fomods do?

 

I knew it was too simple an idea.

 

I don't understand why this hasn't caught on more than it has in the Skyrim community, or with mod authors. MOST problems that I help users with are solved by simple install tweaks or are dependency issues (You NEED Dragonborn..., You need the XXX Dragonborn Patch..., The patch goes AFTER...).

 

Thanks for pointing it out. I'll look around and see if there are some particular reasons why it isn't a more popular mod format.

[Searcher7]

Yeah?

 

I would not say that its the mod managers etc. that have problems, rather it is the "new/casual" players who think its as easy as the Steam workshop tries to make it look. But the reality is that it is not! You have to think and do a bit of work to alter the game.

Almost all mods have clear requirements, and compatibility sections (up to a point), but it requires that people actually read them.

 

I'm a support technician and long ago gave up any hope that users would become familiar with either their computer or the programs on it. Asking a user to follow a README is wishful thinking. The real gamers are different; they'll work to get things running. But most will not.

 

I'm not blaming the MM's either; they do well with what they get. I actually do use Wrye Bash with Oblivion and a little bit with Skyrim, and have tried NMM (nice uninstaller). I'm just a control freak at heart.

 

BOSS was a Godsend, and so is STEP. But the forums are still full of problems that could be solved by simply using BOSS or following STEP advice. Too few do, and that agrees with my personal experience at work.

 

DoubleYou pointed out the fomod/omod; I knew about them but was unaware of how they worked. I had thought they just used a fomm/obmm script for a brute force install and did not know they had an associated XML installation guide.

 

Most users will do one double-click, then call tech support or post in a forum if things don't work. I'm just trying to figure out how to make that one double-click more successful for them. In the long run, its selfish; I want to encourage modders for my own benefit. The easier it is to successfully install and use a mod, the more popular it might be, the more endorsements it might get, the more encouragement for the author to keep going, ...