---
id: tabletop-systems
status: active
supersededBy: []
lang: en
title: 'Cards, dice and tabletop mechanics'
description: >-
  Tabletop mechanisms allocate limited actions and hidden information through
  cards, dice, positions and commitments.
intro: >-
  Tabletop mechanisms allocate limited actions and hidden information through
  cards, dice, positions and commitments. Each overview separates player
  actions, state changes and alternative rules. Examples are hypothetical design
  scenarios, not claims about a named game. A prototype check states an
  observable question for the next iteration. Existing detailed references
  remain separately linked from the direction map.
updatedAt: '2026-10-21'
sources:
  - title: 'PuzzleScript: Rules'
    url: 'https://www.puzzlescript.net/Documentation/rules.html'
    description: The creator’s documentation of pattern replacement and board state.
  - title: 'Wizards of the Coast: Magic rules'
    url: 'https://magic.wizards.com/en/rules'
    description: >-
      Primary example of formal card-game rules, with separate basic and
      comprehensive references; not a description of all mechanisms below.
counts:
  families: 10
  branches: 10
  variants: 40
url: 'https://gamemechanics.pro/en/mechanics/tabletop-systems/'
markdownUrl: 'https://gamemechanics.pro/content/mechanics/en/tabletop-systems.md'
license: CC-BY-4.0
codeLicense: MIT
attribution: gamemechanics.pro contributors
provenance: >-
  Original bilingual editorial overviews authored for gamemechanics.pro on
  2026-10-20 and reviewed on 2026-10-21. Scenarios are hypothetical design
  examples; prototype checks describe work to perform, not completed playtests.
  Primary sources support the stated techniques and implementation context, not
  every proposed variant.
---
# Cards, dice and tabletop mechanics

Tabletop mechanisms allocate limited actions and hidden information through cards, dice, positions and commitments. Each overview separates player actions, state changes and alternative rules. Examples are hypothetical design scenarios, not claims about a named game. A prototype check states an observable question for the next iteration. Existing detailed references remain separately linked from the direction map.

## Mechanics and variants

<a id="mechanics"></a>

### 1. Pre-game deck construction

<a id="t175"></a>
id: t175
canonicalId: tabletop-systems--t175
url: https://gamemechanics.pro/en/mechanics/tabletop-systems/#t175

Decks are built before play under format constraints, setting tool ratios and the likelihood of useful combinations.

#### Mechanic variants

<a id="t175-variants"></a>
- Copy limits restrict repeated powerful cards. <a id="t175-v1"></a>
- Cost curves determine early-turn tempo. <a id="t175-v2"></a>
- Sideboards change composition between games. <a id="t175-v3"></a>
- Leader rules restrict eligible card choices. <a id="t175-v4"></a>

Design example: A fast deck adds cheap responses at the expense of powerful finishing cards.

Prototype check: Test opening hands and the share of games lacking a meaningful first action with a legal starting deck.

