i prefer to edit my INIs with windows 3.1,save them on 5.5 floppys and sing them to sleep at night with the windows nt users manual.DLL strings i edit with my toes and a hex editor -but even i know never to close FLMM and add new files while my mod's are activated

First run through:

Tried to load the current beta build of XML Toolkit Mod, 1.3, and Chip's OpenSP Lite- my standard development environment.

XML Toolkit loaded successfully. The multithreading works beautifully- Toolkit takes quite awhile to load at this point, and now I can check email while I wait

OpenSP Lite did not load successfully. FLMM reported that "F:\temp\FLM46.tmp" doesn't exist. Dunno why it's doing that, but that's a serious "uh oh", all by itself



Second run through.

Used my "oh, crap I totally hosed FL" backup to restore every FL file to pristine, original states.

Tried to load Chips OpenSP all by itself.

Still giving an error message, saying that "FLM4D.tmp" doesn't exist. Methinks that we need to figure out why this very, very important mod doesn't work, pronto- or in the next version, let us overwrite Restart.fl and Newplayer.fl, so that we simply don't need to use it anymore (which, from a purely technical angle, would be better, although I'll be the first to say that we'll have to transmogrify Chip's nice FLMM script into a version that hacks up Restart.fl, so that we can get the same functionality).

Next, tried installing a "new" mod- the Alternative OpenSP.

FLMM claimed that the mod was installed and ready to go, but it didn't show up on the mod list. Checked the directories... and.. no mod! Oops, that could be a problem

Manually installed the mod... and it wouldn't run, either! It said that a TMP file didn't exist




Final conclusions...

1. Installation went smoothly.
2. Tests with various mod configurations did not go very well.
3. Whatever's causing this TMP file problem is a serious "uh oh" bug.
4. There may be other problems with script execution, DLL creation, etc., but this is pretty secondary at this point, these are show-stopper bugs.

Blackhole2001 : could you e-mail me your mod, so I could test it out myself? FLMM is coded in C++, using the MFC framework.

Glock36 : have you ever been able to reliably reproduce those corruption/left over files problems? If so, please let me know ASAP so I can fix them. I haven't noticed anything like that myself, and haven't received any other reports, so it'd be very hard for me to fix that without further detailed info.

Now, for the rest of you: if you had follow my instructions and posted the bug reports in the proper thread, you would have noticed that unzipping support is known to be broken and the TMP file issue is known, and both will be fixed in the next beta .

Beta 2 is out, which fixes all reported bugs and adds support for modifying Restart.fl.

Could you plz put Multithreading into the "unzipping archive" bit?
When you first run a .flmod file it unzips it, that still frezzes up

@ IGx89, this isn't a bug as such more of a quirk, one that I'm more than happy to have found.

After I posted about the probs with the "Restart.fl", I went back to editting my OSP mod. I removed the Restart file and added options into the xml script file using the same way you did for the "freshstart" mod. I only have 2 options with 4 choices each but without the savesafe line, now this is where the quirk comes in, in the past all of the mods that I've used with options only had one save folder. With this new options format I get a save folder for each option scenario (in my case thats 16 of them). The only drawback I can see is with mods like "Alternate opensp", if their options are redone to this format thats going to leave people with a heck of a lot of save folders.

@ Argh, if you read this you really need to try this out as it may remove any need to edit the Restart.fl.

-Trail- : Hmm, that's a good suggestion, but it could be tricky to code; I'll look into it though.

Bejaymac : savesafe="true" means that the mod won't change the saved game format, and thus FLMM shouldn't keep the saved games of that specific mod/options separate from other active mods. You probably individually labeled all your option elements as savesafe="false".

@ IGx89 , sorry Matt I should have checked better before I posted, just looked at the scripts for some of the mods I've got and found "savesafe=true" in beside the option tags. Guess I'm still just a part-time dabbler in xml.

Whatever it is I prefer it this way as its exactly what I need for Rebalance 3.5, as we have two options in the mod "story" and "OSP" and before I found this quirk it meant 1 save folder for both options, now I have a save folder for each option. Now you know why I've got a 40kb beast of a script file, it holds all of the non vanilla entries for Heavens gate and soon it'll have the files for prison station mitchell.

As for my OSP mod this means I no longer have to worry about deleteing or editting the restart.fl, as each option has it own restart.fl.

However I still think that "savesafe" works back to front as to me savesafe means just that, keeping my save files safe from being overwritten. If I use a mod thats "savesafe=true" then I know that my original save files are going to get overwritten by it, but if a mod is "savesafe=false" then my save files are moved to safety, but please don't change it as theres a heck of a lot of mods out there that would need changing.

Yeah, you're about 2 years too late .

What do you mean about saved games getting overwritten? A mod with savesafe=true means that saved games without the mod can be used with the mod, and vice versa; saved games shouldn't ever be getting overwritten unless the user manually does that themselves (not counting Autosave.fl, which naturally will get automatically overwritten). Or am I missing something?

Give a guy a chance I've only been moding since the end of march

In a mod that has this in the script,

<header name="Mod Name" savesafe="true">

I know that with this FLMM will leave my vanilla save files open for the new mod to use, instead of creating a new save folder for the new mod. Loosing the Autosave and all of my stats since my last save can be a pain, but the real problem is with the restart.fl, small mods can get away with using my vanilla one but any large mod with new factions will eventually leave a very corrupt autosave, as my vanilla restart doesn't have the new factions in it.

<option name="Starting system" savesafe="true">

With this it doesn't matter what option you choose as you use the same autosave for them all loosing everything you did the last time you used the mod (people are lazy, give them an autosave and they don't bother making a save game especially in an OSP mod).

If you change the "true" to "false" or remove the "savesafe" line all together, you get a save folder for every mod and one for every option config. as well. This is what I thought "savesave" meant. *one confused moder*

Beta 3 is out now! Notable changes for mod authors are LZMA support (on average, makes mod archives 40% smaller!), mod "caching", full documentation on all the new features (sectionreplace, LZMA support, mod "caching", and the new cmdline arguments), and of course bugfixes. Please test all your mods with this version (they should work, but just in case), because this beta might be announced on the front page for "public" testing if I don't get any bug reports in the next week or so.

I too have found that sometimes FLMM seems to leave things behind when used on several different mod types.
I don't have the opportunity to reproduce right now (I'm not at home) but when my mod team used to script everything that they sent in, I used to have to unscript (is that even a word?) the mod and stick it into mine as I found some files were left or altered. The result was a wipe of FLMM and FL once every 2 days or so, its not exactly a huge problem to do so and I can ensure that there are no problems then with an unclean install when bug hunting.
I too build mods only unscripted (I also find it alot easier) so would add my voice to a special version not supporting scripts.
I can't think of a good way for you to reproduce the results as I have only come across them while sticking together several mods, so I don't know the specific details.

Sorry.

True Intelligence is the ability to admit you know nothing

I don't know if it has been fixed already, but there was a minor problem in 1.31 version... when you moved Freelancer folder to a new location and deleted the previous one while mods were active, it was impossible to change Freelancer folder cause FLMM still reported that one of the mods was active. Maybe it's worth to enable an option to change Freelancer folder with active mods, adding warnings?

http://www.discoverygc.com/' Target=_Blank>Discovery Gaming

IGx89:

I've tested the latest build with XML Toolkit 1.3 (thanks for sending me the earlier pre-release candidate build btw).

It seems to work just fine. Only thing I haven't tested, and will want to test before I want to call everything "good", is whether Restart.fl mods are now working completely without problems. I'll take a look at that issue as soon as I can- this is a pretty vital new feature, if I'm going to make some of the new things I want working for WOS B2 to work