ginnoir/idlegame
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

Define rules for resource-gated story choices #17

New Issue
Open
opened 2026-06-11 22:47:04 -05:00 by ginnoir · 0 comments
ginnoir commented 2026-06-11 22:47:04 -05:00
Owner
Copy Link
Copy Source

Define cost vs requirement semantics + UI for resource-gated story choices (no M1 content yet).

Context

During the PR3 T3.0 view-model review (story column projection), a design question surfaced: how should a story choice that requires/consumes resources behave?

Today isStoryChoiceAvailable only checks node membership + choice requirements; Story-kind actions in the Play column hide when their choice isn't available. There is no defined semantics for a choice that should be gated by (or spend) resources, and no M1 content currently uses one — so it is unspecified rather than broken.

Decide

  • Do resource-gated choices cost resources (deducted on pick) or merely require a threshold (visible-but-disabled until met)?
  • How is the gate authored in storySchema (choice requirements / outcomes)?
  • UI affordance in the Story column: hidden vs shown-disabled-with-reason (current story actions pass disabledReason: null).

Notes

  • Related code: src/engine/story.ts (isStoryChoiceAvailable, choice requirements), src/state/viewModel.ts (story-kind availability projection), src/content/storySchema.ts.
  • Low priority: capture the rule before content authoring leans on it. Design intent should also land in the Obsidian vault (Idlegame/Decisions.md).
<brief>Define cost vs requirement semantics + UI for resource-gated story choices (no M1 content yet).</brief> ## Context During the PR3 T3.0 view-model review (story column projection), a design question surfaced: how should a story **choice** that requires/consumes resources behave? Today `isStoryChoiceAvailable` only checks node membership + choice requirements; Story-kind actions in the Play column hide when their choice isn't available. There is no defined semantics for a choice that should be gated by (or spend) resources, and no M1 content currently uses one — so it is unspecified rather than broken. ## Decide - Do resource-gated choices **cost** resources (deducted on pick) or merely **require** a threshold (visible-but-disabled until met)? - How is the gate authored in `storySchema` (choice `requirements` / outcomes)? - UI affordance in the Story column: hidden vs shown-disabled-with-reason (current story actions pass `disabledReason: null`). ## Notes - Related code: `src/engine/story.ts` (`isStoryChoiceAvailable`, choice requirements), `src/state/viewModel.ts` (story-kind availability projection), `src/content/storySchema.ts`. - Low priority: capture the rule before content authoring leans on it. Design intent should also land in the Obsidian vault (`Idlegame/Decisions.md`).
ginnoir added the prio/3type/contentarea/story labels 2026-06-11 22:47:04 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/engine
Pure game engine
 area/story
Story and narrative structure
 area/ui
React UI and visual behavior
 area/workflow
Tooling, CI, deploy, project workflow
 prio/1
Highest priority
 prio/2
Medium priority
 prio/3
Lower priority
 type/content
Story, balance, or content definitions
 type/feat
Feature work
 type/fix
Bug fix
 type/infra
Infrastructure or workflow
No labels area/story prio/3 type/content
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
ginnoir (Ginnoir)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ginnoir/idlegame#17