| 08-16-2003, 11:33 AM | #1 |
Hi, I did some stuff with triggers which required to register a larger amount (3072) of events in a trigger - unfortunately it never worked how it was supposed to be. I played a bit with some debug effects and came to the conclusion that the register process stopped suddenly. So I tried some other things and found out that there is obviously a maximum duration for a trigger after which it gets terminated - does anyone has an idea how to increase this duration? The only way I can get around this right now is to split the registration into 4 triggers and enqueue them. btw: Is there a maximum number for events that belong a trigger? |
| 10-06-2003, 06:51 PM | #2 |
There's a maximum on almost everything in war3, but I don't know what they are :) |
| 10-06-2003, 07:31 PM | #3 | |
Quote:
Generally you can increase the trigger lifespan when you use common.j functions. If you don't know what I mean, well I don't want to explain it here. Maybe after you posted your trigger. |
| 10-06-2003, 09:51 PM | #4 |
well I solved the problem by splitting the trigger into 4 parts ... each of them is sceduled from the "map init" trigger ... but perhaps one could optimize them a little more by converting them to jass ... |
| 10-07-2003, 08:02 PM | #5 |
That's what I wanted to do. I wanted to help you. So if you convert your trigger (put it into one for that please) to Jass and post it here I can help you. |
