Yes, definitely. I find it annoying as well, but so far never that much annoying to actually rework the script compiler.
I would greatly appreciate it.
As for the crash, if you'd like I can send you my project.. but first I'll mess with it a bit and see if I can figure out what caused it to start crashing right away.
Than you, that would be helpful.
I found the code that was causing the engine to crash:
if (comment = null)
comment = " ";
if (sound = null)
sound = " ";
Let that be a lesson to you all:
Always check your operators.

Still seems strange that these lines would crash the whole program... seems to me the code inside the parantheses should set the variables (parameters in a method, in this case) to
null and always return true, instead of crashing WME. I haven't attempted to duplicate this in another script yet... if you get a chance maybe you could try it, and if you aren't able to duplicate it I can send you my project.
You are using WinXP, so does it mean you are getting blue screens? That's usually a driver issue. Make sure you have the latest Detonator/ForceWare drivers installed with no "dangerous" oprions turned on. It's not possible easy for an application to trigger the blue screen of death...
Yes, I'm using WinXP, and
sometimes a blue screen does flash on the screen for fraction of a second before the machine reboots. Its true this is usually a driver issue, but it only seems to happen with WM. I run dozens of other DirectX apps on a daily basis and have never had the machine just reboot itself like that. I have the latest Detonators, and I'm not using anything fancy (besides the DirectX SDK, but again, this problem started long before I installed the SDK).
To be fair, I have been seeing some other anomalies lately that are definitely not related to WM, including Explorer.exe crashes. This is bad, I know, and I will probably be formatting my system fairly soon. Perhaps you could just keep the situation in mind for now, and I'll let you know if things improve after the format.