You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like it if we could find a way to refactor effects so that the verify test deep (introduced for copy check, but it is doing a little more than that) looping through Card class can find oddities.
An option would be to have one instance of the added effect/ability as member of the class, and reuse/copy it on use. The instantitated one could be static in a lot of situations. Of course this would not help with every use case.
The JaceCunningCastawayDamageTriggeredAbility class is not covered by the Verify test suite.
The text was updated successfully, but these errors were encountered:
Susucre
changed the title
Verify test is blind to dynamically added Effect/DelayedTriggeredAbility
Verify test is blind to dynamically added Effect/Abilities
Apr 28, 2024
I would like it if we could find a way to refactor effects so that the verify test deep (introduced for copy check, but it is doing a little more than that) looping through Card class can find oddities.
An option would be to have one instance of the added effect/ability as member of the class, and reuse/copy it on use. The instantitated one could be static in a lot of situations. Of course this would not help with every use case.
To give an example with
DelayedTriggeredAbility
:mage/Mage.Sets/src/mage/cards/j/JaceCunningCastaway.java
Lines 75 to 79 in 8771d9b
The
JaceCunningCastawayDamageTriggeredAbility
class is not covered by the Verify test suite.The text was updated successfully, but these errors were encountered: