Battlekruser I'll thank you not to say stupid

like that again. Jumping to wild conclusions about SCM Draft 2 corrupting your triggers just because it doesn't edit them is stupid. I tested that out myself, it didn't corrupt the triggers on any of the maps I used.
As for using StarForge for isometric terrain, it doesn't even work the same way at all. I have heard that StarForge doesn't even create an ISOM section in the map when you use it, so how could it possibly be doing it the same way we should all know and love. StarForge is better for custom terrain styles, like sky scrapers and some other stuff I have seen. It can create custom palettes which is very much like copy and paste so you can quickly make a building. But in the end, you still need SCM Draft 2 to fix all the of stuff StarForge screwed up. Neither editor is perfect. The difference is, if you are using StarForge, you need SCM Draft 2 to stop it from ruining your map; however, if you are using SCM Draft 2, you need StarForge to do certain fancy things, not to fix your map because an editor destroyed it.
EDIT: ... crud. SCM Draft 2 appears to cause one of the same problems StarForge does, the save error. I never had this problem before, but when I closed a map I was testing on, there it was. So in the end you need SCM Draft 2, StarForge, and WinMPQ (including the innumerable files WinMPQ requires) in order to keep your map in tip top shape. Not to mention you then need GUEdit (which then requires the correct version of Java Runtime) or SCM Toolkit (which I _THINK_ _MIGHT_ require MPQView) to change player colors, and SC X-tra to do any normal stuff. I guess you just need A LOT of editors...