Weird interaction between Mari, the Killing Quill and Etrata, the Silencer
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 940
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 160
Description
Mari, the Killin Quill exiled the same creature Etrata, the Silencer was targeting. I got the following report:
Game exception occurred: java.lang.IllegalStateException: Target wasn't handled in computer's choose method: mage.target.TargetCard
Server version: 1.4.52-V3-beta2 (build: 2023-04-01 15:07)
mage.player.ai.ComputerPlayer.choose(ComputerPlayer.java:502)
mage.player.ai.ComputerPlayer.choose(ComputerPlayer.java:129)
mage.target.TargetImpl.choose(TargetImpl.java:314)
mage.abilities.costs.common.RemoveCounterCost.pay(RemoveCounterCost.java:84)
mage.abilities.costs.CostImpl.pay(CostImpl.java:32)
mage.abilities.effects.common.DoIfCostPaid.apply(DoIfCostPaid.java:103)
mage.cards.m.MariTheKillingQuillDealsDamageEffect.apply(MariTheKillingQuill.java:120)
mage.abilities.AbilityImpl.resolveMode(AbilityImpl.java:200)
mage.abilities.AbilityImpl.resolve(AbilityImpl.java:184)
mage.abilities.TriggeredAbilityImpl.resolve(TriggeredAbilityImpl.java:151)
mage.game.stack.StackAbility.resolve(StackAbility.java:86)
mage.game.GameImpl.resolve(GameImpl.java:1657)
mage.game.GameImpl.playPriority(GameImpl.java:1583)
mage.game.turn.Step.priority(Step.java:61)
mage.game.turn.CombatDamageStep.priority(CombatDamageStep.java:31)
mage.game.turn.Phase.playStep(Phase.java:184)
mage.game.turn.Phase.play(Phase.java:89)
mage.game.turn.Turn.play(Turn.java:125)
mage.game.GameImpl.playTurn(GameImpl.java:1056)
mage.game.GameImpl.play(GameImpl.java:966)
mage.game.GameImpl.start(GameImpl.java:942)
mage.server.game.GameWorker.call(GameWorker.java:34)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.