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
Ultimately this is an issue with the way the PF2e core system handles speeds. Presently when speeds are converted from a string to value for the speed.total they are converted integers and then any math regarding armour or other effects that reduce speed are applied. This is the underlying issue cause the problem reported in manuelVo/foundryvtt-drag-ruler#27
While it is possible to build a work around using the original speed.value and apply any speed penalties or boosts as part of the ruler. Speeds are being overhauled in the next feature release for PF2e. Consequently I'm going to tackle this after PF2e core speed overhaul if it is still an issue at the time.
The text was updated successfully, but these errors were encountered:
velara
changed the title
Support for Fractional Distances (For the 1.5m -> 5ft metric conversion) in non functional
Support for Fractional Distances (For the 1.5m -> 5ft metric conversion) is non functional
Apr 30, 2021
Ultimately this is an issue with the way the PF2e core system handles speeds. Presently when speeds are converted from a string to value for the speed.total they are converted integers and then any math regarding armour or other effects that reduce speed are applied. This is the underlying issue cause the problem reported in manuelVo/foundryvtt-drag-ruler#27
While it is possible to build a work around using the original speed.value and apply any speed penalties or boosts as part of the ruler. Speeds are being overhauled in the next feature release for PF2e. Consequently I'm going to tackle this after PF2e core speed overhaul if it is still an issue at the time.
The text was updated successfully, but these errors were encountered: