Annoying Trigger Issue

[Cr34p]

Maybe some of you remember the location of an unit in warcraft3 was the same after they died, since the decayed.

In SC2 the unit position gets X:0 Y:0 if the unit dies.
My question now: Is there a solution for this?

 

[Khlox]

I don't really seem to have this problem... This is the trigger that I used:

• HE DIED
  • Events
    • Unit - Any Unit dies
  • Local Variables
    • Point = (Position of (Triggering unit)) <Point>
    • PointValues = (X of Point) <Real[2][2]>
  • Conditions
  • Actions
    • Variable - Set PointValues[2][1] = (Y of Point)
    • UI - Display (((Text(PointValues[1][1]) with Any Precision decimal places) + " X / Y ") + (Text(PointValues[2][1]) with Any Precision decimal places)) for (All players) to Subtitle area
    • Variable - Set PointValues[1][2] = (X of (Position of (Triggering unit)))
    • Variable - Set PointValues[2][2] = (Y of (Position of (Triggering unit)))
    • UI - Display (((Text(PointValues[1][2]) with Any Precision decimal places) + " X / Y ") + (Text(PointValues[2][2]) with Any Precision decimal places)) for (All players) to Subtitle area

(Yeah, I know, I used once with the Point variable and once without, just checking. )
Anyway, both gave me X and Y coordinates which weren't 0, so. :x

 

[Cr34p]

mine is another context, since I'm not using the triggering unit , I'm using unit takes damage and then do some stuff to check if the unit is dead (in a loop, since this is needed), but in the moment the unit dies the position turns to 0,0 that sucks

 

[JakeCake]

create a local variable called "DyingUnit" and set it's intial value to Triggering Unit

Now it's remembered in the memory, a unit is removed from memory when it dies if no variables are assigned to it. You can now reffer to it as "DyingUnit". This is done to remove any memory-leaks (yes, there are down-sides with the new memory cleaner)'

btw. You have used a wait command before referring to the unit

 

[Cr34p]

...you don't get me I think, 1. also if storing it in a variable the point gets 0,0 since the unit position is moved to this point if the unit dies.

This happens since I don't use TriggeringUnit(), seems more like a general problem with the garbage colector, since it should clean the memory of a variable if the variable isn't used anymore, but somehow my loop I use seems to crash this