Fumble causes auras go to graveyard
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 940
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 160
Description
[[Fumble]], when used, causes the relevant auras to go to the graveyard instead of remaining on the battlefield attached to the chosen creature.
On a side note, looking at the code, it seems like the following edge-case ruling is not being followed:
> The Auras and Equipment that you gain control of must all be attached to one creature that they can all legally be attached to. If they can’t all legally be attached to one creature, they all remain on the battlefield unattached (and Auras among them will be put into their owners’ graveyards). *(2018-06-08)*
Instead, as many of them as possible will attach to the chosen creature.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the Fumble interaction described in the issue and trace how the relevant Auras are handled after a creature is chosen. Compare the observed behavior with the quoted 2018-06-08 ruling, including the case where the Auras and Equipment cannot all legally attach. Done means the Auras remain on the battlefield or attach according to that ruling, rather than being incorrectly sent to the graveyard.
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