Ok, so I'm working on a map with a partner, they do triggers in xtra edit and I do mine in starforge. Anyway, they gave me the map earlier today, and I went to change it.
First it gave me some weird error, the error didn't say anything but jibberish. (@^*$#&*^%$#*&^@ ect.)
When I clicked ok the map seemed fine, so I paid no heed. I went to edit the triggers, but realized soon after testing that, many of the triggers weren't working properly. After testing the triggers all over, I finally open up the backup I had of the map. I get the same error, this time I add one condition, and then take it away before saving. The triggers which worked fine before I edited the triggers are messing up now! And there was nothing changed. After more long testing I realize that it isn't recognizing any of my created units in bring conditions. They are not hallucinated or anything. I'm quite sure it has nothing to do with the triggering, because if I take out the one condition "Bring unit to location" It works. And its got nothing to do with the location its brought to, because that is centered on the unit the whole time. The location is still centered on the unit, but it's not recognizing the unit as being there. It's as if the unit were hallucinated, but it's my unit and it's not blue.
I've been testing all day and I'm almost positive it has nothing to do with triggers.
I'll pm the map if you think you could help me out, but it's a secret project (sorta) so I don't want it getting too spread out.
ADDITION:
Wow, nevermind, it had to do with unit properties. It's weird but the unit property 3 for defilers makes it undetectable by bring commands, but not hallucinated. I fixed it.
This should probably go in the Starforge section. I wouldn't really recommend using two different editors like this. If you can extract any meaningful data out of the error message it would be helpful (what about the title bar?). If you PM me the map I'll try and take a look at it.
Yeah I am 100% sure that it is not the triggering. This problem has occured with me and my friend once also. We were working on a map, started with X-tra for the triggers, then went to StarForge to make nice looking terrain, then back and forth to keep on adding in with the triggers and terrain with both of the editors. This error I think occurs because of you using to entirely differnet Editor programs. The two programs just got messed up with your map being from each one, and it cause a major glitch just like you said.

So the best way that this could be solved, is nothing. (none that I can think of) You could just stick with one editor and use that throughout your enitre project, other than that I don't have a solution. So yeah that is really annoying why it does that, especially when you are almost done with your map and it starts messing up.

So I hope that I cleared it up for you alittle bit.

Good luck with your map though Rantent, since you make badass terrain!

Ya, as I said right after posting the glitch was fixable, but I could still pm you the map sometime Hiemdal, so you might be able to make some sense of the situation.
I guess ill download xtra then... *grumbles*
sometimes i use starforge for the terrains n then use scxe for triggers then go back 2 starforge n stack/sprites..etc. Then i just use starforge trggers since i dont want those stacks/sprites to b removed....n it worked fine

Hmmm.... that's weird Vic. I wonder why it didn't mess up for you but it did for me and Rantent? Well I have got to start learing out on how to use StarForge triggers. lol So I could just stay in one editor.
If you could PM me the map that you got from your partner, that would be great. You guys may have discovered a new unit property flag...
I can tell you the error you got was the sound. Whenever i open a map from x-tra to SF it gives that crazy error, then i lose all sounds. but not the strings ;\
Glad that you got to figure it out Rantent. lol

But I still have that error for mine and my friends map.

Just like you said Trigga, it does also delete all of my music/sound.

I suppose you should fix the sound problem Heimdal. (GL with that) And another weird thing about this two units, one string problem, is that I'm noticing the triggers divided up which unit was used in the trigger at seemingly random. It's kind of annoying. Oh well, you might be able to do something on it in the future. Thanks for helping me analyze what happened.
\\\Topic Closed
(I always wanted to say that

)