GetClosestUnit(s)

sorry for digging this out but i would like to know if i can use this as a very frequent event lets say like every second
how much would that influence the overall performance ? may it cause lagg along with other functions ?
I dont know much about jass so i cant really guess it myself

Only once per second shouldn't be a problem at all, unless you have several hundreds of units that need to be searched through to find the closest one. Generally it is best to use the function that goes through the least amount of units possible, for example GetClosestUnitInRange instead of GetClosestUnit whenever the range limit doesn't bother you.

EDIT:
New version 1.3 is now up. Its GetClosestUnit most often avoids going through all units on the map unlike the old one, thus the new one should be a lot faster on maps with a lot of units in it.

Originally Posted by JoHnyW

sorry for such stupid question delete this post if i shouldn ask but i want to know what are closest units ?

ROTFLOL

closest unit=the closest unit to the point
close=near
unit=soldier/building/creep/worker/...

this may be a dumb question but, what's the difference between vJassless and the normal one?

The normal version requires you to have jasshelper whereas the vJassless doesn't, but on the other hand when importing the vJassless version you have to create a few global variables with the Trigger Editor's variable editor.

The current versions of both of the systems (1.3.1) are identical when it comes to performance and functionality, except that the normal version is in a library called GCU and thus can be required by other libraries.

Damn, I made my own version of this using 3D, and just getclosestofgroup, as it seemed to be the most generic + efficient way to use the function for each situation

I didn't even think about using ForGroup()

I think you might want to add in a 3D version too, just incase your working with projectiles and the such

I think you might want to add in a 3D version too, just incase your working with projectiles and the such

Nobody cares for the third dimension in wc3 because there are many algorithms and calculations when working in 3D plus it's very possible that you'll never get it right...... it's just not worth it and it doesn't make much difference.

But you can post your 3D version if you know how to make it :)

For a 3-D GetClosestUnit, all you need to do is add another real parameter for the Z, and incorporate the Z calculations for the pythagorean theroem, instead of x*x + y*y = d*d, it becomes x*x + y*y + z*z = d*d

Ok, I will post a 3D version, for this specific case, it is much more simple than using any crazy algorithms