Open zkat opened 4 days ago
Here's an idea: Allow "insert this move block" and "roll this move" to be separate actions, if desired.
So, the flow for Suffer would go something like this:
So, changes that would be needed:
@cwegrzyn popping this over to you. From our Discord convo:
We're just gonna add a "skip roll" entry into the stat prompt for the Make a move
command. That should take care of the Suffer issue just fine.
We still need to add a "Roll move oracle" button for all moves with tables, but I'll make a separate issue for that.
There's also #326 which will help with that optional roll.
Some moves have more complex workflows than "make the move" or "do an action roll"--some of them involve a multi-step process with optional steps and even oracle rolls.
This data is completely missing from datasworn, aside from the raw move text, but it can make it super annoying to use certain moves and still get the move blocks you want.
For example, the flow for most Suffer moves in Starforged is:
I think in order to support this, we'll have to do the same thing we're doing with entities and hardcode it per known move, creating a modal- and prompt-based multi step move flow.