I only used SCMDraft.
After the damage was done I was able to repair a bit of it in starforge. But up until that point it was only SCMDraft.
ADDITION:
More info:
I used multiple versions of SCMD.
I used the latest version. The version before that you posted in the shoutbox and the version before that with regular trig edit.
I used classic trig edit.
I messed with the strings agressivly.
ADDITION:
QUOTE(Gigins @ Dec 1 2006, 06:52 AM)
I'm not saying it's perfect. I'm saying if you have saved your map in SF before, it's obviously SF fault.
[right][snapback]597654[/snapback][/right]
DEAD, stop being a huge fanboy. Stuff can go wrong that is not "obviously SF's fault".
I might have opened and closed the map with SF at some point (trying to give units negative hp or something), but I'd been using SCMD for quite a while when that happened. The trouble definitely started with SCMD.
ADDITION:
I think one of the problems is that I use string recycling far more aggressively than most people. Unlike SF SCMD doesn't encourage string recycling as much. You need to fill in the same string twice instead of selecting a string from a list.
In short, I'm not sure if a bug exists, but I would tend to think that string recycling is extremely under tested.
ADDITION:
QUOTE(spinesheath @ Nov 30 2006, 01:28 AM)
Can't help you any more but tell you that I will release a working version of my Editor by the end of the year which can fix any STR section, no matter which program corrupted it. Might be some work, since it's intentionally non-automatic (you already saw what automatized string recycling can do to your STR section), but is certainly possible.
[right][snapback]597117[/snapback][/right]
That type of thing wouldn't help, sorry.
It's not that the string section was corrupted, just mistreated. Triggers pointed to wrong strings, strings deleted is pretty much it.