If you are going to wipe the mod directory, please put a warning popup for that. I'm sure a lot of people would hate to accidentally delete their mod directories. The same goes for the potential to "restore" the installation directory as well, since there are a lot of people tweaking things in the installation folder.

If this is something you plan on continuing to develop, I will change the next SW release to use your program after you release it (if the player wants to, obviously won't be forced). This is really great and I think would help people install and see incompatibilities and so on.

Ten thumbs up from me.

Another small request, how the mod manager will handle incompatibilities. Right now it looks like I have to add each version of the other mods that my own mod is not compatible with? That's a hassle. For example, ALL Master's Affliction mods are incompatible with ALL Stormworld mods, so I don't want to have to update that bit every time they or I release a new one.

I'm on my way to think about a good method to handle incompatibilities.

At the moment the section    

<ModCompatibility>

contain the tag

<NoCompatibility>1</NoCompatibility>

to tell the program that this MOD is NOT compatible at all (Master's Affliction).

the <item> section is not used at the moment, is a work in progress on how handle mod interaction (if mod X is compatible with mod Y but nod mod Z....)

Really nice work

I have something for the"what is dreamed" list, interface mods basically even if two mods are incompatible there might one day be a mod that creates an interface between the two so they can work together, changing a few files here and there etc.

Its just that while you are thinking on how compatibility is defined between mods that might be something to keep in mind

Uhm...

well, file exension is not a problem as long as the content is valid xml.

I'm thinking about removing the format specification for the zip file..with some minor change on my logic i can use the archive as they are now (adding only the configuration file).

rumble rumble klang klang...gears turning 

 I thought another thing. Dependencies. I use those a lot in my mod. For example Stormworld_Quests requires Stormworld_ExpandedFactions_Champions. Something to support that would be great.

Edit: Looks like you already have it in the xml. Never mind!

Development Update

What is done (with some bug here and there):

• dependecies management (like, in Stormworld, selecting Quest also select Expandend Faction and Reliquary, deselecting Expanding Faction also deselect Quest)
• backup management (for file modified in the FE installation direcotry); backup file are stored in zip archive
  
• before mod installation the program delete all MOD directory contents (after user warning and approval)
• before mod installation the program delete all MAPS directory contents (after user warning and approval)
• basic mod conflict management  (only total incompatibility is managed like Master's Affliction)
• minimun impact on modder for mod distribution ("configuration.femm" is the only file needed, no change to actual archive structure)

What is under bug hunting (is done, but with major bug that do not allow a correct execution)

• mod installation

what is under reengineering (some code written...was garbage...starting again from scratch)

• before mod installation the program restore backup in FE install directory (restore only file modified by the mod after user warning and approval)
• complex mod conflict management
  

what is dreamed:

• do not wipe MOD direcotry (delete only mod related file)
• wizard to create configuration file
• bug free program
• idea are welcome!

if all goes well (bug on mod installation solved) I will release an alpha version tomorrow

Ciao

At the moment is:

Program asks: "Do you want to delete all the content in  <MODS or MAPS> directory?"

Yes - program wipes and proceeds

No - program proceeds (no wipe)

As i'm well known to make bad user interaction option i definitively switch to the Yes\No\Ignore option

(i think this last sentence is written in a bad english...sorry for that)

For the description, you mean some automatic runtime mechanism? Obviously is possible to insert all the information needed in the xml description tag

Excellent idea.  When do you expect to have something you want to share with others?

If I can solve a few very annoying bugs, tomorrow is the day (is 22/11 00:06 in Italy, so at least 24 hour from now)

yes, c#, .NET framework 4

FIRST: this is an alpha version, with bugs. At this point, i suggest you to use temporary folder for installing core file and mods files (i.e.: create and empty "C:\tmp\FallenEnchantress" where install core file, "C:\tmp\MODS" for mods file and "C:\tmp\MAPS" for maps file) and do some installation test. After that, backup all your FE data (core and mods file), and use real path for your installation.

Alpha release is ready, install from here

At the moment I've prepared configuration file for this mod:

• Stormworld 1.5j
• Improved Faction Color 3
• Master's affliction 1.02.016

download the file, rename in "configuration.femm" and insert into zip archive

For Master's affliction you need to recreate the archive in zip format (do not rename in .zip!)

For Stormworld, you need to extract the archive "Stormworld_Rivermod\TerrainTypes.rar" in the folder "Stormworld_Rivermod_TerrainTypes" (in the root of the zip archive)

Known bug:

1. no user manual
2. no check box on root node on start up (they magically appear after checking a child node)
3. sometimes tree expand/collapse wrongly
4. backup of MODS file create the file in a directory with the same name
5. zip backup have problem and restore backup of core file does not work
6. Progress bar 'tilt'

I'll put up a full Stormworld release with a config file in a bit. That configuration doesn't look right for the rivermod.