Structuring the mod before writing the FOMOD
BeermotorWB opened this issue · 2 comments
First, thanks for writing this. I've been looking for a solid set of documentation for FOMOD for a while.
I'd like to help out by contributing language (or a section) on how to structure the mod before writing the FOMOD XML since it kills three birds with one stone:
- It is an incredibly simple concept and makes logically following the structure, therefore writing the XML, dramatically easier
- It makes the mod universally compatible with all mod managers and installation methods.
- we won't end up with thousands of mods that cannot be installed anymore like what happened with the OMOD fiasco that engendered the BAIN structure standard in the first place. Things are starting to get eerily similar to how they were in 2008 with all of the "folder salad" mods being released lately.
I'm in the process of writing a BAIN reference for the Wrye Bash project so I already have most of it written, I'd just have to adjust the language a bit to fit the audience.
Mhmm, that is one thing I debated about including since it's not strictly fomod. I sort of talked about/gave an example at the end of A Step Forward but it's obviously not the same thing.
Maybe include in Tips and Tricks? See where you can make it fit. I await your pull request!
Excellent. Yes that's a perfect place for it. Give me a few days to clean everything up and I'll send you a PR.
Cheers