A very magical dragon! (targeting distance errors in raw FGU)

[SilentRuin]

[TESTED IN 5E RULESET] Ok I have this huge token - a dragon - that my normal medium token - a PC - is moving up towards. Here is me 15ft away moving toward the arrow shown...

MagicalDragon15.jpg

Then I move a little closer to 10ft away...

MagicalDragon10.jpg

Then a little closer to 5ft away...

MagicalDragon5.jpg

Then one more move just to crawl up onto this beastie - which technically in game targeting would still be 5ft away...

MagicalDragonMagic.jpg

10 ft away? Now maybe the NPC dragon has some strange phase shift ability I'm unaware of - but I'm skeptical on that. If I move further it goes back to 5ft.

A truly magical dragon!

But in reality probably FGU distance targeting display error.

[SilentRuin]

FYI this "hiccup" of distance change can reek havoc with extensions like Aura Effects where the effect can switch off and on several times (triggering in some cases) just by passing by/through edge of larger than 1 grid unit tokens when the aura is 5ft (1 grid unit)

[SilentRuin]

Another bug is that Token.getDistanceBetween is returning #0 when one of the tokens is not visible. Why would this ever matter when trying to find distance between things? I think this is also a bug.

[Ulric]

[TESTED IN 5E RULESET] Ok I have this huge token - a dragon - that my normal medium token - a PC - is moving up towards. Here is me 15ft away moving toward the arrow shown...

MagicalDragon15.jpg

Then I move a little closer to 10ft away...

MagicalDragon10.jpg

Then a little closer to 5ft away...

MagicalDragon5.jpg

Then one more move just to crawl up onto this beastie - which technically in game targeting would still be 5ft away...

MagicalDragonMagic.jpg

10 ft away? Now maybe the NPC dragon has some strange phase shift ability I'm unaware of - but I'm skeptical on that. If I move further it goes back to 5ft.

A truly magical dragon!

But in reality probably FGU distance targeting display error.

I can reproduce this in a clean test campaign. That is an odd bug to me.

[SilentRuin]

I can reproduce this in a clean test campaign. That is an odd bug to me.

Painful if you use extensions like Aura Effect... I'm having to set all my minimum aura distances on my huge+ sized npcs to 10ft so it does not go nuts on this bug (flipping in range and out of range does bad things). Also having it ignore auras when and effect changes on something invisible is something I now have to manually manage.

Hopefully both issues get resolved soon (aslo waiting on some onMove duplication that was supposed to be fixed in next release).

[GKEnialb]

It looks like if the center of a token is on the closest square of the other token, that other token uses the center of the token as the coordinates instead of the the center of the closest square (2.5' away). Whether that 2.5' would go to 0' or 5' as SilentRuin suggests, I'm not sure, though. Here are a scattering of images from different sized tokens.

Medium - Large.png
Medium - Huge.png
Medium - Gargantuan.png
Large - Huge.png
Large - Gargantuan.png

[GKEnialb]

And one more for completeness

Huge - Gargantuan.png

[SilentRuin]

It looks like if the center of a token is on the closest square of the other token, that other token uses the center of the token as the coordinates instead of the the center of the closest square (2.5' away). Whether that 2.5' would go to 0' or 5' as SilentRuin suggests, I'm not sure, though. Here are a scattering of images from different sized tokens.

Medium - Large.png
Medium - Huge.png
Medium - Gargantuan.png
Large - Huge.png
Large - Gargantuan.png

I've only seen what your looking at as going 5-10-5 never 0. The invisibility thing is a separate thing purely with Token.getDistanceBetween always returning #0 when one of the comparisons is invisible.

[GKEnialb]

Yep, I was just saying that if tokens overlap, I'm not sure if the distance should be 5' (like you suggested with "which technically in game targeting would still be 5ft away" in your first post) or 0' since they're on top of each other. Maybe it should be 5', maybe it should be 0', but definitely shouldn't be 10'.