Game Setup

Setup

Playing The Game VoidSiege is a competitive tabletop game designed for two or more players. Players require an army, the corresponding operational data for their units, and a table or surface to represent the…

Last updated 9 August 2026

Playing The Game

VoidSiege is a competitive tabletop game designed for two or more players.

Players require an army, the corresponding operational data for their units, and a table or surface to represent the battlefield.

Chosen Army

Players select an army for which they have miniatures available.

Only miniatures from the chosen army may be used during the game, and they must correspond to the operational data sheets.

Source army list:

  • The Confederation
  • The Asylumists
  • The Dark Blade
  • The Order
  • The Host
  • The Biosite Expanse

The source army list above is setup source text pending faction and lore review. It should not be treated as final public faction canon until Jason approves that status.

Threat Points

Threat Points are setup and scenario deployment points.

Threat Points are distinct from Command Points.

  • Threat Points determine game size and may be spent by scenarios to deploy or reinforce units.
  • Command Points are the turn resource spent to issue commands.
  • Spending or discarding Threat Points does not issue a command unless a scenario explicitly says otherwise.
  • Spending or discarding Command Points does not buy or deploy units unless a scenario explicitly says otherwise.

Table Setup

VoidSiege is best played on a table at least 4' by 4'.

While a bare surface can be used, incorporating terrain and scenery enhances gameplay.

Players can agree on terrain placement or alternate placing terrain pieces.

Terrain provides Cover as defined in core/cover.md.

Example: If two players cannot agree on terrain placement, they alternate placing pieces until the table is set, ensuring a balanced battlefield.

Battle Scenarios

Scenarios determine the victory conditions, deployment options, and special rules of a game.

Players can select from predefined scenarios or create custom ones by deciding on deployment, setup, and victory conditions.

Example: A predefined scenario might require players to capture objectives, while a custom scenario could focus on destroying enemy units within a set number of turns.

Game Size

Game size determines the number of units players can deploy, based on Threat Points.

Recommended game sizes:

  • 5 Threat Points: Short game, about 2 hours.
  • 10 Threat Points: Medium-length game, about 2 to 4 hours.
  • 20 Threat Points: Long game, about 4 or more hours.

Preparing To Play

Players agree on the game size and scenario.

Roll off to determine which player chooses their table edge and deploys first.

Deployment alternates between players unless the scenario states otherwise.

Front-Line Assault Scaling

Front-Line Assault Scaling is a shared setup/scenario module for allocating Threat Points over the opening turns of a scenario.

If a scenario uses Front-Line Assault Scaling, use the table matching the agreed game size unless that scenario states otherwise.

Small Game

  • Turn 1: 1 Threat Point
  • Turn 2: 1 Threat Point
  • Turn 3: 2 Threat Points
  • Turn 4: 3 Threat Points

Medium Game

  • Turn 1: 2 Threat Points
  • Turn 2: 3 Threat Points
  • Turn 3: 4 Threat Points
  • Turn 4: 5 Threat Points

Large Game

  • Turn 1: 3 Threat Points
  • Turn 2: 4 Threat Points
  • Turn 3: 5 Threat Points
  • Turn 4: 6 Threat Points

Unused Threat Points do not carry over between turns.

Front-Line Assault Scaling allocates Threat Points for Turns 1 through 4. No Threat Points are allocated by this module after Turn 4 unless a scenario explicitly says otherwise.

Notes

  • This file does not define how Command Points are generated or spent; use core/commands/command_points.md.
  • Scenario-specific deployment and scoring rules belong in scenario files unless Jason approves a shared scenario module.
  • Shared scenario modules are defined in ../scenarios/scenario_modules.md.
Rule topics