Is unit dead?

[dudeim]

Hey,

got a little question there are a few ways to check if a unit is dead, but all have their disadvantages.
So the question is if the "A Unit Dies" event triggers is the unit really considered dead so can't there be any way to revive him by setting his hp higher? (I'm not talking about the hero revive action thingy)
So will the "Unit dies" event not fail or does it fail?

Thanks (hope you get what I mean)

 

[Azlier]

I'm not sure I understand. If a unit dies by taking damage or through KillUnit or possibly other means, the unit dies event will always fire. If the unit is removed via RemoveUnit, it does not fire.

If you wish to know if a unit you currently have a reference to is dead, you can use this native, once you paste it into your map. Make sure you're using a recent Jasshelper version, though.

native UnitAlive            takes unit id                               returns boolean

 

[dudeim]

But doesn't this native bugs when you compress a map using an optimizer? That's what I heard atleast (or something along that way)

 

[Sevion]

Use [ljass]IsUnitType(whichUnit, UNIT_TYPE_DEAD) or GetUnitTypeId(whichUnit) == 0[/ljass]. That will return true for dead and/or removed units.

 

[Jedi]

I really want to puke everywhere because of this retarded IsUnitDead-Alive discussion.

 

[dudeim]

I really want to puke everywhere because of this retarded IsUnitDead-Alive discussion.

As long as it's not near me go ahead

 

[Frozenhelfir]

I just use GetWidgetLife(unit) > .405 for alive, less than for dead.

 

[Sevion]

I really want to puke everywhere because of this retarded IsUnitDead-Alive discussion.

It's not retarded. Many methods have different pros and cons.

You should research before you make such comments.

 

[Jedi]

If you dont increase a dead unit's life, I see nothing wrong with GetWidgetLife.

 

[Azlier]

First, UnitAlive has no known cons whatsoever.

Second, GetWidgetLife isn't magically safe even if you're careful to check before modifying life. Some abilities have been reported to increase life after death, such as Stone Form. Best to avoid dodgy methods when there are better ones available.

 

[kingkingyyk3]

First, UnitAlive has no known cons whatsoever.

Hmm, Vex's map optimizer got problem with it. Sadly.

 

[Laiev]

Its not a problem with the native, is problem with Vex's optimizer.

 

[kingkingyyk3]

Yes, I know.

 

[Nestharus]

First, UnitAlive has no known cons whatsoever.

Second, GetWidgetLife isn't magically safe even if you're careful to check before modifying life. Some abilities have been reported to increase life after death, such as Stone Form. Best to avoid dodgy methods when there are better ones available.

I heard UnitAlive returns true the instant a unit is removed (same with IsUnitType((u, UNIT_TYPE_DEAD), hence the GetUnitTypeId != 0 check. I guess you could actually use not (UnitAlive(u) and GetUnitTypeId(u) == 0) to see if a unit was currently dead and (UnitAlive(u) and GetUnitTypeId(u) != 0) to see if a unit is alive..

 

[emjlr3]

that is a very rare occurrence when you will be checking whether a unit is alive at the same moment it is removed - if that is the only time it doesn't function properly, I say its pretty reliable

 

[Azlier]

GetUnitTypeId(u) == 0)

I seriously doubt GetUnitTypeId will return 0 the instant a unit is removed, as the unit isn't truly removed right then and there. The moment GetUnitTypeId returns 0 is the same moment that UnitAlive works.