Digging the new icon as well!

Well, give to end users the possibility to install / unistall mods with no pain.... 

It took me awhile to figure this out. What you do is the following:

This is for your improved faction color mod

First get your zip file with the mod

save this file

https://dl.dropbox.com/u/8654092/Configuration/Improved%20Faction%20Colors%20v3-13-v3.configuration.femm

as configuration.femm and place it in the root directory of your zip file.

so it has your configuration.femm file and the directories that contain your mod.

You should then be good to go.

Ops!  Sorry,  too tired to undertand nd a simple question 

Added

Manual for configuration.femm (work in progress)

Good work.

The XML is easy enough to figure out, however the bit that is confusing (to me anyway) is what to do with the files once you've created them. 

You need to put that somewhere in you explanation, or in the OP.

mqpiffle, Glazunov1  Look here 

Looks good.  Thanks!

...now we'll just wait for the people who show up and complain about how difficult it is to expand an archive and create a new one of a different type out of its contents.  Could take oh, two button presses.  Maybe three.

Should we use these comma to ensure that required items are installed, or can we leave them off of these items that are already flagged as required?

Why mantain this two similar configuration possibility

in this case

<Module>
           <name>Test</name>
           <description>Test description </description>
           <item>2,5,8</item>
<Module>

<item>
    <id>2</id>
    <type>MODS</type>
    <category>Folder</category>
    <name>Test</name>
    <destination></destination>
    <required>0</required>
    <requirements></requirements>          
</item>

the user see one module; the program install 3 item

in this case

<Module>
           <name>Test1</name>
           <description>Test description </description>
           <item>2</item>
<Module>

<Module>
           <name>Test2</name>
           <description>Test description </description>
           <item>5</item>
<Module>

<item>
    <id>2</id>
    <type>MODS</type>
    <category>Folder</category>
    <name>Test</name>
    <destination></destination>
    <required>0</required>
    <requirements>5,8</requirements>          
</item>

<item>
    <id>5</id>
    <type>MODS</type>
    <category>Folder</category>
    <name>Test</name>
    <destination></destination>
    <required>0</required>
    <requirements></requirements>          
</item>

the user see 2 module, selecting module Test1 also select module Test2 (deselecting Test2 also deselect Test1); the program install item 2,5 and 8

If 8 is not a module, insert it into module item or in item requirements is the same; if both inserted, double installation of that item (not a problem, only a loss of time)!

[edit] In the second case, the user can select and install only Test2

Not really something I would find useful. Plus extra files in the archive confuses manual installers.

I built a version for my GinsuKnives mod, but there's one issue -- Ginsu uses the mods/gfx folder for some image files.  No matter how I put them there, the entire mod/gfx folder is removed when the mod is uninstalled.  Is this an assumed risk?