Skip to content

Main Street: GDD -- Content Design and Progression #404

@SorraTheOrc

Description

@SorraTheOrc

Summary

Write the content and progression section of Main Street's Game Design Document covering the card pool, recipes/blueprints, difficulty curves, scoring, and any meta-progression or unlockable content.

User Story

As a game designer, I want Main Street's full content scope and progression systems documented so that we know exactly what needs to be created and how the player experience evolves over time.

Prerequisites

  • Main Street: GDD Core Rules and Mechanics (CG-0MM4RC1K81JU4U5D) completed

Sections to Cover

  1. Card Pool / Content Inventory -- Complete list of all cards/items in Main Street, organized by type/category, with all attributes specified. Include quantities (how many of each card in the deck/pool).
  2. Recipes / Blueprints / Combinations (if applicable) -- What can be crafted/built from what? Full recipe list with inputs, outputs, and any conditions.
  3. Resource Economy -- Flow of resources through the game. Sources, sinks, conversion rates. Economy balance targets.
  4. Difficulty and Balance -- How is difficulty managed? Difficulty settings, handicaps, or progressive challenge. Target win rates.
  5. Scoring System -- How is score calculated? What are the scoring components? What constitutes a 'good' score?
  6. Progression / Unlockables (if applicable) -- Does anything carry over between sessions? Unlockable cards, modes, challenges?
  7. Replayability Hooks -- What drives the player to play Main Street again? Randomized elements, challenges, personal best chasing, content discovery.

Expected Output

A formal GDD section covering all of Main Street's content and progression design with enough detail to scope the full implementation.

Acceptance Criteria

  1. Complete card/content inventory is specified with quantities and attributes
  2. All recipes/combinations are documented (if applicable)
  3. Resource economy is modelled with sources, sinks, and target flow rates
  4. Scoring system is fully specified
  5. Replayability hooks are identified and designed
  6. The document is reviewed and approved by the producer

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions