It happens everytime a hero unit dies and I tought I already fixed it... however it seems that the trigger ignores the event (only NON fatal damage) and the condition (unit alive = true).
However the error I get seems caused by the fact that the owner of unit trigger is not able to get the correct owner, probably due to the fact that the unit is dead.
The error is not really problematic but I would like to get rid of it. Any idea?
If it cant get the units owner cause its dead, try giving it a death time - that'll keep the unit in the game a bit longer and probably allow your trigger to check its owner.
The bug seems to occur when a creature receives damage from a missile shot by a unit that just died... so I didn't make the live check on the damaging unit :P
Kinda tricky but the error didn't always show up so I suppose it may be the problem.
Let's see in the next version if it will show up again!
It happens everytime a hero unit dies and I tought I already fixed it... however it seems that the trigger ignores the event (only NON fatal damage) and the condition (unit alive = true).
However the error I get seems caused by the fact that the owner of unit trigger is not able to get the correct owner, probably due to the fact that the unit is dead.
The error is not really problematic but I would like to get rid of it. Any idea?
If it cant get the units owner cause its dead, try giving it a death time - that'll keep the unit in the game a bit longer and probably allow your trigger to check its owner.
@TheAlmaity: Go
Yeah that's a possibility but I would prefer to make the condition "is unit alive" work :|
1) is there an else? put all the conditions into trigger conditions.
2) try saving the owner in an int variable as very first action
3) use triggering player instead of owner of unit (it returns the same)
Oh wait.. maybe I figured it out!!!!
The bug seems to occur when a creature receives damage from a missile shot by a unit that just died... so I didn't make the live check on the damaging unit :P
Kinda tricky but the error didn't always show up so I suppose it may be the problem.
Let's see in the next version if it will show up again!