So I have 2 triggers that run periodically throughout the game, working fine for 4 weeks now. Just recently, they trigger error message starting appearing, saying that they're taking too long. Anyone have any ideas what's causing this? Perhaps there's too much triggers and events, causing them to stop executing to free up system resources maybe?
Its gotta be more then 100K, I have a trigger that does at least 150K actions off the top of my head, a for->for looper to compare the height points of each of the map's grid squares can do that on larger maps :P Meanwhile I consistently hit that error if I tried to push about 30K lines to an error log file at once so its probably more tied with an actual time frame then amount of actions. :P
But yes EarendilSphere this is pretty much what's going on: They're doing too much and the game thinks they're a problem because of that. Try breaking up what they do into a few different functions or just make them more stream lined, like I said I had to pretty much purposely break my giant trigger to cause that error, no trigger should hit that if its being done reasonably.
Okay vjeux and BumInTheNig, I got it. Thanks guys.
A question: How do you know all these limitations and the details of them, surely there's some sort of documentation somewhere that touches on them, no?
So I have 2 triggers that run periodically throughout the game, working fine for 4 weeks now. Just recently, they trigger error message starting appearing, saying that they're taking too long. Anyone have any ideas what's causing this? Perhaps there's too much triggers and events, causing them to stop executing to free up system resources maybe?
A single trigger cannot execute more than 100 000 actions or something. Check if one of your trigger is doing a big loop.
Its gotta be more then 100K, I have a trigger that does at least 150K actions off the top of my head, a for->for looper to compare the height points of each of the map's grid squares can do that on larger maps :P Meanwhile I consistently hit that error if I tried to push about 30K lines to an error log file at once so its probably more tied with an actual time frame then amount of actions. :P
But yes EarendilSphere this is pretty much what's going on: They're doing too much and the game thinks they're a problem because of that. Try breaking up what they do into a few different functions or just make them more stream lined, like I said I had to pretty much purposely break my giant trigger to cause that error, no trigger should hit that if its being done reasonably.
Okay vjeux and BumInTheNig, I got it. Thanks guys.
A question: How do you know all these limitations and the details of them, surely there's some sort of documentation somewhere that touches on them, no?
Experimentation, experience and searching these forums. Pretty much the standard methods of gaining any knowledge about the editor. ;)