And ideally # of combats - both for analytics, and so that we can persist knowledge about surge and skill check rotations across combat.
The really tricky thing here will be knowing when to clear this. For example, it should be easy in a quest - keep it as part of the quest state, and drop the quest state when you leave the quest. But the way we currently do GM mode (hopping backwards on victory and defeat) would require an unhealthy amount of duct tape to RETURN. Perhaps we instead adjust GM mode to behave more like quests, where it keeps moving forward in state? Perhaps injecting a single roleplaying card between each fight? (which could be handy once we have skill checks, so that the DM could choose either a combat or skill check next...)
smartin015
commented
6 years ago
And ideally # of combats - both for analytics, and so that we can persist knowledge about surge and skill check rotations across combat.
The really tricky thing here will be knowing when to clear this. For example, it should be easy in a quest - keep it as part of the quest state, and drop the quest state when you leave the quest. But the way we currently do GM mode (hopping backwards on victory and defeat) would require an unhealthy amount of duct tape to
RETURN. Perhaps we instead adjust GM mode to behave more like quests, where it keeps moving forward in state? Perhaps injecting a single roleplaying card between each fight? (which could be handy once we have skill checks, so that the DM could choose either a combat or skill check next...)