In my map, I am trying to detect if a bunker needs more units in it. During this process I have discovered the following:

If you use a trigger to detect units in a bunker assuming that location BUNKER is directly over the bunker, if the condition is:
Current Player Brings EXACTLY 1 of Terran Marine To Location BUNKER

This works fine. It only executes when there is exactly 1 unit in the bunker. However if you use this:

Current Player Brings AT MOST 1 of Terran Marine To Location BUNKER
The trigger seems to fire regardless of how many units are in the bunker.

The trigger in my map is something like this:

Conditions:
Current Player Brings AT MOST 3 of Terran Marine To Location BUNKER

Actions:
Order Unit To Move To Location Bunker
Run AI Script "Enter Closest Bunker" at location BUNKER
Preserve Trigger

The problem with this is that even when there are 4 units in the bunker, the trigger still fires and units still try to get into a bunker that is full. I can't have that.

Here is an example map.
If anyone finds a way around this, or finds that I am doing something wrong then please let me know. This isn't a hugely important part to my map but it is kind of a big deal. And I can't do it any other way in my map, I have to be able to detect if the bunker is less than full or it won't work.

Post has been edited 1 time(s), last time on Apr 6 2008, 4:42 am by KilaByte.

You will have to make 4 triggers, 1 for each number of marines inside (0-3).

Lets say my map has over 60 bunkers that would need these 4 triggers.

Thats 240 triggers. I can't do that, and I'm guessing that since it would be 240 triggers all relating to unit movement it would cause a bit of lag.

Any other ideas?

Anyone know why the hell AT MOST doesn't work. Because AT LEAST and EXACTLY work fine.

Because Blizzard has a fun sense of humor.

Have a trigger that loads marines into the bunker for location "Bunker". Recycle this location among the 60 bunkers. One way to do this is have a death count with each value corresponding to a different bunker. In the Load trigger, add one to this death count.

You could also have a "Number" Death Count that cycles between all the copies of the Load trigger -- exactly 0 marines, exactly 1 marine, exactly 2 marines, and exactly 3 marines. Then when it's done, add one to the "Location" death count, which causes the location "Bunker" to switch to the next bunker.

It's called trigger duplicator. A trigger doesn't lag when it doesn't fire. You could probably get away with centering a location and only using 5 triggers.

Welcome to Starcraft mapping.
However, you can optimize what I said by using binaries:
First check for exactly 0 (--> create 4)
Then DON'T make a trigger for exactly 1
Because exactly 2 & 3 will also create 3 marines in total.

If these triggers really fire so often that you experience lag you should not leave out exactly 1 as in 25% of the cases you cut the lag caused by these triggers by half. ==> 1/8 less laggy if not less... O.o

Btw. having a number dc for the copies of the load trigger doesn't help, because you cannot use dc's as arguments in other conditions as "Death".
For the location cycling you should use burrowed lings given from P11 to P12 under the bunkers:
#1
Always
center 'Bunker' on on P11's lings

#2-4
Check for exactly 0,2,3 rines
<load bunker>
give ling at "Bunker" to P12

#5
P11 has at most 0 lings
give all lings of P12 to P11

Here is also no dc needed.

Sorry I was under the impression that having 240 conditions being tested caused more lag (And Map Size) than having say... 60 conditions tested.

My map does not create the units at the bunker. Instead if a bunker needs units in it, Units are sent to that bunker (1-60) from a different location.
Regardless, I have figured it out by giving certain bunkers priority over others and getting units to enter the highest priority bunker first, then the remaining units (I.E. Units not inside that bunker) move to the next bunker in the priority list.

I have manage to do this using 120 Triggers, which is good enough for me.

Thanks anyway.

In this case you can place burrowed hyds at the creation locations as well and cycle them too.
Cycling usually > Trigger duplication

At Most doesn't work because it doesn't detect units in bunkers(don't ask me why).

At Most not detecting units in bunkers is a nice feature more often than it is a downside, which is probably why blizzard changed the requirements for it sometime during their own scenario development. It's especially with disabled bunkers where you can't remove the men inside anyways.

http://www.staredit.net/?file=191

Here you go. This shows how to use a small location ( 1 pixel ) to detect when, in this case 1, a unit enters a bunker. This could be done with 1-4 units.

Is there a way to change the amount of units that are able to enter a bunker via EUD triggers?

You should've just had burrowed units under the bunkers and cycled through them.