You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Range penalty on ranged weapons seems to always use the 1/2/1 counting method for diagonals, even when foundry is configured to use alternate counting. For example, here is an air repeater (range 30ft) suffering from a -2 range penalty when the targeted token is within 25ft, using equidistant diagonals:
I also can't find any way to disable the range penalty automation, so you have to manually disable it in the roll settings each time. A toggle in the automation settings to disable it (like flanking has) would be nice, especially if fixing the measuring issue isn't feasible. Thanks!
The text was updated successfully, but these errors were encountered:
Plus, a (potentially wrong) pointer: seems like this function for measuring distance switches from the system-provided, rule-accurate measuring to foundry's built-in measuring if you aren't using a square grid. Perhaps it should also fall back on foundry's own measuring when the square grid diagonal setting has been changed? For example:
Edit: Ignore that, that code is irrelevant. However, making the same modification in this code seems to work (tested it with a quick and dirty modification of the js).
Range penalty on ranged weapons seems to always use the 1/2/1 counting method for diagonals, even when foundry is configured to use alternate counting. For example, here is an air repeater (range 30ft) suffering from a -2 range penalty when the targeted token is within 25ft, using equidistant diagonals:
I also can't find any way to disable the range penalty automation, so you have to manually disable it in the roll settings each time. A toggle in the automation settings to disable it (like flanking has) would be nice, especially if fixing the measuring issue isn't feasible. Thanks!
The text was updated successfully, but these errors were encountered: