Vote for 'Separate' :up:

I vote combined. Combining into one JSGME doesn't have to be complicated, it can still retain some simplicity. For the Command and Conquer game series I've been using a program called TibEd. While not a mod enabler (more of a mod creator) the interface is quite simple when selecting the game you want to work with. It might be worth a look to get an idea for a beta.

As the old saying goes, "If it aint broke...." Separate is fine. Thanks for your great utility! :up:

Separate works fine for me, but I really like skwasjer's idea best.

I voted separate, but mainly because I'm a luddite when it comes to learning programs. In case you don't remember I actually had problems understanding the original JSGME, and posted years ago saying I didn't use it for that reason. And let's not remind me of my huge faux pas over SH3 Commander's 'Update' function!:oops:

I would probably sooner or later learn to love a combined version, but for now I'm thoroughly enjoying it the way it is.

And as for this:
Gee, I'd have to have it installed in roughly 100 games before it equalled the size of SH3 with GWX. I think I can live with that. The only downside for me is having a separate icon on the desktop for each install, and so far I only have it in SH3 and SH4, so it doesn't bother me a bit.:sunny:

Another advantage to seperate installation is that mega-mod builders can pre-bundle it with their mega-mod.

Personally, I don't mind paying 570kb for that extra convenience...

I voted for "combined" but the alternative is still fine for me too.
Thanks anyway JScones. :yeah:

I always subscribe to the K.I.S.S. theory. :D

aka separate. :yep:

:up: my vote goes to seperated version :woot:

Love your programs.:up: I'd keep it separate as it avoids possible confusion over which game has what mod(s).

The separate version does work well, but I always wished you could reside the mod folder in a different location, so that leans toward central install :hmmm:

Separate works for me also. Less confusion when things get a bit blurry late at night.

I like the combined idea.
Skwasjer's thoughts are great on this.
Carotio makes a valid point also.
The footprint may be small but each install of the MODS
does an offset that defeats the small footprint.
Plus any upgrade to JSGME or any MODS
would be much easier and quicker.

But I'm happy we have what we have so I'll not complain.
:salute:

I think combined the way that Skwasjer described would be great as I already am using it on SHIII, SHIV, Star Trek Armada II and Starfleet Command III. One update is much easier than four or five or more which I will have shortly.

I like Skwasjer's idea too. The best of both worlds. And that's also why I haven't voted. I like the mods and their backups to remain in the individual game folders. But I like a single JSGME application that administrates those MODS-folders.

I cant imagine the grief that would unfold if the drive containing the 'MegaMotherload'-Mods folder would crash. That would kill (or atleast allow no further mod-changes to) all games that get modded files from there. And would take longer transfer-wise if the files had to be moved between 2 physical harddrive units. (and more chance of curruption) Or in a Bernard-moment I put mod-files from one game accidentally into anothers mod-area.

The size of the JSGME application (the odd 500kb or so) is of no issue to me in this day and age of plenty of GBs. But needing to remember which game uses a JSGME application or has not, maintaining easy accessible shortcuts to all those individual JSGME exes, has prevented me from making more use of it.

Centralise mod-management (just the application), but seperate mod-storage/backup.

If it aint broke don't fix it...I onlt have a few installations of it. Seperate is just fine with me.:)

With less than two days left to vote, your collective preference so far seems pretty clear to me. I'm certainly not complaining as it's work I no longer have to think about.

I toyed with this idea a while ago (when I first implemented the installer), but the words I bolded above stopped me from pursuing it with any seriousness. SH3Cmdr used to allow pointing to different locations through users modifying the shortcut (admittedly not in exactly the same way). The fact that it no longer does says a lot to me about avoiding the reliance on user-modifiable shortcuts in the future.

I also fear that incorporating this approach into JSGME will lead to file integrity problems through people forgetting to disable all mods across all games before updating the central exe installation (in instances where such action is required when installing an updated release). With this approach we go from a one-to-one relationship between the engine and the game to a one-to-many relationship, with the management of the relationship left solely to the user and their ability to maintain shortcuts correctly.

I know you suggested making it an option (perhaps even an "advanced" option), but TBH my preference is to keep everything together as IMHO that better aligns with the KISS principle...and limits the possibility of user snafu.

Separate for me.

If it aint broke, don't fix it! Keep it as is!:up:

Separate......works just fine http://www.psionguild.org/forums/ima...s/thumbsup.gif