Okay, so I'm working on a map, believe it or not. It has 1683 triggers right now. As I was continuing to make triggers and testing, however, the triggers began to stop working.

Basically, the trigger that's failing is a basic spawn trigger. I have triggers for force 1 with dialogue, and to sync the spawn timing with the text, I use a death count for a spawn condition of another trigger. Pretty basic. I already had 5 before this one that doesn't seem to work. Naturally, I thought I messed up the trigger, and reread it and verified that everything was right. But still it didn't work. So then I made extra triggers to display a message if the death counter condition was being met. It was. So there was no reason for the trigger to not work.

Finally, I began to move the trigger around, giving it to other players. I gave it to force 1, and suddenly, it worked! I felt relieved and confused, but continued the map. After making maybe 40 more triggers I tested again, and the spawn failed...

Upon retesting various times, I noticed that there's a 20% chance (or so) of the spawn trigger to work. With multiple people in the map, I haven't seen or heard of it working at all.

And here is my official surrender. I need help. I figure I must be hitting some sort of map limit. I still haven't tried things like duplicating the trigger... That might work... But that would just be a quick-fix. I want to know what the problem is.

Post has been edited 2 time(s), last time on Aug 23 2008, 5:00 am by Roy.

There's no such limit when it comes to map triggers. I am working on a map that has over 4k handmade triggers and counting.

Can you give us the map? That way we can see what the problem really is and know in detail your triggers.

I figured you'd say that...

Trigger in question is "Spawn 6" under p7. The condition is met with a trigger in Scene2 (sorry for the same comments, I'm trying to save strings ) It's 5th or 6th from the bottom in Force 1.

[Removed Attachment]

Post has been edited 1 time(s), last time on Aug 23 2008, 4:59 am by Roy.

The problem won't be the triggers. My map runs at least 15000 triggers per second to calculate values and the like, and it's fine because 99.9% of them only affect death counters. (like taking your strength and weapon and other stuff values and adding them to get your total damage and stuff, with randomization, done 12 times a second)

The problems start when you have masses of triggers that are either unorganized or unsystem-ized so that they run in to overlap problems or wait blocks. There also might be a buffer that stops it from creating units or performing specific actions within itself. To test it, try adding a display text within the trigger, and see whether or not it's firing at all. In any case, if problems persist, you might want to remake your map with more precise trigger handling.

Eh, I was watching for wait blocks throughout the whole thing. The scene2 trigger already has a display text in it. And, of course, like I said, I've added a trigger with the same conditions as the spawn, except made for player 1, with a display text trigger, which worked, whether the spawn did or not. Which would imply that the trigger would work under player 1 and not under player 7...

Heheheh, if I have to remake my map, I won't. 3-digit trigger counts are high enough for me.

Oh right, I also copied/pasted the texted triggering into wordpad and used "find" to look for anything that might interfere with these triggers. I found nothing.

And if this is unheard of and you can't figure out what's wrong with it, I'm guessing my map got corrupted. It crashed on me when I was working on it a while ago, and I had to redo Scene2. I don't know whether of not the triggers were working before the crash; I hadn't tested.

Post has been edited 2 time(s), last time on Aug 22 2008, 11:06 pm by Roy.

I saw the triggers. There are so many waits it's ridiculous. I'm not 100% sure whether you're getting wait blocks or not, but from the looks of it, you are. Having that many waits with multiple players you're bound to run into problems (again, I'm not completely sure if this is the problem). If it is, however, you can and should use death counts for your timing. With death counts, you will hardly ever run into problems.

Right, well, ignoring the fact that I've been watching for wait blocks, and how everything worked fine up to this point, AND how the trigger/condition in question doesn't have a wait before it, you're right. I'll have to switch from waits to death counts for a few things (I'm currently not comfortable with death count timings, although my last bound used only dcs). As of right now, I don't believe I'm getting wait blocks, and even if I am, that's not related to the question I have...

Sorry if I sounded a bit rude right there This map's been pretty aggravating.

I just checked it out too, and there are so many waits, I'm almost certain that's the source of the problem, I can see how you're trying to only have one at a time, but death counts are always the best solution. The main reason why I believe it is waits, is because there's no other explanation that would allow you to still run your map.

Eh, I never heard of waits blocking other triggers that don't have waits... Oh well... I'll swap out some waits, and see if that works... Eventually. At least I won my bet that you guys would say it was wait blocks.

Yeah, but the conditions of other triggers without the waits may ride on whether or not a trigger with a wait runs.

Eh, I don't think it is for that particular trigger; I'd be able to see the spawn on the minimap; but I had a feeling that waits would become problematic. I wasn't planning on this map being so big. Looks like I'll have to convert it a bit.

Solved? Was it wait blocks then?

not that this helps, but i had that same problem a very long time ago, and i didnt even have that many triggers, not even 100 when it happened to me. all my triggers worked just fine then i noticed that 1 just didnt work for some reason, to make sure i found out that ANY new trigger i made, not mattering on what, wouldnt work. so i came to the conclusion that no new triggers would work and quit that map.

Well you obviously did something wrong, because that doesn't just happen.

Eh, sorry for the misleading title, I'm just giving up.

It's not wait blocks.