We would like to improve the current interface after a spell or attack is begun. Currently there is a default behavior that we have reason to believe is not optimal for players and GMs to click through
Spend Spell: Autoroll dice (no button), play Automated Animation, show a single card with dice result and spell description
Show Spell: No dice, no animation, show a single card with spell description
We're inviting more suggestions, including mockups
Why?
This was sparked by the request in #381, which once implemented we noticed shows for both buttons when clicked because both buttons do nearly the same thing. I'd like to take a design-first approach by first asking the community what they think the optimal workflow is before code considerations, because we might not get a well-designed workflow with a code-first, think-later process.
Code of Conduct
[X] I agree to follow this project's Code of Conduct
I think this is a good way to do it. That way players can preview a spell's description without actually casting it, but when they choose to use it, modules like Maestro and Automated Animations can trigger! 👍
New Feature or Changed Behaviour
We would like to improve the current interface after a spell or attack is begun. Currently there is a default behavior that we have reason to believe is not optimal for players and GMs to click through
Old Behavior Spend Spell screen-recording-2023-03-29-at-111539.webm
Old Behavior Show Spell screen-recording-2023-03-29-at-112150.webm
Suggested New Behavior
Spend Spell: Autoroll dice (no button), play Automated Animation, show a single card with dice result and spell description Show Spell: No dice, no animation, show a single card with spell description
We're inviting more suggestions, including mockups
Why?
This was sparked by the request in #381, which once implemented we noticed shows for both buttons when clicked because both buttons do nearly the same thing. I'd like to take a design-first approach by first asking the community what they think the optimal workflow is before code considerations, because we might not get a well-designed workflow with a code-first, think-later process.
Code of Conduct