4.2 KiB
Reflection Template For Dredgeless Dredge
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: Identify whether the game was decided by graveyard velocity, recursive pressure, mana pain, opposing hate, combat tempo, or failure to close after early setup. Record the exact turn where the game shifted and the visible board or stack state that caused the shift.
-
Mulligans: Check whether kept hands had colored mana plus either
Stitcher's Supplier,Otherworldly Gaze,Dredger's Insight,Timeline Culler, or a castable pressure plan. Flag keeps that had only recursive payoffs likeBloodghast,Prized Amalgam,Silversmote Ghoul, orCreeping Chillwith no reliable way to move cards into the graveyard. -
Mana: Review every life payment from
Mana Confluence,Watery Grave,Overgrown Tomb, andBreeding Pool. Mark payments as correct only when they enabled a meaningful spell, recursion sequence, sideboard answer, or lethal/survival line. -
Velocity: Measure whether
Stitcher's Supplier,Otherworldly Gaze,Dredger's Insight, andTimeline Culleractually converted into battlefield pressure or life swings. Card text check required forDredger's InsightandTimeline Cullerwhen judging exact tactical outcomes. -
Engine conversion: Track how often graveyard setup produced
Bloodghastreturns,Prized Amalgamreturns,Silversmote Ghoulreturns,Creeping Chilldrains,Willow Geistpressure, orSouls of the Lostpressure. A self-mill turn that does not produce pressure, interaction, or future inevitability should be tagged as low conversion. -
Removal and disruption: Evaluate whether
Witherbloom Command,Fatal Push,Duress, andTear Asunderwere aimed at the visible card or permanent most responsible for the opponent's plan. Note any use on a low-impact target while a hate piece, lethal attacker, combo enabler, or sweeper remained the real problem. -
Sideboard execution: Check whether each sideboarded card matched a proven opponent axis.
Leyline of the Voidshould answer graveyard reliance,Damping Sphereshould answer spell chains or big mana,Fatal Pushshould answer creature pressure,Duressshould answer hidden noncreature pressure,Tear Asundershould answer artifacts or enchantments, and extraWitherbloom Commandshould have relevant legal modes. -
Closing: Record whether the deck turned early graveyard setup into lethal pressure quickly enough. Flag games where repeated setup actions delayed attacks from
Bloodghast,Prized Amalgam,Silversmote Ghoul,Willow Geist, orSouls of the Lostdespite a clear damage race. -
Role: Decide whether the pilot correctly played as aggressor, stabilizer, disruption-plus-clock, or hate-aware midrange deck. Mark role mistakes where the pilot raced a faster board, over-defended against control, or diluted the engine against an opponent without relevant hate.
-
Mistakes: Note any missed land-drop sequencing for
Bloodghast, missed attack opportunities with recursive creatures, unnecessary shock-land orMana Confluencedamage, premature self-mill into graveyard hate, or failure to hold interaction for a higher-impact visible threat. -
Stranded cards: List cards stuck in hand and why they failed: wrong colors, no legal targets, graveyard hate, low battlefield relevance, or timing constraints. Separate stranded main-deck cards from stranded sideboard cards so tuning does not blame the wrong package.
-
Overperformers and underperformers: Identify which exact cards changed outcomes rather than which cards merely appeared often. Give special attention to
Creeping Chill,Bloodghast,Prized Amalgam,Silversmote Ghoul,Willow Geist,Souls of the Lost,Witherbloom Command, and each sideboard card.
Existing User Requests
No additional user reflection requests were supplied.