Extension: Height label

[bmos]

This version is tentatively compatible. I have not tested it as thoroughly as Kelrugem usually does as I don't know this code as well.
There were certain functions in the code that were referenced and no longer exist. I have updated that code to reference the newer functions and made small changes necessary to support this.

EDIT: reuploaded to simplify the 'on load announcement' approach (which saves .7KB! -- almost 2% of the filesize!)

EDIT2: reuploaded because I had made a mistake

EDIT3: updated to be medium instead of large (but made it 26pt rather than 24).

[Kelrugem]

This version is tentatively compatible. I have not tested it as thoroughly as Kelrugem usually does as I don't know this code as well.
There were certain functions in the code that were referenced and no longer exist. I have updated that code to reference the newer functions and made small changes necessary to support this.

EDIT: reuploaded to simplify the 'on load announcement' approach (which saves .7KB! -- almost 2% of the filesize!)

Thank you for your work

Yeah, the height extension is probably one of my first extensions I update again, once I have time for it That is gladly easier to maintain than other extensions, but still so much to do right now for me aside the extensions (and with your version I basically do not need to update anything anymore related to the last patch, hehe )

[bmos]

Thank you for your work

Yeah, the height extension is probably one of my first extensions I update again, once I have time for it That is gladly easier to maintain than other extensions, but still so much to do right now for me aside the extensions (and with your version I basically do not need to update anything anymore related to the last patch, hehe )

And with these new functions, it should be pretty easy to handle getting a ruleset-independent correct range indication including height!
Although, a 5E check should be included since 5E is non-euclidean (you just use the longest leg). Hopefully, since I did the compatibility fixes, you can focus on the fun stuff

[Kelrugem]

And with these new functions, it should be pretty easy to handle getting a ruleset-independent correct range indication including height!
Although, a 5E check should be included since 5E is non-euclidean (you just use the longest leg). Hopefully, since I did the compatibility fixes, you can focus on the fun stuff

Yup, I was also already thinking about including those new functions

yeah, I want to combine the height measure in the distance measure similar to the x-y-plane Basically using the same diagonal multiplier as in the plane, then it should automatically cater settings of rulesets, like the uniform norm of the standard 5e setting

(Like Moon Wizard wrote here too https://www.fantasygrounds.com/forum...l=1#post566763 )

EDIT: I've linked your version at the beginning in the first post

[bmos]

Yup, I was also already thinking about including those new functions

yeah, I want to combine the height measure in the distance measure similar to the x-y-plane Basically using the same diagonal multiplier as in the plane, then it should automatically cater settings of rulesets, like the uniform norm of the standard 5e setting

(Like Moon Wizard wrote here too https://www.fantasygrounds.com/forum...l=1#post566763 )

EDIT: I've linked your version at the beginning in the first post

Oh, if that variable is stored in a consistent place between rulesets that would be very conventient!
Neat, hopefully I did everything right

EDIT: I did not do everything right
But now I think I did! I replaced the attachment on that original post.

[Zygmunt Molotch]

noice!

[bmos]

Yup, I was also already thinking about including those new functions

Did some research into this. Looks like you have also (as I saw some comments of yours).
Seems like the main difficulty will be getting the height value, since only token position data is passed to the function for calculating targeting distance. It will have to search through all the tokens and see which one matches the location. This is somewhat an issue since it will not be able to distinguish between stacked tokens (although this can be avoided by un-snapping the tokens and offsetting them slightly which has the added benefit of making it easier to move and target them).

It's looking like you might not need to do this after all. This has moved up to 6th place on the wishlist!
http://fgapp.idea.informer.com/proj/?ia=135361