
Humble Sage |
I'm posting this because I'd appreciate feedback.
The main change is that the roll is made AFTER the unstable action.
Either after the first unstable action taken each turn... which would be a lesser change
Or after the second unstable action take each turn... which I feel would encourage a more unstable play-style.
The second is lowering the flat-check DC.
Currently 17, or 20% chance of success,
Can be 16, or 25% chance of success,
Or as low as 15, or 30% chance of success and a more familiar DC value.
Additionally, Unstable can track for each unstable action separately. This can be with or without any of the changes above.
I'm leaning toward a DC 15 flat check made after the second unstable action, and otherwise leaving it as is, but like I said, I'd appreciate feedback. I and my players are experienced at TTRPG's, including D20 systems like Pathfinder and D&D, but not Pathfinder 2e, so I don't know how balanced this is.

AnimatedPaper |

Mark has said Unstable will look very different in the final version, and that it is not worth playtesting this version.
My suggestion: all unstable actions are non-magical Focus "spells". You get a single focus point at level 1. Unstable redundancies gives you a second point and the ability to regain 2 points when you refocus.

MaxAstro |

Interestingly, the survey contains this wording:
In the playtest, the inventor's unstable abilities allowed you to use them more often than you should in a desperate situation, but after getting the effect a second time, there was a major risk...
Makes me wonder if a wand-style "the effect goes off and THEN the device breaks" thing was actually the intended mechanic.

roquepo |
1 person marked this as a favorite. |

I would like every unstable action to have its own unstable effect.
For example, Explode unstable could deal low fire damage on the first failed check and high fire damage on subsequent fails. Kickback strike could make you flat footed on the first and knock you prone on the second.
What I like is failure chance to be unified. Some people suggested that each unstable action should have its own traking of usages. That would be too complicated. I also like all unstable actions having the same "failure chance".