PDA

View Full Version : BUG - height calculation on maps not correct



Lo Zeno
July 4th, 2023, 11:31
I've managed to replicate this in a 5E game and a Cyberpunk RED game:

When adjusting the height of a token (with alt+scroll wheel), the distance from the token to its target is calculated as the MAX between the height and the horizontal distance.

For example, a character is on elevated ground (20 feet up) targeting an enemy 6 squares away on the map (at 5 feet per square means 30 feet) has the distance calculated as 30 feet. If the elevation is 40 feet, but the distance on the grid is still 6 squares, the distance is calculated as 40 feet.

Moon Wizard
July 4th, 2023, 17:14
That's correct; it's using the adjacent cube measure of distance by default (i.e. D&D 5E method). (i.e. any cube that shares a corner with another cube has a distance of 1 grid unit)

There is no way to specify alternate calculation for diagonal cubes vs. squares; they should use the same logic based on image settings and campaign options.

Regards,
JPG

Lo Zeno
July 4th, 2023, 17:24
That's correct; it's using the adjacent cube measure of distance by default (i.e. D&D 5E method). (i.e. any cube that shares a corner with another cube has a distance of 1 grid unit)

There is no way to specify alternate calculation for diagonal cubes vs. squares; they should use the same logic based on image settings and campaign options.

Regards,
JPG

I checked my campaign setting, because I was sure I was using the 1.5x rule for diagonal calculations in the 5E ruleset, and the Raw rule for Cyberpunk, and sure enough they were both set to 1x instead - so that would explain why now I see different results than before. But I'm 100% sure the settings were different until at least 2 weeks ago: I had session zero's with both groups months ago to decide things like these together, and notes from several old fights confirm that the distances were calculated with different systems. Is it possible a recent update to the rulesets might have reset the options? Otherwise the only explanation I could think of is that an extension might have changed that setting, but I don't use extensions that affect distance/height etc.

Moon Wizard
July 4th, 2023, 17:31
There's nothing specific changed that I'm aware of; but always lots of moving parts. If you see the issue and can recreate, I'll get it fixed. I haven't seen it here.

Regards,
JPG