Some thoughts on some more features. One thing that really sucks about the modding with new textures is you have to either install them in the actual game data folder over the existing ones, or copy the whole textures from there (1 gig) to your mod folder and then copy in your new textures.

I was thinking about making the installer have a button near the button that is labeled "Components...". Clicking this button displays a dialog to the end-user and lists the aspects of the mod they wish to install.

Really though, what could a user choose to install or not? The only thing I can really think of whole textures issue. What other optional components? Perhaps new sounds or something. Maybe someone can come up with some ideas.

The problem that may be run into though is (and I may be wrong in aspects of this) your mod will have a value assigned to based on an algorithm compiled against it when you load the mod in the game. This is probably done to ensure when you are playing in multiplayer you are using the same mod as someone else and others don't hack them. I don't know what makes up this number though (do they only calculate the data files? or do meshes affect it? etc...) So do optionally installing other sound or graphics files effect it? If I install the textures to the base game, does this make multiplayer unplayable unless I play against someone who has done the same thing?

What I was thinking of doing is breaking the XML out into sub sections. The Actions would have sub groups which define the Component to install and one of these would have to be labeled MAIN. This component is always installed and you cannot turn it off. The optional stuff my be on by default but users could click that [Components...] button and turn them off. Additionally you could code the XML to turn off specific features when one is turned on. This would allow the user to see two components related to where textures are installed, and choose between them
1) [X] Install textures to mod directory (Will use 1 GB+ of space)
2) [X] Install textures to game directory (Will affect main game and may affect other mods)

If 1 is chosen, 2 is turned off, and if 2 is chosen, 1 is turned off...

Thoughts?

Sample Xml:

<Install>
    <Component name="main">
        <Actions>
            <copyFolder.... />
            <copyFile .... />
        </Actions>
    </Component>
    <Component name="texturesMod" default="on" displayText="Install textures to mod directory (Will use 1 GB+ of space)">
        <Actions>
            <copyFolder.... />
            <copyFile .... />
        </Actions>
        <Restrict id="texturesGame" />
    </Component>

    <Component name="texturesGame" default="on" displayText="Install textures to game directory (Will affect main game and may affect other mods)">
        <Actions>
            <copyFolder.... />
            <copyFile .... />
        </Actions>
        <Restrict id="texturesMod" />
    </Component>
</Install>

 

Yah 1.3 is here! Some people had asked me to put on an option (that I originally proposed) to allow the user to choose if they would like to install textures to the game directory or the mod directory. Well I decided against that because I felt this was too much of an important flaw in the modding system that the developers would eventually address it and address it soon. And my predication came true!

Patch 1.3


If anyone has been using the mod installer they should upgrade their XML to not:
1) Copy the new textures into the game folder
2) Copy the game textures into the mod folder

I'm still looking for feedback from people who've used the installer. I haven't been doing any new features on it because no one has requested any features and I've been working on the StringEditor.

Indeed sadly I never realised the download was public otherwise DS may have been using this for quite some time. I'll take a look in to using this for the next release

EDIT:
Interestingly enough trying to just run the file without messing causes the error:

Folder Missing: C:\Program Files\Stardock\TotalGaming\Sins of a Solar Empire

Which ofcourse these days with impulse being around doesnt exist, and should be something similar to depending on the OS bit type:
C:\Program Files\Stardock Games\Sins of a Solar Empire
C:\Program Files (x86)\Stardock Games\Sins of a Solar Empire

Interesting how the installer actually checks for the games installation quite odd that.

To add to the edit:

Im using Windows 7 64bit and couldnt find any reference to that folder I mentioned above anywhere in my registry.

Yeah thanks for confirming those Harpo it was where I was looking already, sadly they all point to the correct directories so its not an install issue my end >.<

Oh also minor suggestion here, could you setup a default folder for all the extra files that users dont need to use and mess with just to save confusion.

Example:
SinsModInstaller.exe
./setup/backdrop.png
./setup/mod.xml
./setup/mod.xsd
./setup/sins_logo.png
./setup/SinsModInstaller.pdb

 

Awesome!    Hope to be able to test it out soon (though not too soon, as I'm going on holiday va-ca)!

Thinking about it... that Sins Install Directory path was only utilized with textures in original Sins, wasn't it?  Unless there's some other use for it, that code could probably be removed entirely.  The Sins User Directory seems to be all that the installer needs to know.

That's a neat idea, Thraka.  However, for the auto-update to work as you describe, every mod would need to have it's own publicly-accessible web server so the program could compare the currently-installed version with the newest available version.  Seeing how most mods are hosted on Filefront/Mediafire, though, it doesn't seem many mods have their own dedicated web servers.  (If anyone can think of a way around that requirement, please do advise!)

I can see the use of performing an actual registered-installation so that a user could easily uninstall the mods.  But I'm not sure about that auto-update.  Incorporating seperate methods of installing vs. patching would certainly be a help, though!  Also, how about a final option that asks whether to activate the mod and/or start the appropriate version of SoaSE?  (Just to be safe, it may be better to activate it *instead* of any already-activated mods, rather than activating it alongside.)

About WPF: I thought that was a rather recent Windows technology.  Will your installer still work on WinXP?

And one small thing... the part of the installer's window just below the title bar doesn't respect Windows colors.  For example, I've got Windows set to white-text on black-windows, and this is how the installer looks to me:

I didn't realize this at first, but evidently there's supposed to be some text in that white area too, which isn't showing because my text color is set to white.

Yeah. I'd absolutely love this because our testers screw patches up almost every week. We have our own webserver and I think most mods should, so that as a requirement isn't a big deal to me at least.

Sorry. Got sideline and forgot because of family i had much vacation time off spending with them. I'll get back into this soon.

Maybe auto patching is a better term. Someone just needs to download the full thing and run the installer. It will detect what version is already installed and follow the upgrade instructions, or just do CRC checks on the files and anything that doesn't match it updates. Don't know yet. Thats the future.