Curse of Silience used on a known card in the graveyard in commander #33

New Issue

bstein · 2026-07-10T19:51:48Z

bstein commented

2026-07-10 19:51:48 +00:00

What happened

Commander is a singleton format. So there are only single copies of every card in each deck. Using Curse of Silence on an already card (unless it has flashback or something like this to allow it to be recast from the graveyard) is pretty much a huge waste of this card.

What should have happened

In a commander format this is probably meant to make the commander itself more expensive to bring in, or some card that the casting player knows the other player has and is important, and will be castable again in the future. Agent players should be aware of the other player's decklist when selecting a card like this. This is a very unique circumstance but it still needs a general solution - solutions cannot be specific for individual cards in the engine - card specific rules can only be in strategy specific content (its guide).

Context

Page URL: https://veles.bstein.dev/table?path=/data/veles-artifacts/logs/dashboard/sp0619-phage-s2026072321-v2-lazav-v22-phelia-v15/duel_commander_phelia_exuberant_shepherd__15_g1_2026072321/game.jsonl
Route: table
Path: /table?path=/data/veles-artifacts/logs/dashboard/sp0619-phage-s2026072321-v2-lazav-v22-phelia-v15/duel_commander_phelia_exuberant_shepherd__15_g1_2026072321/game.jsonl
Backend version: 0.6.21
Frontend version: 0.6.21
Sim version: 0.6.21

## What happened <img width="1440" alt="image.png" src="attachments/ffb69ac5-37d4-4c5d-b42a-c1baf6cd35fa"> Commander is a singleton format. So there are only single copies of every card in each deck. Using Curse of Silence on an already card (unless it has flashback or something like this to allow it to be recast from the graveyard) is pretty much a huge waste of this card. ## What should have happened In a commander format this is probably meant to make the commander itself more expensive to bring in, or some card that the casting player knows the other player has and is important, and will be castable again in the future. Agent players should be aware of the other player's decklist when selecting a card like this. This is a very unique circumstance but it still needs a general solution - solutions cannot be specific for individual cards in the engine - card specific rules can only be in strategy specific content (its guide). ## Category - kind: misplay - severity: obvious ## Context - Page URL: https://veles.bstein.dev/table?path=/data/veles-artifacts/logs/dashboard/sp0619-phage-s2026072321-v2-lazav-v22-phelia-v15/duel_commander_phelia_exuberant_shepherd__15_g1_2026072321/game.jsonl - Route: table - Path: /table?path=/data/veles-artifacts/logs/dashboard/sp0619-phage-s2026072321-v2-lazav-v22-phelia-v15/duel_commander_phelia_exuberant_shepherd__15_g1_2026072321/game.jsonl - Backend version: 0.6.21 - Frontend version: 0.6.21 - Sim version: 0.6.21

image.png

974 KiB

bstein added the

pilot/veteran

kind/misplay

severity/obvious

labels 2026-07-10 19:51:48 +00:00

bstein commented

2026-07-10 21:09:52 +00:00

Verified fixed and deployed in Cassandra 0.6.22.

Proof:

Cassandra 0.6.22 is live: /api/v1/app-config reports backend/frontend/sim_worker 0.6.22; /api/v1/ready is ok with config/database/storage/queue ready; backend and both frontend pods are Running with 0 restarts.
Regression coverage: PYTHONPATH=src python3 -m unittest tests/test_playtest_decisions.py tests/test_misplay_audit.py tests/test_atomic_decision_eval.py -q ran 405 tests OK; strategy-program suite ran 116 tests OK; feedback replay audit reports the exact six expected findings and atomic evaluator flags decision 15.
Runtime safety now replaces singleton/Commander cast-affecting card-name choices when the chosen card is only visible in the targeted opponent's public graveyard and lacks a visible recast hook. It preserves true exceptions such as the named card's own flashback/escape/retrace/jump-start or visible global graveyard-cast permission, and refuses to guess in multiplayer if the targeted opponent/source cannot be recovered.

Closing this misplay issue.

Verified fixed and deployed in Cassandra 0.6.22. Proof: - Cassandra 0.6.22 is live: /api/v1/app-config reports backend/frontend/sim_worker 0.6.22; /api/v1/ready is ok with config/database/storage/queue ready; backend and both frontend pods are Running with 0 restarts. - Regression coverage: PYTHONPATH=src python3 -m unittest tests/test_playtest_decisions.py tests/test_misplay_audit.py tests/test_atomic_decision_eval.py -q ran 405 tests OK; strategy-program suite ran 116 tests OK; feedback replay audit reports the exact six expected findings and atomic evaluator flags decision 15. - Runtime safety now replaces singleton/Commander cast-affecting card-name choices when the chosen card is only visible in the targeted opponent's public graveyard and lacks a visible recast hook. It preserves true exceptions such as the named card's own flashback/escape/retrace/jump-start or visible global graveyard-cast permission, and refuses to guess in multiplayer if the targeted opponent/source cannot be recovered. Closing this misplay issue.

bstein closed this issue

2026-07-10 21:09:53 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cassandra-alpha/feedback#33