32 lines
3.8 KiB
Markdown
Raw Normal View History

2026-06-19 18:54:22 -03:00
# Reflection Template For Ninjas
2026-06-14 15:24:54 -03:00
2026-06-19 18:54:22 -03:00
For each loss, name one primary cause and one secondary cause.
For each win, name the card, package, or tactical policy that most contributed to the win.
Classify each result as a card quantity problem, card selection problem, mana problem, tempo problem, matchup problem, sideboard problem, pilot sequencing problem, or closing-power problem.
Report mana performance, sideboard impact, stranded cards, overperforming cards, underperforming cards, and whether the Deck Strategy or Tactical Policy guidance was followed.
- Deciding factor: Did the game turn on the first successful Ninja connection, a protected `A-Moon-Circuit Hacker`, a high-impact `Yuriko, the Tiger's Shadow` attack, a `Kaito, Bane of Nightmares` board state, or a disruption exchange involving `Force of Negation`, `Fatal Push`, `Snuff Out`, or `Sink into Stupor`?
- Mulligans: Did the kept hand contain a castable enabler such as `Ornithopter`, `Changeling Outcast`, or `A-Thousand-Faced Shadow`, plus either payoff, interaction, or a clear mana plan? Record any keep that lacked pressure, lacked black mana, lacked blue mana, or relied on a single fragile card.
- Mana: Did `Watery Grave`, `Darkslick Shores`, `Prismatic Vista`, `Island`, `Swamp`, `Gloomlake Verge`, or `Otawara, Soaring City` produce the colors needed on the critical turn? Flag any turn where `Lórien Revealed`, `Sink into Stupor`, or `Force of Negation` was stranded by sequencing or color constraints.
- Velocity: Did `A-Moon-Circuit Hacker`, `Yuriko, the Tiger's Shadow`, `Lórien Revealed`, or `Kaito, Bane of Nightmares` convert early damage into enough cards to keep interaction flowing? Note whether the deck ran out of action after trading one-for-one.
- Engine pressure: Did `A-Silver-Fur Master` change the turn by improving attack damage, enabling cheaper Ninja deployment, or making multiple plays possible? Card text check required for `Hydroponics Architect`; log whether its visible role advanced the Ninja plan or felt disconnected.
- Removal quality: Did `Fatal Push`, `Snuff Out`, `Dismember`, or `Toxic Deluge` answer the creature that mattered most, or were they spent on low-impact blockers? Record life paid to `Snuff Out`, `Dismember`, and `Toxic Deluge` when that life changed the race.
- Counter/discard quality: Did `Force of Negation` or `Thoughtseize` stop the opponent's decisive noncreature spell, protection, sweeper, combo piece, or stabilizer? Mark any use that traded for a spell the deck could have ignored while continuing pressure.
- Sideboard effect: Did `Thoughtseize`, `Damping Sphere`, `Barrowgoyf`, `Dismember`, `Toxic Deluge`, or `Leyline of the Void` materially change the matchup, or did sideboarding dilute evasive pressure? Track every sideboard card drawn and whether it improved the actual board or stack.
- Closing: Did the deck finish quickly after establishing advantage, or did the opponent get extra draw steps because the pilot protected resources instead of attacking? Record stalled games where `Kaito, Bane of Nightmares`, `Yuriko, the Tiger's Shadow`, or repeated Ninja attacks were unavailable or mis-sequenced.
- Role and mistakes: Did the pilot correctly identify when to be the aggressor, when to conserve interaction, and when to race? List concrete mistakes: missed attack, wrong ninjutsu timing, unnecessary shock, premature `Force of Negation`, poor `Sink into Stupor` target, or overextension into a public sweeper window.
- Stranded and swing cards: Which cards were stranded, overperformed, or underperformed? Track `Hydroponics Architect`, `Lórien Revealed`, `Kaito, Bane of Nightmares`, `Snuff Out`, `Sink into Stupor`, `Barrowgoyf`, `Damping Sphere`, and `Leyline of the Void` separately by matchup.
## Existing User Requests
No additional user reflection requests were supplied.