StaticAbility InfectDamage for Phyrexian Unlife#7108
Merged
Conversation
29 tasks
tool4ever
approved these changes
Mar 2, 2025
Contributor
tool4ever
left a comment
tool4ever
left a comment
There was a problem hiding this comment.
Even when combined into one class technically it should still be two modes?
Also I wonder if some AI checks should be updated to consider it or if the overhead without KW isn't worth it...
Contributor
Author
|
Yes still two modes I don't know if AI needs more update, but we can do that later |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Changes Phyrexian Unlife into a Static Ability
or should this new class be merged with StaticAbilityWitherDamage? (WitherDamage uses Source, this uses Target)