Proof of concept for displaying reaction limit #3278
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
How are you handling stuff like some of the special characters who give an extra in multiple phases if something happens or doesn't happen. Or restricting which reaction could be used? |
I'm not currently, for those I imagine we could just add a specific override for "append *" by checking if the specific trait ID is in the roster. Currently I just did the default warlord traits. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Edit: I redid this to use categories instead of costs so this now works and looks good. It's still a proof of concept because I only did it on the generic warlord traits, we'd have to go through and add it to every warlord trait.
