Triggering Glitch

[DoomCarrot]

While working on the next map of my campaign, I encountered a problem.

I added two triggers (12 and 13), and quit to test the map. However, when I try to activate the map as "own," I get an error message saying that for some reason, trigger(2) is broken or something. Which is weird, because I mever touched that trigger, and everything was working fine earlier.

Does anyone know what could cause a trigger error?

[Constantin]

Maybe you send a screenshot of the second trigger?

[Hardeep]

Lolololol
Happens to me all the time!
Solution: Delete everything in the trigger and remake it.
Works 100% of the time

[DoomCarrot]

grrrrrr.... fine.

I'll remake the trigger, and report any success, as well as a screenshot if it is still broken.

[DoomCarrot]

Hardeep was right.

I believe I may have pinpointed the issue as well.

One of the trigger effects was to change all forest sentries to another team in a certain area. However, I had deleted one of the forest sentries on my last edit, which although that SHOULDN'T have messed anything up, apparently it did.

[Alpha]

Lol. Hardeep bested DoomCarrot.