Welcome my dear moder, I have something that might peak your interest.

I present to you:

The Manifest Watcher MK 0.8

So, what is this about?

This tool will keep checking the selected manifest (-s) for the selected mod(-s) every secound

and update it if needed.

The system works this way:

The build manifest will be based on the original expansion manifest - the entries in the original manifest that aren't in the mod manifest (if there is one) + the files in the gameinfo/Galaxy/Window folder which already aren't in the original manifest.

This means that total conversion mods which might only need some files from the original game will keep those in the future manifests without getting all the other stuff, etc.  

Select the expansion, version and mod to watch and right click on the Active Watchers box to add or remove an extension/manifest to watch. Note skyboxes aren't supported since they use the .mesh extension.

Notice about test version:

Now the test part isn't there without reason.

First make a backup to ensure that nothing will be lost.

Secound, the original manifests are based on the files in your installation folder.

Note: Since there have been some downloads since i made the link in the other thread I thought I would leave a notice on this part. Aparently the problem lies in it basing the "outside files" on all of the files in the install folder rather then on the manifests. A fix might come later depending on the ease of fix.

Since this only happens when you don't already have a manifest in your mod, a quick way to avoid the problem is to copy the one from entrenchment or diplomacy (if diplomacy does not have one use the one from entrenchment). They are already in txt so there will be no need to convert  them.

Apparently there are 4 entity files in the entrenchment folder which belongs to diplomacy (haven't identified them yet), but they don't cause any problems since they aren't included in the manifest, I would want to know if this is only on my computer, or also so on others. You can check by renaming the manifest for your mod (entrenchment version), the watcher should make a manifest with 4 more files then the original. If you activate the mod in the entrenchment dev.exe you should get a bin error and an enum not found error.

Third: the test version includes another window named the Stalker, which is a window for each watcher showing what actions is done, incase there should be some oddities (window text reflects the watcher it is stalking).

The stalker also tell how long an update takes incase lower performance systems should take longer (I would like to know if that is the case). The first update will fill up the "inside" manifest, the increase in time that the stalker shows is mostly because the list box (the one showing the updates) is beeing constantly updated for each entry, the actuall process only takes a few ms (millisecounds = 0.001 secound). A tick is a smaller unit of measuring, its "value" can differ for each system, so comparing them can be hard since I haven't included the frequancy of each tick to be showed.

In the test version each update is done every 5 secound, in the final version the interval will be 1 secound. 

Not yet implemented:

Relations - make manifests based on several mods

Build in original manifests and defoult path

Unknown bug fixes

File association - watch a manifest by simply double-clicking on it

And before I forget it here is the download link:

Required to run the program:

.Net Framework 4.0

The program, save the file whereever you want and double click it to run it.

Manifest Watcher MK 0.8