-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
RFC: Initiative Tracker Layouts #276
Comments
When doing this, please include conditions. The default conditions are DnD5e. Changing the game system should also update the conditions tracked. And then still offer the capability to add custom conditions. E.g. my use case is I play Pathfinder 2e, and would like to be able to select Pathfinder conditions from a dropdown. But to help me keep track of e.g. breath weapon cooldowns, I have a custom condition called Cooldown #. |
To add to this, it'd be nice if there was a way a condition could actually apply to a stat block. For instance, if a creature is Restrained, then it's speed would be set to 0. This sort of feature is more useful for systems like pf2e, where most conditions alter the statblock in some way (for instance, Off-Guard in pf2e reduces AC by 2). This could also be used potentially to extend to things like Elite/Weak adjustments, mentioned here on fantasy-statblocks. I can imagine it'd be quite painful to implement this, because you'd need to display different versions of the same statblock for creatures with different conditions (like if you have Wolf 1 who is Restrained, and Wolf 2 who isnt). |
Initiative Tracker was created for DnD 5e specifically. While it has been updated to mostly work generically, there is still quite a bit about it that is meant to use for 5e and its derivatives.
A layout system akin to the Fantasy Statblocks layout maker would alleviate some of these issues by allowing custom layouts to be created (and bundled). These custom layouts could change the what fields are displayed in the tracker and in what order.
The text was updated successfully, but these errors were encountered: