Hasn't this been submitted before? Anyway, it is a useful snippet. However, no one ever ends up using these kinds of small library requirements because it makes the systems much more annoying to implement. IMO, just inline it unless you are coding a map yourself.
Well i find that most of the projectile systems or any kind of system that intends to move units accordingly to the ground's height use a private global location. This is just to generalize that and has a intuitive API, i was thinking of adding GetUnitZ but then i realized that most of the times you already know the unit's flying height and it would end up reading it twice from the native, people should do the math themselves
FullOfUltimateTruthsAndEt ernalPrinciples, i.e shi
Why do you think projectile libraries inline the MoveLocation(g_loc, x, y), instead of using a wrapper like this? Because a function call turns out very expensive for efficiently moving hundreds of projectiles ~32+ times per second.