Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Status-es that auto-reset when new round start (e.g., for "Reacted") #139

Closed
dfaggioli opened this issue Apr 22, 2023 · 0 comments · Fixed by #140
Closed

Comments

@dfaggioli
Copy link
Contributor

A good example for this is the pre-defined "Reacted" condition. I think it's quite cool to use Statuses to track things like this, i.e., in this case, reactions. Like, creature Foo reacted, I give it the "Reacted" Status. Then creature Bar and Foobar react as well, and I give them the Status too. The rest of the creatures did not use their reaction in this round.

Now, new round start, and I need to go manually through the entire list of creatures of the encounter and remove the "Reacted" Status from the one that have it.

How about we add a checkbox (something like "Automatically resets on new Round", or something like that), in the 'Edit Status' modal (when defining/modifying Statuses). And if it's set, when a new round is started, the Status is automatically removed from all the creatures that have it (while, of course, nothing happens to the ones that don't).

This would spare to the DM the effort of scrolling the (potentially long) list of creatures in the encounter and manually act on them.

FTR, in the game I'm playing, there's no reaction, but creatures have one chance per round to try to "Dodge" a hit. Which I'm modelling with Statuses, exactly like with "Reacted"... And it's awesome, except for the part that I need to remember to do the removal pass at the start of each round. And if I don't, then I'm not sure whether a creature really "Dodge"-ed already this round, or it it's just me forgetting to remove the Status from previous one, which is annoying and looks like it could actually be automated. :-P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant