Yea it's better.

 

 

Edit:

.120-.121:

Apparently that's not good enough for a release thread, so I'll include some info:

EntityAPI.closest uses real distance instead of pythagorean. Real distance cannot be calculated if an object is not reachable. If you need to restore original behavior, use closest(false, ...)

Mouse event changes to be more accurate.

Couple internal changes, including some to reduce CPU usage.

 

.122:

Reverses the EntityAPI.closest() changes. Now closest(...) has the same behavior as closest(false, ...)

woo i just like it's better.

Nice release

very nice

 

now for the ww 

Noice!

Nice, really like these updates!

These are good changes. Thanks.

Thanks

Thankyou:)

.121 patches AutoLogin handler.

What happens if the closest method isnt reachable? (RIP)

What happens if the closest method isnt reachable? (RIP)

 

Call closest(false, ...)

 

Edit:

For anyone else that's wondering, closest(false, ...) is the original behavior for closest(...). In this update, closest(...) was changed to closest(true, ...).

Call closest(false, ...)

Edit:

For anyone else that's wondering, closest(false, ...) is the original behavior for closest(...). In this update, closest(...) was changed to closest(true, ...).

So using real distance, does noot include can reach method? I don't get it.

Edited October 9, 201510 yr by Joseph

So using real distance, does noot include can reach method? I don't get it.

 

Real distance cannot be calculated if the object is unreachable. So, the object must be reachable.