[Stable Build] 2.3.120-122

[Zach]

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, ...)

[Gold Scripts]

[Maldesto]

woo i just like it's better.

[TheRealSwaps]

Nice release

[Tom]

very nice

 

now for the ww 

[Khaleesi]

Noice!

[Magyar]

Nice, really like these updates!

[Dark Magician]

These are good changes. Thanks.

[Benny_]

Thanks

[NayBely]

Thankyou:)

[Zach]

.121 patches AutoLogin handler.

[Czar]

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

[Zach]

  On 10/9/2015 at 6:23 PM, Czar said:

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, ...).

[Joseph]

  On 10/9/2015 at 6:24 PM, Zach said:

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, 2015 by Joseph

[Zach]

  On 10/9/2015 at 8:09 PM, Joseph said:

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.