Battles protected by removed player can't be attacked
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 940
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 160
Description
[704.5w.](https://yawgatog.com/resources/magic-rules/#R7045w) If a battle has no player in the game designated as its protector and no attacking creatures are currently attacking that battle, that battle's controller chooses an appropriate player to be its protector based on its battle type. If no player can be chosen this way, the battle is put into its owner's graveyard. See rule 310, "Battles."
Thus when a defending player dies, a new protector should be chosen until no opponents are left.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how battles select a protector after a defending player is removed, using rules 704.5w and 310 as the behavioral references. Reproduce the multiplayer case described in the issue and verify that a new protector is selected, or that the battle is put into its owner's graveyard when no eligible player remains.
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