TIME SYSTEMS

Characters and the world change as calendar time advances — people age, skills decay or mature, generations succeed each other, and long-term consequences accumulate beyond any single session's actions.

Turn structure where sides alternate activating one unit (or small group) at a time — I move a unit, you move a unit — instead of one side moving its entire force before the other responds.

In-game time advances continuously, cycling lighting, NPC schedules, spawns, and available activities between day and night.

Turn order is determined by a speed or initiative stat rather than fixed player-then-enemy alternation, so faster characters act more often and slower ones less, and turn order itself becomes a strategic target.

A distinct phase where players plan against previewed information — seeing enemy intentions before committing moves, programming actions that execute simultaneously, planning turns that resolve later.

Combat resolving continuously in live time — attacks, dodges, and decisions executed as they happen, with reflexes, spacing, and timing as first-class skills alongside build and strategy.

Combat runs in real time but the player can pause at any moment to assess, queue orders, and issue commands, then unpause to watch them execute.

Time-slot programming of recurring behavior — colonist daily schedules assigning sleep, work, and recreation by hour; NPC routines that put the blacksmith at the forge by day and the tavern by night; player-authored timetables for shifts, patrols, and services.

In-game time cycles through seasons that change the environment, available activities, resources, and challenges.

All players' orders executing at once — plan phases where both sides commit blind, then resolution where the plans collide — rather than alternating turns.

The player can slow the flow of time — often during combat — while retaining near-normal reaction speed, creating a window to aim, dodge, or plan amid slowed action.

Player control over simulation speed — pause, normal, double, quadruple — decoupling the game's clock from the player's attention.

Time quantized into discrete simulation beats — server ticks resolving all actions at fixed intervals, energy systems granting turns by speed, games where 'real-time' is secretly a fast turn sequence.

Hard clocks on tasks — the mission that fails at zero, the bomb's countdown, turn limits on objectives, escort windows and evacuation deadlines.

The day-night cycle as a rules layer — shops closing at dusk, enemies strengthening after dark, NPC schedules rotating with the sun, stealth odds and spawn tables keyed to the clock.

The player can reverse time to undo recent actions — a death, a mistake, a missed jump — treating time itself as a manipulable resource or a puzzle element.

Combatants act in discrete turns rather than simultaneously in real time.

Weather as a changing system over time — fronts rolling through on schedules or simulations, seasonal tendencies, forecast-able patterns that gameplay can plan against, the sky as a slow machine rather than a random skybox.