Austere Command instructions not performed in correct order.
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 940
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 160
Description
I played an [[Austere Command]] choosing to destroy all enchantments and all creatures with mana value 3 or less.
One opponent controlled an [[Oubliette]] which had targeted another opponent's [[Serra Ascendant]].
Austere Command should have destroyed the Oubliette, causing the Serra Ascendant to phase in tapped, and then the Austere Command should have destroyed the Serra Ascendant. But somehow the Serra Ascendant survived.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by reproducing the reported interaction between Austere Command, Oubliette, and Serra Ascendant, then trace how the two destruction choices and phasing are resolved. Done means the Serra Ascendant is destroyed after Oubliette leaves play and the card interaction is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100