[fabianfred]

the new maps which I altered from the default ones......midway_ffb and hawaii_ffb

in the old system with a filelist I could 'stop' the 'static.ini' line from working by adding a couple of // in front of it..... and the objects appeared OK...... after we found out the problem was with the Destruction mod

now with the new system they will not appear...even if I delete the static.ini file from the MODS folder....presumably forcing it to use the default one

...anyone any ideas...or got it working normally?

...it was a pity that the destruction mod got F'd up by the 4.09bm patch....it was going to be great for ground-pounders...........and I also had managed to 'harden' the trees from too easily being damaged........something which Lal_Rone had said he was incorporating in the mod....but didn't in the version he left us when he left

[Bee]

Hi FF :wink:

Did you remove the Destruction files from your folders before you moved them across to the new Mods folder? I didn't do this with a whole lot of experimental stuff that I previously had deactivated by putting /// in front of their entries in my Filelist. All kinds of fruity things were going on

The new wrapper just loads anything that is present in the mods folder with a legitimate name. Striking them out of the filelist is no longer enough. These days we need to stick a "-" minus symbol on the front of each and every file or folder we want to disable.

[fabianfred]

yes....that destruction mod was the one causing the peoblems with the 4.09bm maps and objects......but as we know it was the static.ini which was the problem....not the ships.ini.........so I made seperate folders in the MODS folder.....with full paths to the ships.ini and one for the static.ini........... and I tried putting a - in front of the foldername......and even removing the folder completely
........the static.ini file in my original Files folder which I moved to the MODS folder had been deleted too

????