Apparently after one of the versions of my map, shortly after adding randomizer triggers for character selection(Which removing these didn't help.), every time I tried to save my map, it would come up with an error. Of course I can easily bypass this by ignoring the message and saving anyways, it doesn't crash you ingame either. Furthermore, its also doing it after a few trigger edits and if my trigger editors up and it does this, I can't bypass it at all and work done to triggers or anything at the time gets wasted. I'm quite confused at why its doing this, can anybody help me out?

Not sure about why, but re-installing it should work. Does work for me whenever I have a problem.

Its not ScmDraft2. I can open up and save any other map just fine. But if I save mine, it errors but the work done is rescuable. If it errors while Im working on triggers, work gets wasted.

Try clearing the backup database, that's what fixed it for me both times I had ScmDraft2 start crashing.

Did it crash for the same map or all maps?

I never tried other maps, and at some point I started clearing it regularly so it wouldn't happen again.

It's under Advanced at the top of the editor.

A backup database would cause a crash message when trying to save any map. If your SCMD2 was crashing for all maps, Azrael's guess is most likely correct, but since this is not the case, it must be something else.

You may have reached the string limit. Can you give us more information on your map, or post the map itself?

What the?... It won't even let me open the backup database up. It tells me something bad happened and I can do nothing more. Also it only crashs for this map, no others.

You can manually delete the backup database. It's the file in your SCMD2 folder, probably the size of a couple gigabytes. It's called "backupDB.scmdDB."

Hurray. It stopped crashing for the map. Apparently, my backup file was over 2million kbs(2GB). But why would it be crashing if the backup folder got that big? Is it because it can hold no more?

Some sort of programming oversight, just make sure to clear it every so often to avoid the same thing in the future

There's a memory leak in SCMD2's backup database. I'm guessing it times out when trying to append to a very large database, and the timeout prepares the program to shut down, hence the "Something bad has happened" message. I'm not SI, though, so I could be wrong.