- 10,739
- 12,079
Since it came up recently it's probably worth discussing and adding, sooo...
On our reactions page we have the perception time (i.e. reaction time) table.
We have the following reminder listed on that page
So illegitimate way of perception quantification would be: "Character is 100m/s fast, so I assume they can react in 1m/(100 m/s) = 0.01s."
Legitimate would be something like: "A 100 m/s attack was fired at the character from 2 meters away and they managed to create a forcefield in time. 2m/(100 m/s) = 0.02s perception time."
or "Character was stated to move at 100 m/s at that moment and turned a corner into a 1m wide corridor without crashing into the wall. To coordinate that they must have the reactions to turn in the timeframe in which they pass by the corridor, so 1m/(100 m/s) = 0.01s reactions."
Things like that.
So my proposal is to expand the upper note to
On our reactions page we have the perception time (i.e. reaction time) table.
We have the following reminder listed on that page
That reminder should be extended to also include the reverse. I.e. if you have travel, combat or reaction speed in a m/s format, you can't just calculate a perception timeframe to it by assuming the character can react in the timeframe necessary for something with that speed to cover 1 meter. That was basically already the issue in the space travel case, so noting it is worth it.Reaction speed has both a distance and a timeframe component, so all calculations that are completed for reaction speed cannot simply be a timeframe by itself. Do not randomly assume a 1 meter distance for each timeframe and use that speed for the reaction speed.
So illegitimate way of perception quantification would be: "Character is 100m/s fast, so I assume they can react in 1m/(100 m/s) = 0.01s."
Legitimate would be something like: "A 100 m/s attack was fired at the character from 2 meters away and they managed to create a forcefield in time. 2m/(100 m/s) = 0.02s perception time."
or "Character was stated to move at 100 m/s at that moment and turned a corner into a 1m wide corridor without crashing into the wall. To coordinate that they must have the reactions to turn in the timeframe in which they pass by the corridor, so 1m/(100 m/s) = 0.01s reactions."
Things like that.
So my proposal is to expand the upper note to
Reaction speed has both a distance and a timeframe component, so all calculations that are completed for reaction speed cannot simply be a timeframe by itself. Do not randomly assume a 1 meter distance for each timeframe and use that speed for the reaction speed. Other way around, perception time is just a timeframe and by that not proportional to a speed value alone. Do not assume that a character with a certain speed will have a perception time of 1 meter divided by that speed. Such calculations need a feat that demonstrates perception time and a suitable distance determined from that feat.