Skip to content

Evaluate Create Workshop Setting values to their defaults #54

Description

@e54-bot

Problem

After athena#50 (PR #52), Bastion (/Users/teakowa/Repos/wrightkit/.task-scratch/bastion/bastion.ow, scenario .../bastion/scen.json) stops with not_modeled: "value createWorkshopSettingFloat" at tick 0. Bastion reads its mode settings through the Create Workshop Setting ... values (float, integer, bool, enum/combo, hero, string — check which Bastion uses).

Scope

  • Evaluate the Create Workshop Setting value family to the setting's declared default, since the simulator runs one lobby with no player-edited settings. Honor the min/max semantics the workshop-rs catalog documents only as far as needed for the default; the value returned is the default argument.
  • Provide a way for the scenario to override a setting by (category, name) only if the scenario format already has a place for it; otherwise leave overrides out and say so (no new scenario fields in this issue).
  • A value with no passing capture fixture is recorded in docs/findings.md as modeled-not-measured, per AGENTS.md.

Acceptance criteria

  • Tests: each Create Workshop Setting kind Bastion uses evaluates to its default; reading it inside a rule condition and an action argument works.
  • The Bastion run moves past this stop; record the next stop in the PR body.
  • docs/simulator-interface.md updated; fmt, clippy -D warnings, tests, wasm32 build pass.

Activity

  1. added
    enhancementNew feature or request
    ready-for-implementationContract settled; an Engineer can implement without inventing a decision
    p1Critical path of the current roadmap line, or a bug that hits real workflows
    on Oct 25, 2026
  2. added theissue type on Oct 25, 2026
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 requestp1Critical path of the current roadmap line, or a bug that hits real workflowsready-for-implementationContract settled; an Engineer can implement without inventing a decision

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions