"Stop skips on declare blockers" stops skips on declare attackers too.
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 940
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 160
Description
This is very annoying when it's not uncommon for Commander games to have 5-30 triggers going on the stack in the Declare Attackers step. I would love to have this split into "stop skips in Declare Blockers if [ANY/ZERO] blockers available" and "stop skips in opponents' Declare Attackers", so that I can leave the former turned on (and have the opportunity to block even if I'm on 'skip to my turn') and have the latter turned off most of the time.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the existing stop-skip handling for the Declare Blockers and Declare Attackers steps. Determine where the current setting applies to both phases, then separate the controls so blocker opportunities remain configurable independently from opponents' Declare Attackers stops; verify both behaviors in a Commander game with triggered abilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100