hello all,
Reading the comments per the aftermath of the this packaging adventure, I am going to circle back and focus on the original goal of the packs. This goal is the framework.
I plan to re-release the packs as the empty framework (NO MODS INCLUDED). The framework will contain the categorization, associated vanilla DBW inis and any other requirements for various mod placement and will be maintained/updated for DBW revisions as they are released. This will then be a clean slate for users to mod DBW as they wish without the need to risk corruption of their vanilla DBW install. Of course, I will still have my personal modded packs that I will continue to evolve and nurture as I direct my own DBW install to the paths I desire; however, I will not publicly post these populated packs. Though, for others out there I will communicate via PM to make suggestions for releasing work for the ease of the user base as a whole.
Note, yesterday's release of
Monty's Desert Air Force campaign is a perfect example where a #DBW_MOD_Static_DAF would be an excellent way to distribute the campaign to allow users an easy way to layer it over a clean DBW install. Already in this case, people are reporting issues or unwillingness to edit the inis and/or gather the required mods. In this case, a Clean functional JGME pack could be created which includes the mods (with credits). Users could simply enable the pack and everything would fall into order and work. Currently, I am working on this and will likely introduce the idea to Monty.
However, as for releasing further working populated JGME mod packs as I previously have done, I believe I am retired. I simply do not want to upset the modders and risk doing things that will get me black balled. CrazyFlak was the first to call it out, and in retrospect, he is correct.
~S~
wind