- [PuzzleScript: Rules](https://www.puzzlescript.net/Documentation/rules.html)
- [Wizards of the Coast: Magic rules](https://magic.wizards.com/en/rules)

### 2. Trick-taking, shedding and set collection

<a id="t178"></a>
id: t178
canonicalId: tabletop-systems--t178
url: https://gamemechanics.pro/en/mechanics/tabletop-systems/#t178

Tricks, shedding and set rules change a card's value according to turn order and previously revealed cards.

#### Mechanic variants

<a id="t178-variants"></a>
- Following suit requires a compatible response. <a id="t178-v1"></a>
- Trumps change the normal strength order. <a id="t178-v2"></a>
- Discarding frees a hand but removes an option. <a id="t178-v3"></a>
- Sets value combinations over individual strength. <a id="t178-v4"></a>

Design example: A player keeps a weak card of one suit to avoid spending a trump later.

Prototype check: Test legal responses when a suit is absent and consistent rank interpretation in the interface and scoring.

- [PuzzleScript: Rules](https://www.puzzlescript.net/Documentation/rules.html)
- [Wizards of the Coast: Magic rules](https://magic.wizards.com/en/rules)

### 3. Worker placement and action selection

<a id="t179"></a>
id: t179
canonicalId: tabletop-systems--t179
url: https://gamemechanics.pro/en/mechanics/tabletop-systems/#t179

Workers reserve actions in a shared offer, so placement both grants a benefit and denies an opponent an opportunity.

#### Mechanic variants

<a id="t179-variants"></a>
- Exclusive spaces accept one worker. <a id="t179-v1"></a>
- Extra payment permits repeating an occupied action. <a id="t179-v2"></a>
- Specialists improve a particular space type. <a id="t179-v3"></a>
- Worker retrieval opens another action round. <a id="t179-v4"></a>

Design example: Occupying a sawmill now supplies timber and prevents a rival from finishing construction on time.

Prototype check: Test useful fallback actions after a first choice is blocked, especially for the last participant.

- [PuzzleScript: Rules](https://www.puzzlescript.net/Documentation/rules.html)
- [Wizards of the Coast: Magic rules](https://magic.wizards.com/en/rules)

### 4. Area control, majorities and enclosure

<a id="t180"></a>
id: t180
canonicalId: tabletop-systems--t180
url: https://gamemechanics.pro/en/mechanics/tabletop-systems/#t180

Influence is compared by presence, connectivity or enclosure, linking placement to the timing of a future scoring check.

#### Mechanic variants

<a id="t180-variants"></a>
- Majorities earn rewards when scoring occurs. <a id="t180-v1"></a>
- Enclosure changes an isolated region's owner. <a id="t180-v2"></a>
- Connectivity supports an adjacent territory. <a id="t180-v3"></a>
- Ties preserve disputes or split a reward. <a id="t180-v4"></a>

Design example: One token connects two weak areas and creates a majority before the round ends.

Prototype check: Test ties and broken connections immediately before scoring so the evaluation moment is visible.

- [PuzzleScript: Rules](https://www.puzzlescript.net/Documentation/rules.html)
- [Wizards of the Coast: Magic rules](https://magic.wizards.com/en/rules)

### 5. Tile placement and shared boards

<a id="t181"></a>
id: t181
canonicalId: tabletop-systems--t181
url: https://gamemechanics.pro/en/mechanics/tabletop-systems/#t181

Placing a tile changes a shared board and its legal continuations, requiring attention to edges and neighboring pieces.

#### Mechanic variants

<a id="t181-variants"></a>
- Matching edges constrain adjacency. <a id="t181-v1"></a>
- Closing a region triggers scoring. <a id="t181-v2"></a>
- Shared tiles can benefit several participants. <a id="t181-v3"></a>
- Rotation chooses between alternative network continuations. <a id="t181-v4"></a>

Design example: A road tile completes a rival's short route while opening the player's longer chain.

Prototype check: Test every rotation and preview all regions completed by a single placed tile.

- [PuzzleScript: Rules](https://www.puzzlescript.net/Documentation/rules.html)
- [Wizards of the Coast: Magic rules](https://magic.wizards.com/en/rules)

### 6. Dice, rerolls and result assignment

<a id="t182"></a>
id: t182
canonicalId: tabletop-systems--t182
url: https://gamemechanics.pro/en/mechanics/tabletop-systems/#t182

A roll supplies limited values; rerolling and assignment turn a random outcome into a manageable resource.

#### Mechanic variants

<a id="t182-variants"></a>
- Keeping dice locks in useful results. <a id="t182-v1"></a>
- Rerolls consume a limited attempt budget. <a id="t182-v2"></a>
- Assignment distributes values between actions. <a id="t182-v3"></a>
- Modifiers alter results for an explicit cost. <a id="t182-v4"></a>

Design example: A six can power an attack or long movement but cannot serve both actions at once.

Prototype check: Test locking and rerolling during simultaneous confirmations so each die is consumed only once.

- [PuzzleScript: Rules](https://www.puzzlescript.net/Documentation/rules.html)
- [Wizards of the Coast: Magic rules](https://magic.wizards.com/en/rules)

### 7. Wagers, bluffing and pushing your luck

<a id="t183"></a>
id: t183
canonicalId: tabletop-systems--t183
url: https://gamemechanics.pro/en/mechanics/tabletop-systems/#t183

The player chooses whether to continue an uncertain attempt, increasing rewards and the risk of losing unbanked gains.

#### Mechanic variants

<a id="t183-variants"></a>
- Stopping banks the accumulated reward. <a id="t183-v1"></a>
- Bluffing changes others' estimate of hidden state. <a id="t183-v2"></a>
- Stakes limit the maximum possible loss. <a id="t183-v3"></a>
- Visible probabilities make risks comparable. <a id="t183-v4"></a>

Design example: An expedition can bank three discoveries or open another room while risking the whole cargo.

Prototype check: Test loss comprehension before continuing and ensure stated probabilities do not change invisibly.

- [PuzzleScript: Rules](https://www.puzzlescript.net/Documentation/rules.html)
- [Wizards of the Coast: Magic rules](https://magic.wizards.com/en/rules)

### 8. Hidden orders and simultaneous selection

<a id="t184"></a>
id: t184
canonicalId: tabletop-systems--t184
url: https://gamemechanics.pro/en/mechanics/tabletop-systems/#t184

Simultaneous hidden choices emphasize predicting intentions rather than reacting to an order already executed.

#### Mechanic variants

<a id="t184-variants"></a>
- Sealed orders lock before their reveal. <a id="t184-v1"></a>
- Priority resolves conflicting identical targets. <a id="t184-v2"></a>
- Scouting exposes part of another plan. <a id="t184-v3"></a>
- Decoy orders spend an action on misleading signals. <a id="t184-v4"></a>

Design example: Both players secretly choose a bridge or bypass and one can scout at the cost of speed.

Prototype check: Test that a confirmed plan cannot change after information from another participant's reveal is received.

- [PuzzleScript: Rules](https://www.puzzlescript.net/Documentation/rules.html)
- [Wizards of the Coast: Magic rules](https://magic.wizards.com/en/rules)

### 9. Dexterity and digital tabletop toys

<a id="t185"></a>
id: t185
canonicalId: tabletop-systems--t185
url: https://gamemechanics.pro/en/mechanics/tabletop-systems/#t185

Physical precision determines game-piece placement while a digital model translates the result into game state.

#### Mechanic variants

<a id="t185-variants"></a>
- Flicks set a piece's impulse and direction. <a id="t185-v1"></a>
- Balance limits a tower's safe height. <a id="t185-v2"></a>
- Rebounds bypass a direct obstruction. <a id="t185-v3"></a>
- Landing zones distinguish execution quality. <a id="t185-v4"></a>

Design example: A player rebounds a piece off a rail to bypass a blocker and stop within a target zone.

Prototype check: Test identical input at different frame rates and clear visibility of the initial force application point.

- [PuzzleScript: Rules](https://www.puzzlescript.net/Documentation/rules.html)
- [Wizards of the Coast: Magic rules](https://magic.wizards.com/en/rules)

### 10. Drafting and shared offers

<a id="t177"></a>
id: t177
canonicalId: tabletop-systems--t177
url: https://gamemechanics.pro/en/mechanics/tabletop-systems/#t177

Drafting distributes elements through sequential selection: taking an item improves one participant and removes an option from others.

#### Mechanic variants

<a id="t177-variants"></a>
- Passing packs change offers after each selection. <a id="t177-v1"></a>
- Open rows display a shared public offer. <a id="t177-v2"></a>
- Snake order compensates for first-pick advantage. <a id="t177-v3"></a>
- Bans remove a dangerous option instead of gaining one. <a id="t177-v4"></a>

Design example: A player takes a fitting card and leaves a rival to choose between incompatible strategies.

Prototype check: Test full offer circulation, simultaneous-pick conflicts and useful options for the final participant.

- [PuzzleScript: Rules](https://www.puzzlescript.net/Documentation/rules.html)
- [Wizards of the Coast: Magic rules](https://magic.wizards.com/en/rules)

## Sources and examples

Sources support particular techniques or methodology, not every family variant. Design examples and mechanic combinations are illustrative.

- [PuzzleScript: Rules](https://www.puzzlescript.net/Documentation/rules.html): The creator’s documentation of pattern replacement and board state.
- [Wizards of the Coast: Magic rules](https://magic.wizards.com/en/rules): Primary example of formal card-game rules, with separate basic and comprehensive references; not a description of all mechanisms below.