Detecting if a unit is dead

[AoW_Hun7312]

What's the best method to detect if a unit is dead or not?

GetUnitState(GetTriggerUnit(), UNIT_STATE_LIFE) > 0

GetWidgetLife(GetTriggerUnit()) > 0

IsUnitType(GetTriggerUnit(), UNIT_TYPE_DEAD)

I've also heard that 0.405 is better than 0, is this true?

 

[Laiev]

>> I've also heard that 0.405 is better than 0, is this true?

The reason is because an unit die when life become 0.405 and not 0

[ljass]GetUnitState(GetTriggerUnit(), UNIT_STATE_LIFE) > 0.405 //never use it lol[/ljass]
[ljass]GetWidgetLife(GetTriggerUnit()) > 0.405 //good and fast but can bug if you increase the life of unit when he's death[/ljass]
[ljass]IsUnitType(GetTriggerUnit(), UNIT_TYPE_DEAD) //idk... not too bad and not too good[/ljass]
[ljass]UnitAlive(GetTriggerUnit()) //better in my opnion[/ljass]

 

[Tamisrah]

So GetWidgetLife is faster than GetUnitState or is it just fast on it own?
Most of the time I do use "GetUnitState(GetTriggerUnit(), UNIT_STATE_LIFE) > 0.405".

 

[Komaqtion]

Yupp, quite a lot faster, and easier to use too

Though the AI native [ljass]UnitAlive(whichUnit)[/ljass] is even better

 

[Laiev]

i'm with komaqtion but remember, you need to declare it in your code

[ljass]native UnitAlive takes unit id returns boolean[/ljass]

 

[Bribe]

There is a problem with using UnitAlive with Vexorian's map optimizer.

If you have the option "shorten function names" enabled, the stupid optimizer shortens the name of the native, as well, which makes it unable to function when you try to play the map later. Lame.