WARNING!

The CutScenesOff.vbs script makes changes that could have compatibility problems with FLMM-based mods that modify SP cutscenes. Do NOT use it before installing a mod. If you have used it and wish to install a mod, run CutScenesOn.vbs before attempting to install the mod.

There are several mods that turn cutscenes on and off, and being full mods they are a bit more exciting than this set of scripts; I recommend you NOT use this unless you feel comfortable with direct mass modifications to your Freelancer INI files that could theoretically force you to completely reinstall Freelancer.

If you aren't scared off yet, keep reading. :)

What Do The Scripts Do?
CutScenesOff turns off the ingame cut-scenes, CutScenesOn turns them back on. The cut scenes are the cinematic sequences that happen when you are at a base.

The CutScenesOn and CutScenesOff scripts were actually inspired by the batch files that accompany portions of FLRebalance - credit for the general idea goes to JoeBoomz, I believe. I'll explain how it works below, but for people who just want to use it, here's the simple bit:

(1) Make sure you have Freelancer installed and are running Windows 2000/XP/2003 (your mileage may vary on other systems).

(2) To turn off all of the cutscenes in standard SP, double-click the file CutScenesOff.vbs. When it finishes running, it will pop up a message that says "Made 111 edits turning cutscenes OFF".

(3) To turn the cutscenes back on, run CutScenesOn.vbs. When it's done, it shows a slightly different message: "Made 111 edits turning cutscenes ON".

Why This Script?
Primarily because it works with almost any mod already installed. You can turn off the standard SP cutscenes, and in fact if someone has added custom missions but they use standard xxxnrml.ini and xxxoffer.ini filenames, it will handle them as well.
It also doesn't cause problems if you run accidentally run CutScenesOff 5 times in a row, for example - no new changes will happen.

How Does it Work?
Both scripts just list all files anywhere under Data\Missions\ whose names end in nrml.ini or ffer.ini - all the scripted actions are handled in those files.
When CutScenesOff finds these files, it reads them line by line looking for beginning "action", "offer", "accept", and "decline" statements, and writes them back with a ";" before them so the lines are still present but commented out.

CutScenesOn looks instead for ";action", ";offer"... and you get the idea. When it finds them, it trims off the initial ";" and writes the line back so it is no longer commented out.

ABOUT SCRIPT BLOCKERS
Many virus scanners and Internet safety tools will complain about WSH scripts. Although this is an inconvenience for scripters, it's generally a good idea for users. If the same thing always happened for new IE plugins and random executables people get, the world would probably be a better place.
In any case, scripts like this are plain text files; when you get them, you have the actual "program" source code and can read the contents if you're so inclined to reassure yourself that they don't do anything malicious. You can usually run a script by simply confirming to your protection tool that you want to run this script, this time.
I suggest you DO NOT disable these script warnings unless you know exactly what you are doing with scripts and how it affects your overall exposure. It usually only takes an extra click or 2 to get through them when you do want to run a script.

Bugs, suggestions, email alexangelopoulos@hotmail.com