Quote:
Originally Posted by JScones
Anyway, large mod developers can overcome the whole issue by providing a robust installation routine which automatically provides the ability for users to install the mod either straight into SH3 or JSGME.
|
Well from what I understand the point of putting together super mod (like grey wolves) was to create a simple one time install for the average joe that doesn't want to use jsgme or mess with editing and configuring mods. It wasn't made to be a standard install for the intention of jsgme users to add additional mods.
That was my main disappointment with Grey Wolves that it it didn't come in a modular format for those of us that use jsgme to keep mods up to date when new mods come out. But, like it says in documentation the purpose of it was to create a simple install so everyone has a chance to enjoy all the popular mods that are currently out there. The downside to this is that it is dated. Because as new mods come out you will always have this problem as you are describing of having to back track and fix edits, config files, etc which is why most solutions even for the installation of grey wolves is to start with a "fresh" vanilla install.
The issue isn't jsgme to change its ways....the issue is for super mod makers if they intend to cater to jsgme users is to break it up into a modular format. So, when a new mod or alternative mod comes out that changes a particular behavior of something already installed it can then be kicked back to the vanilla install to put in the new mod.
The standard should be JSGME modules and the standard vanilla sh3 installation. Not, a supermod like Greywolves. Greywolves can't be a standard because it has to much extra stuff that is not needed. A standard install is like RUB where it only changes a behavior of one particular aspect of the game and nothing else or a collection of fixes that patched broken behaviors...a standard should be a unofficial patch like captain america's gauge fix...these are standards...because they don't need to be changed later....not compilations of textures, music, campaigns, user interfaces, map tools, and other extra stuff that will be changed consistently by each personal preference anyway....these should only be offered as modules as a standard by supermod makers so they can be swapped easily with jsgme based on the individual tastes...
My biggest problem I have with mod makers is they don't go by standards. You always see somone add extra features or fixes they like in addition to the mod the user origianlly wanted to install. Like if you wanted to install a ship it would add some fix to a plane or to the weather....something completelty unrelated...just because the mod maker thought this was a nice fix based on his assumptions that his install is what everyone is using.....this stuff needs to be broken up into modules so as they outdate or becoem more advanced they can easily be replaced...plane and simple...that way the problem and instructions can simply be written for the configuration of that specific module and not the 4 different uber mods people are using as supposed standards...people don't have time to write lengthy install instructions for what various supermod needs...if supermods are going to modified they need to be broken up into a modular format that can easily be replaced.