Card-Forge / Card-Forge/forge

Non-Siege Battle rules update

Open
#11,509 3 comments 0 reactions 0 assignees View on GitHub
Game Mechanics keep
Dominant language
Java
Stars
2.7k
Forks
1.1k
Avg merge
1d 1h
Merged PRs (30d)
163

Description

> 310.8. If a non-Siege battle’s defense is 0, it’s put into its owner’s graveyard. (This is a state-based action. See rule 704.)
>
> 704.5w If a non-Siege battle has defense 0, it’s put into its owner’s graveyard.
>
> 704.5x 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 the battle has no battle type, its controller must be chosen.** If no player can be chosen this way, the battle is put into its owner’s graveyard. See rule 310, “Battles.”

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by locating the battle state-based-action and rules handling for rules 310 and 704.5. Verify zero-defense non-Siege battles and battles without a battle type follow the listed graveyard and protector-selection outcomes.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.