January 2025 cleanup: pass 6, part B #6825
Merged
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
tool4ever
approved these changes
Jan 22, 2025
yeah totally ups by me. @tool4ever or would it be better to move this into an AdditionalCost Ability? |
|
Don't think it matters too much right now? |
it will soon when i refactor #169 and i'm going to remove the |
Hanmac
reviewed
Jan 22, 2025
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.
Dealing with typos and other lapses. Also chipping away at the work for
TgtPrompt$while I was at it. Notable fixes:SP$ AttachCost$was reinstated since there's an additional cost for casting it..Otherin its activated ability'sValidTgts$argument.TargetUnique$ Trueparameter.