Does anyone know if units that are 'dead', ie those that have just died and have 0 HP, but haven't yet been removed from the game (they linger for 1 frame) are counted against map max?

Specifically I have a trigger that creates large numbers of temporary units, and then uses Kill on them, before creating just a few units that are supposed to be permanent, however sometimes the units don't get created due to map max. I'm wondering if the units that are in the process of dying are counted against map max (there are also hundreds of other units active on the map at the same time), or if using Remove Unit instead of Kill Unit would avoid this issue? If Remove Unit, within the same trigger, doesn't have this issue, I'll go with that, otherwise I guess I'll have to rig a system where I remove the temporary units in one trigger, and add the permanent ones in the following trigger.

Removed units vanish instantly, so np there.
Killed units is easy to make a testmap for. My guess is yes, because the unit is still visible.

Yes Lanth, I believe they do. A unit in its last frame before death has all the properties of a living unit.

They can be detected, yes. But they can't be moved afaIk. I think that was what was used to identify the position of some dieing units.

units exist until their death animation disappears. Which is an awfully long time for buildings, zerg ground, terran infantry, and dragoons. They can still be detected as units on the frame they die, but not the frame after.

Ah hah, very useful.

When you say death animation, do you specifically mean the animated part? Once there's just a corpse/blood stain on the ground that is not moving, the corpse/blood stain is no longer taking up unit space?

The sprite is an animation which eventually fades into nothingness. As long as there is a bloodstain (and perhaps a little longer) the unit takes up space.

@Lanthanide

1) If you're gonna use so many units as death animation.. enough to cross the map max.. you're using too many

2) I found this useful for creating a unit @ the place where a previous unit has died so that the new unit does not get displaced by the previous one.
- Instead of creating the unit @ location of dying unit, create it elsewhere, and move it to the location of the dying unit.

Also, it's good form to set a switch (DC) and have it run a trigger which moves the unit to the proper location. Then, clear the switch once the unit is moved. This way, nothing can possibly go wrong, except if you use the switch for something else.

UU - this is DS Night, so there could already be 1600 units on the field, so it doesn't take many to go over map max.

I'm already using a system where units are created off the field and then moved into their final position before they're used for any purposes. That's actually the entire point of this particular trigger - it's used for nuke, to arrange the spider mines that eventually get placed on the field in a spread out pattern, instead of just a big clump of mines that blow each other up and get in the way of each other. It creates 28 mines, then moves 21 of them to the field, followed by 1 that belongs to a different player, then moves the remaining 7 and another 1 of the other player. Then it kills the 28 'filler' ones. Then it does this whole thing a total of 19 times, creating 532 'filler' mines in the process. I'll just set them to be removed, instead of killed.

I'll make a pass over all the other triggers I have that create units, and try and make sure that it does some 'remove' units in addition to 'kill' sufficient to cover for any new units being created within the same trigger.

Post has been edited 2 time(s), last time on Apr 18 2011, 5:52 am by Lanthanide.