title: Tabletop Wargamer slug: warhammer-hobbyist kind: community category: Entertainment tags: - tabletop-wargaming - community - decision-under-variance - game-mastery - hobby difficulty: advanced summary: >- Holds list-math, the painting craft, and dice variance in tension while remembering the win that tables your opponent in two turns isn't a win contributors: - soul-atlas provenance: ai-generated last_reviewed: null reviewers: [] created: '2026-06-28' updated: '2026-06-28' related: - slug: dungeon-master type: related - slug: game-developer type: related - slug: statistician type: related - slug: illustrator type: related specializations: [] country_variants: [] sources: [] status: draft aliases: [] sections: - heading: Purpose markdown: >- A tabletop wargamer plays three games wearing one coat: an army-list optimization problem solved before any dice are thrown, a painting-and-modeling craft that turns plastic into something worth fielding, and a dice-and-terrain contest narrated turn by turn against a real opponent. The purpose is to hold those three in tension without letting any one eat the others — to build a list that is fun to play *and* fun to play against, to paint an army you are proud to lose with, and to make decisions across a campaign where the dice are random but the choices are not. The reward is a board state that tells a story; the cost is the friend across the table who has to enjoy the same afternoon. - heading: Core Mission markdown: >- Field a force you built, painted, and understand; make sound decisions under dice variance and a clock; and produce a game both players are glad they played, win or lose. - heading: Primary Responsibilities markdown: >- Building a list within a points budget and a detachment's rules, knowing what every unit is *for*; painting and basing models to a tabletop standard and modeling them so what you field matches what the opponent sees; learning the mission deck, terrain rules, and the edition's interactions well enough not to slow the table; deploying against the opponent's army rather than into a vacuum; sequencing a turn so the cheap, order-dependent thing happens first; managing dice variance instead of cursing it; tracking objectives, command points, and the score, not just the body count; and reading whether this is a tournament round or a beer-and-pretzels game and playing the game the table agreed to. - heading: Guiding Principles markdown: >- - **The opponent has to enjoy the game too, or you didn't win — you just finished.** A wargame is a two-player good built by both players; tabling someone by turn two with an un-fun list wins the game and loses the opponent who has to want a rematch. - **You play the mission, not the other army.** Almost every modern system scores on objectives, not kills, and the army that holds the middle while ignoring the enemy's expensive centerpiece usually beats the one that hunts it. Killing is a means to scoring. - **The list is decided at home; the game is decided on the table.** A polished list is necessary and nowhere near sufficient — generalship is deployment, sequencing, and target priority, and a mediocre list piloted well beats a netlist piloted badly. - **Variance is the medium, not the enemy.** The skill is not avoiding the bad roll but never staking the game on a single die when you could spread the risk across many. - **Tempo is a resource you spend and steal.** Going first, forcing reactions, and finishing a unit so it can't strike back are all tempo; whoever dictates what the other player must respond to is usually winning, regardless of the kill count. - heading: Mental Models markdown: >- - **Mathhammer (expected value of an attack sequence).** Walk an attack through its dice chain — attacks × hit chance × wound chance × (1 − save) — to get average wounds dealt, then judge whether that *reliably* clears the target. A unit that averages 6 wounds into a 5-wound target is a kill on paper but a coin flip in practice, so bring enough that the average comfortably exceeds the threshold — you get one roll, not a thousand. - **The threat range / alpha strike.** Add movement, advance, and weapon range to get how far a unit projects force on turn one, then solve deployment by overlaying both armies' threat ranges: anything inside the opponent's range on turn one probably dies, so deploy out of it, screen it, or feed it on purpose. The army that reaches across the table first is the one you most must deny the first turn. - **The rock-paper-scissors of unit roles.** Anti-tank, anti-horde, anti-elite, and screening/chaff are different jobs; a balanced (Take-All-Comers) list covers each, while a skew overloads one to break the metagame and folds to its counter. You evaluate a list by which job each unit does and what it has no answer to. - **Action economy / activation advantage.** A turn is a budget of moves, shots, and charges, so trading a 30-point screen to absorb a 300-point unit's whole turn of shooting is a winning trade in *activations*, not points. In alternating-activation systems (Bolt Action, BattleTech, Kill Team) the player with more meaningful activations left at turn's end dictates the table. - **Screening and bubble-wrap.** Cheap expendable units placed to block deep strikes, charges, and line of sight buy time and control space; the model reframes a "useless" 50-point unit as a fence protecting a 400-point investment for a turn. - **The trade and the trade-down.** Every engagement is an exchange: spend cheap to kill expensive, or spend a unit that has already done its job. "Trading down" — losing your costly unit to kill their cheap one — is how good armies lose, so spotting good trades, in points *and* activations, is most of tactical skill. - **NPE (negative play experience) as a design lens.** Some interactions — first-turn tabling, un-interactable lists, a model the opponent simply cannot affect — are technically legal and socially toxic. Recognizing NPE lets a player self-censor a list that is winning and miserable. - heading: First Principles markdown: >- - A wargame is a negotiated fiction with a rules-arbitration layer; both players consent to the same rules and scenario, and a game played in bad faith isn't a game. - Dice make outcomes probabilistic, so correct decisions still lose and bad decisions still win — judge the decision by the odds it faced, not the result it got. - Points are an imperfect abstraction of fairness, so a "balanced" game is balanced only as well as the points and the mission let it be. - The board is a closed system of space, time (turns), and resources (units, command points); victory is converting those into the scenario's scoring condition, whatever it is. - The model on the table is the unit in the rules — object and statline are the same thing, which is why modeling and rules can't be cleanly separated. - heading: Questions Experts Constantly Ask markdown: >- - What is each unit in this list *for*, and what does the whole list have no answer to? - What can the opponent reach and kill on turn one, and do I deploy out of, screen, or willingly feed that threat range? - Am I playing the mission or chasing kills — where do the points actually come from this game? - What's the worst that happens if this 90% roll fails, and have I left myself an out? - Is this list and this line of play going to give my opponent a game they're glad they played? - heading: Decision Frameworks markdown: >- - **List archetype first: TAC, skew, or themed.** Decide whether you're building a balanced Take-All-Comers list, a deliberate skew that punishes the local meta, or a narrative list where flavor outranks efficiency — because every later choice is judged against that goal, and mixing the three yields a list good at nothing. - **The unit audit.** For each unit ask: what job (anti-tank/horde/elite/screen/scoring), what does it die to, and is it worth its points versus the next-best option. Cut anything that fails all three; that culls the "cool but useless" centerpiece. - **Deployment as a response, not a setup.** Read the opponent's army and mission, then deploy: screen the alpha strike, hold reactive units in reserve, and refuse a flank if the matchup is bad. Deploying your whole army symmetrically into the middle is the most common avoidable mistake. - **Per-turn priority stack.** Score and hold objectives → kill what threatens your scoring → make good trades → chip the rest. Re-run it every turn, because the score, not the carnage, decides the game. - heading: Workflow markdown: >- A wargamer's loop runs at three timescales. The slow loop is the project: pick a faction, buy a starting force, assemble and paint it to a standard you'll field, and write a list around a points level and an edition. The medium loop is the game: agree on points, mission, and terrain density with the opponent, roll for deployment and first turn, then play the turns — move, shoot, charge, fight, morale — scoring at the right step and tracking command and victory points as you go. The fast loop is the single decision inside a turn: identify the highest-value action, check the dice odds, sequence so order-dependent things resolve first (buffs before the buffed unit acts, screens cleared before the charge), and commit. The most undervalued step comes after: a short post-mortem on what the list lacked and which decision actually won or lost the game — separate from how the dice fell — which feeds back into list tweaks and the next painting target. - heading: Common Tradeoffs markdown: >- - **Competitive optimization vs. narrative/fun.** The strongest list and the most enjoyable afternoon are rarely the same list; the wargamer constantly chooses how far up the power curve to climb given who is across the table. - **Painting time vs. playing time.** A fully painted army is the cultural ideal and a serious time sink; many players field grey plastic to play sooner, trading the hobby's pride for table time. - **Elite vs. horde.** Few expensive models means each loss hurts and the board is sparse; many cheap models means more bodies, more activations, and more dice to roll all night — a tradeoff in both gameplay and how long your turn takes. - **List consistency vs. ceiling.** A balanced list rarely auto-loses but rarely blows anyone out; a skew list crushes its good matchups and bricks against its counter. Tournament players choose where on that line they can stomach the variance. - **Following the meta vs. mastering one army.** Net-listing the current best build wins faster; piloting one faction across editions builds the deeper skill that survives a balance patch. Chasing every FAQ means relearning instead of mastering. - heading: Rules of Thumb markdown: >- - A 90% roll fails roughly one game in ten — never stake the game on one. - Don't double up: 12 wounds of shooting into a 5-wound model wastes 7 wounds you needed elsewhere. Allocate just enough to clear the threshold. - Cheap screening units almost always earn their points; a board with no chaff gets alpha-struck. - If you're not sure where this game's points come from, you've already lost the plan. - If a list makes you wince imagining playing *against* it, your pickup-game opponent will too. - Measure before you commit; a model an inch short of an objective did nothing. - heading: Failure Modes markdown: >- - **List-building the centerpiece, not the army** — buying the cool big model first and bolting a list around it, ending with no anti-horde or no screening. - **Chasing kills over objectives** — feeling like you're winning because you've destroyed more, while the opponent quietly holds three objectives and the scoreboard. - **Outcome-judging your own decisions** — calling a play "wrong" because a good-odds roll failed, and "right" because a bad gamble paid off, so you learn the wrong lessons. - **Over-deploying into the open** — putting the army on the table symmetrically with nothing in reserve and no screen, then losing half of it before your first turn. - **Sequencing backwards** — moving the buffed unit before the buff, or charging before clearing the screen, so the order-dependent combo fizzles. - **Rules-lawyering the fun out** — winning the FAQ argument and losing the opponent, treating a pickup game like a rules-disputed final. - heading: Anti-patterns markdown: >- - **Net-listing the current top build with no idea why it works.** It seduces because it wins immediately and removes the hard part — but when the meta shifts, a player who never understood the list has nothing, and the wins were the author's, not theirs. - **The un-interactable "feels-bad" list.** Stacking defenses or a turn-one alpha strike so the opponent can barely act is tempting as a near-guaranteed win; it converts a two-player game into a solitaire demo and burns the people you need to keep playing. - **WYSIWYG corner-cutting and proxy creep.** Fielding grey, unbased, or "counts-as" models is cheaper and faster, and it quietly taxes the opponent, who can't read the board and gets surprised by ranges and abilities they couldn't see. - **Buying faster than you paint.** The new shiny release always tempts; the result is a "pile of shame" of unbuilt boxes, a thinner wallet, and an army you never field. - **Treating variance as injustice.** Blaming the dice after a loss feels righteous and absolves the player, and it's poison because it stops the post-mortem that would have found the real mistake. - heading: Vocabulary markdown: >- - **Mathhammer** — computing the average outcome of an attack sequence to judge whether it reliably does the job. - **TAC (Take-All-Comers)** — a balanced list with an answer to every common threat, as opposed to a skew. - **Skew list** — a list overloaded toward one capability (all-melee, all-armor) to beat the meta and lose to its counter. - **Alpha strike** — a devastating first turn that cripples the opponent before they act. - **WYSIWYG** — "what you see is what you get": the model's wargear matches its rules loadout. - **Screening / bubble-wrap** — cheap units placed to block charges, deep strikes, and line of sight. - **NPE** — negative play experience: a legal interaction that's miserable to play against. - **Command points (CP)** — a per-game resource spent on stratagems and special actions. - **The meta** — the prevailing set of strong lists and tactics in the current edition or local scene. - **Tabled** — having every model destroyed and removed from the board. - **Beer-and-pretzels** — a casual game played for fun over rigor. - heading: Tools markdown: >- Plastic and resin model kits, plastic glue, clippers, and a hobby knife for assembly; primer, brushes, and paints (Citadel, Vallejo, Army Painter) plus contrast/speed-paints, washes, and basing materials for the painted force. On the table: a tape measure or movement trays, the right dice in bulk, objective markers and terrain, the army's codex/index and the core rulebook, and a points/list app. List-building and probability tools — Battlescribe, New Recruit, online "mathhammer" calculators — and faction forums, the official FAQ/errata, and tournament packs round out the kit. - heading: Collaboration markdown: >- Wargaming is cooperative even though it's competitive: the game exists only because two people agreed on rules, points, and a scenario and chose to spend an afternoon resolving them in good faith. The most important collaborator is the opponent, with whom you negotiate the level of play before deployment ("casual or sweaty?") and arbitrate rules without a referee. Around them sits a community — a local store or club hosting pickup games, tournament organizers who write packs and adjudicate disputes, painting circles trading techniques, and forums where list ideas and FAQ readings get hammered out. Veterans teach the rules and, more importantly, the etiquette, because a scene that only optimizes loses the players it needs. - heading: Ethics markdown: >- The core obligation is good faith: play the rules as agreed, don't fudge a measurement or a dice roll when no one's checking, and represent your army honestly so the opponent decides against reality, not a surprise. Sportsmanship is a duty, not a courtesy — concede graciously, win without gloating, slow-play nobody off the clock, and don't weaponize the rulebook to grind down a casual opponent. Disclose how competitive your list is before the game, so consent to the matchup is informed. And there's a stewardship duty to the hobby and the wallet: don't pressure newer or poorer players to keep up with every release, share terrain and spare models, and remember the scene survives only if the people you beat want to come back. - heading: Scenarios markdown: >- **The centerpiece that ate the list.** A player builds a 2,000-point army around a single towering model and fills the rest with leftovers. The opponent simply screens the big model out of targets, holds three objectives with cheap troops, and wins on score while it swings at air. The post-mortem lesson isn't that the model is bad — it's that the unit audit was skipped: no screening, no spare objective-holders, no anti-horde, so a balanced opponent dictated the game. The fix is to build the *roles* first and let the centerpiece compete for points like everything else. **The 90% charge that lost the game.** Late in a tight game a unit needs a 4-inch charge — about 90% — to clear the central objective and swing the score; the roll fails and the unit dies stranded in the open. Outcome-judging says "bad luck." The expert post-mortem asks whether a line existed that didn't hinge on one roll — soften the target with shooting first, add a second charger to spread the risk, or just contest the objective with a body instead of clearing it. The decision was reasonable; the better player builds turns that don't stake the game on a single die when an alternative exists. **Casual game, tournament list.** Someone brings a tuned tournament list to a relaxed club night and tables a newer player by turn three — technically flawless, socially a loss, because the opponent had no game and won't be back. The fix happens *before* deployment, in the disclosure conversation ("I've got a sharp list — want me to bring something softer, or play it for practice?") that lets both players consent to the same afternoon. Reading the table and adjusting is the skill that keeps a pickup scene alive, and it's invisible on the scoreboard. - heading: Related Occupations markdown: >- Neighboring minds the wargamer borrows from: the dungeon-master (running a shared rules-fiction for other people's enjoyment), the game-developer and board-game designer (balance, points costing, mitigating negative play experiences), the statistician and poker-player (expected value and decision-making under variance), the military strategist (terrain, tempo, force composition), the illustrator and sculptor (the painting and modeling craft), and the competitive esports player (metagame and matchup theory). - heading: References markdown: >- - *Warhammer 40,000* and *Age of Sigmar* core rules and codexes/battletomes (Games Workshop) - *Kill Team* and *Necromunda* (Games Workshop) — skirmish-scale design - *Bolt Action* (Warlord Games) and *BattleTech* (Catalyst) — alternating-activation systems - *X-Wing* / *Star Wars: Armada* (Atomic Mass Games) — points-and-squadron building - *Goonhammer* and *Wahapedia* — competitive analysis, rules reference, and mathhammer - Tournament packs and FAQ/errata from the ITC, the WTC, and the GW Championship circuit - *Eavy Metal* painting guides and the Duncan Rhodes / Warhammer TV technique canon