Commands Overview

Core Rule

Commands are formal action structures used to resolve unit activity.

A unit performs actions by being issued a legal command.

Commands do not create separate action systems. They call existing core engines such as movement, shooting, close combat, and damage, unless a rule explicitly states otherwise.

General Rules

• A unit may only be issued a command it is eligible to perform.
• A command must define its own Declaration Trigger.
• A command must define its own Resolution Timing.
• A command may call one or more core rules engines.
• A command does not redefine a core rules engine unless it explicitly states an override.
• A command may be declared during a unit’s normal activation or at another permitted timing if a rule allows it.
• A command token identifies the declared command, but does not by itself apply restrictions unless the command says it does.

Command Declaration

When a command is declared:

1. Confirm that its Declaration Trigger is valid.
2. Confirm that the unit is eligible to perform it.
3. Assign any command token required by that command.
4. Resolve the command according to its Resolution Timing.
5. Apply any command-specific restrictions or resulting state changes required by that command.

Command File Responsibilities

Each individual command file should define only:

• its Declaration Trigger
• its Resolution Timing
• its permitted targets, if any
• which core engines it calls
• any command-specific restrictions
• any explicit overrides or exceptions

An individual command file should not restate the full rules for movement, shooting, close combat, damage, or timing unless it creates a true exception.

Command Categories

Commands may include one or more of the following effects:

• Movement
• Shooting
• Melee or charge interaction
• Defensive positioning
• Recovery or removal of restrictions
• Special command-specific effects

Timing

• Use timing/command_timing.md for declaration timing and command resolution timing.
• Declaring a command does not by itself determine when its effects are resolved.
• A command declared from a trigger is still a normal command unless a rule explicitly states otherwise.

Restrictions

• Use core/commands/commands_restrictions.md for restriction rules.
• Restrictions are applied only where a command explicitly states that they apply.
• A command token is not itself a restriction unless a rule states that it is.

Engine Interaction

• Use core/movement.md for movement resolution.
• Use core/shooting.md and related shooting rules for ranged attack resolution.
• Use core/close_combat.md for close combat resolution.
• Use core/damage.md and related damage rules for damage outcomes.

Notes

• This file defines what commands are and how they relate to the rules engine.
• Individual command files should remain narrow and modular.
• Timing, restrictions, and engine resolution should stay in their own source files unless a command creates a specific exception.