40 CARROTHow do you review a Warhammer 40K game and learn from your decisions?
Choose the decision that most changed your options, rebuild that exact position, and write what you expected at the time. Test one alternative while everything else stays fixed. Then turn the result into a cue you can recognize next game. The aim is a better repeatable decision, not a verdict on the final score.
What is the five-step 40K game review loop?
- Choose the decision. Find the deployment choice, staging move, target choice, trade, or scoring commitment that most narrowed what you could do next.
- Rebuild the position. Put down the relevant models, terrain marked as objectives, deployment zones, and measurements. Include only information you actually had.
- State the assumption. Write one sentence: “I chose this because I expected…” That separates the decision from the dice that followed.
- Test one alternative. Change one move, target, or reserve timing. Keep the opposing response and every other known fact fixed for the first comparison.
- Write the future cue. Use “When I see ___, I will ___ because ___.” That is the part you can carry into round one of the next event.
How do you criticize the play without rewriting it with hindsight?
Judge the decision using what was visible at the time. Separate three things: the information you had, the range of outcomes you could reasonably expect, and the result that happened. “I lost the unit” is an outcome. “I committed it before checking the return threat and scoring swing” is a reviewable decision.
Ask: “Which fact should have changed my choice?” Avoid: “Why am I bad at this matchup?” The first question points to a check you can repeat.
Which positions are worth capturing?
Full Access Snapshots are manual position keyframes. Capture the start of the turn, the decision point, and the position after the response only when those views will answer a real question. They are not an automatic action log and do not record dice, command points, or rules. A shared tabletop also excludes your private Snapshot timeline.
What should go in a reconstruction worksheet?
- Situation: turn, score pressure, objective, relevant units, reserves, and known resources.
- Choice: the move, target, trade, or sequence you selected.
- Expectation: what success looked like and which failure you accepted.
- Missed check: distance, line, counter-charge, coherency, return trade, or next-turn scoring.
- Alternative: one changed decision and the opponent’s most sensible answer.
- Future cue: the board feature that should trigger a different action next time.
How do you test whether the board assumption was wrong?
Use the real base sizes and terrain footprints. Check the gap instead of remembering it. Turn on the relevant movement, threat, coherency, objective, or line-of-sight view and ask whether the line still works. The overlays help inspect geometry; they do not replace current rules or tell you which play is correct.
If the question is damage rather than movement, use the free damage calculator to compare the expected range and wipeout chance. Keep the profiles and modifiers honest, then price the whole exchange rather than the first activation alone.
Why should you change only one variable first?
If you move three units, change the target, and alter the opponent’s response, you learn only that a different turn looks different. Start with the smallest useful fork: one unit starts 2 inches farther back, one screen moves first, or one activation changes targets. If that fixes the position, you have a clear lesson. If it does not, test the next variable.
What does a useful future trigger look like?
A good trigger is visible before the mistake. “When my trading unit cannot finish behind obscuring terrain after touching the center objective, I will stage instead of commit” is usable. “Trade better” is not. Connect a board cue to one action and one reason.
How can another player help with the review?
Send a read-only share link and one narrow question: “Is there a line that scores this objective without exposing both units?” The link is an immutable copy, so later edits to your tabletop do not change what they see. If you want two lines compared, send two labeled versions. For a full method, see how to practice with better players.
What does the review look like in a real scenario?
You commit a five-model unit to a neutral center objective, score, then lose both that unit and the support piece behind it. Rebuild the start of the turn. Test one alternative where the support piece stays outside the return threat, then another where the trading unit stages behind terrain. Compare current scoring, next-turn access, and what the opponent must expose to answer.
Frequently asked questions
What should I review after a 40K game?
Review the decision that most changed your options: a deployment choice, staging move, target choice, trade, or scoring commitment. Rebuild what you knew then, not what the final result later revealed. One well-tested decision is more useful than a turn-by-turn recap.
How soon should I review a game?
Write the decision and your reason soon after the game while the information is fresh. A deeper board review can happen later. A short note such as turn, objective, units involved, and expected outcome is enough to reconstruct the moment.
Do Snapshots automatically analyze my game?
No. Full Access Snapshots are position keyframes you create yourself. They do not record dice, command points, rules, or every action, and they do not judge the play. Capture only the positions you expect to compare later.
Should I review bad rolls?
Review the decision around the roll, not the unlikely result by itself. Ask whether the trade was good across the plausible range, whether you had a safer line, and what failure would cost. A poor roll can still follow a sound decision.
Can I send a review position to another player?
Yes. A read-only link sends an immutable copy of the complete multi-board tabletop without your private Snapshot timeline. Give the recipient one narrow question and include a separate version for each alternative you want compared.