I just wanted to warn everyone that using starforge and scmdraft on the same map while editing strings and such can screw your map up and make it crash when you run it. It has something to do with scmdraft recycling strings and starforge not recycling strings, something like that. Just a word of advice.

Yeah. Not to be mean or anything, but this has been know for a very, very, very long time. To fix just don't use starforge and open up scmdraft's backup database and save a previous version.

The main issue is that with the way SCM Draft recycles strings, often the issue people have is when they change a string in SF, all the strings that were recycled change as well, not just that one like they intended.

.

oh ok. I thought so, i just wanted to say it because i just had a map i was workin on for about a year now, ruined for that reason.

No problem, thanks to ScmDraft's backup database.

yeah except i disabled the backup database because it kept filling up really quickly for some reason like gigabytes of memory.

That's not normal operation. You should report this bug in the "Last call for ScmDraft" topic.

Maybe you had autosave saving too often?

Sample map? I couldn't even get a map to crash by manually editing the string section or references with a hex editor. (Invalid Scenario)