A question about GetLocationZ

[Tal'Rarity]

So its pretty much only a graphical function right? Like let's say I want to make a full house intense type of map that uses a lot of projectiles which has to collide with other units in the air as well as terrain/mountains however what if I want them to take terrain level into account so it doesn't look lame sliding?

Also technically since flying height doesn't desync by itself, you should be able to locally set it for pretty cool effects in a multi player game.

 

[WaterKnight]

Clarify the question. GetLocationZ returns the terrain height of a spot, according to the local player's information of that spot, which may be async if for example there is a deformation but the player does not see it due to fog of war. Terrain height is also affected by walkable destructables like bridges. In case such destructable is animated, the terrain height is too. Flying height is only for graphical purposes in standard wc3, it does not alter the gameplay.

 

[Tal'Rarity]

What if you want to detect collisions in the air, that's the main question.

 

[Wietlol]

I have air-collision in my Missile System.
I pick units that collide on the X + Y axis and check if the flying height of the missile is not larger or smaller than the flying height of the unit with (Height) as maximum difference.
In that case you do not require GetLocationZ(). I do use it to calculate the route of the missile though.

 

[Tal'Rarity]

As long as your using flat terrain then yeah that works.

 

[Wietlol]

Well you can indeed increase precision by also adding the difference (in same order) between the GetLocationZ() of missile and unit.
But as they are basically at the same spot. The GetLocationZ() would be almost the same.
So you basically add/remove 0-10 to the difference. You tell me if you think it is worth it or not...
I can see that some people wouldn't care.

 

[rulerofiron99]

You'd need the LocationZ if the two units are colliding near a very steep cliff. They could be colliding across a distance of up to 100, and depending on your terrain that could mean a z-difference of up to 300.

 

[WaterKnight]

Even if you are not adding the terrain height in your collision check, basing it on flying height puts it in a sync context. And you most-likely set the flying height depending on terrain height anyway. You would normally save the current z of the missile in a variable and operate on that.