Skip to content

Declared Speed and Load-Threshold Movement

Overview

Declared speed and load-threshold movement treats movement as a meaningful decision instead of a passive number on the sheet. Load determines what speeds are available. The chosen speed then determines what the party can safely do, notice, map, or risk.

This makes movement a logistics declaration with immediate gameplay consequences.

Core Pattern

The procedure has two linked questions:

  1. how burdened is the party
  2. how fast are they choosing to move right now

The first limits capacity. The second declares risk appetite.

Standard Procedure

  1. Determine the party's movement ceiling from the slowest or most burdened member.
  2. Choose a speed band for the current turn or round.
  3. Apply the benefits and penalties of that speed.
  4. Resolve navigation, traps, mapping, encounters, and consumables with that declaration in mind.
  5. Reassess after treasure pickup, injury, pursuit, or terrain change.

Why It Works at the Table

  • Encumbrance matters without becoming pure accounting.
  • Speed becomes a tactical declaration, not just geometry.
  • Players can choose risk rather than being surprised by invisible assumptions.
  • Heavy treasure and urgent retreats naturally alter exploration tempo.

Speed Band Logic

Typical movement bands answer different needs:

  • careful pace: better awareness, fuller mapping, more actions retained
  • fast pace: more distance, less detail, higher hazard exposure
  • sprint pace: maximum distance, minimal control, highest procedural risk

The exact numbers can vary by system. The structure is what matters.

Load Threshold Rule

Encumbrance should change movement in clear steps rather than tiny decimal adjustments.

  • light load: broadest choice of speed bands
  • medium load: moderate speed ceiling and less spare action economy
  • heavy load: safe movement narrows and retreat becomes dangerous
  • extreme load: mobility collapses into emergency crawling or forced dropping of gear

Thresholds preserve legibility under pressure.

Referee Procedure

  1. Ask for pace explicitly when tension matters.
  2. Tie speed to what the party can perceive, map, and carry.
  3. Make hidden hazards more dangerous at faster declared speeds.
  4. Let overloaded parties feel the consequences immediately.
  5. Use the same logic for pursuit, escape, and treasure extraction.

Design Guidance

  • Do not ask for speed declarations when nothing meaningful changes.
  • Heavy loads should create interesting choices, not just punishment.
  • Mapping quality is a useful tradeoff lever.
  • The slowest-member rule is strong because it forces parties to negotiate risk collectively.

Practical Comparison Rule

Use declared-speed and load-threshold movement when exploration pace, escape pressure, and treasure logistics are meant to matter. Use flat movement rates when the campaign does not care about resource strain or hazard timing.

See Also