Skip to content

Integrate the typed scenario registry into new campaign setup #4

Description

@aribradshaw

Player outcome

Let players choose a registered scenario from the new-campaign setup and ensure the selected scenario controls the initial campaign session.

Implementation direction

Follow docs/architecture.md: resolve and validate a ScenarioSession, pass it into engine initialization, apply resources and sparse state overrides before Week 1, and preserve the scenario id and seed in saves.

Acceptance criteria

  • The setup screen lists registered scenarios without hard-coded duplicate metadata.
  • Invalid scenarios cannot start.
  • Save and resume preserve scenario id and deterministic seed.
  • Historical 1976 remains the default.
  • Unit and browser tests cover selection, initialization, and resume.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is neededscenarioHistorical or alternate campaign content

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions