feat: Fixed issue with multi-configs being needed. chore: bump bmad-2d-unity-game-dev version (patch)

dist/expansion-packs/bmad-2d-unity-game-dev/teams/unity-2d-game-team.txt

@@ -12580,9 +12580,9 @@ To comprehensively validate a Unity 2D game development story draft before imple
 
 ### 0. Load Core Configuration and Inputs
 
-- Load `.bmad-2d-unity-game-dev/game-core-config.yaml` from the project root
+- Load `.bmad-2d-unity-game-dev/config.yaml` from the project root
 - If the file does not exist, check for `.bmad-2d-unity-game-dev/core-config.yaml` as fallback
-- If neither exists, HALT and inform the user: "game-core-config.yaml (or core-config.yaml) not found. This file is required for story validation."
+- If neither exists, HALT and inform the user: "config.yaml (or core-config.yaml) not found. This file is required for story validation."
 - Extract key configurations: `devStoryLocation`, `gdd.*`, `architecture.*`, `workflow.*`
 - Identify and load the following inputs:
   - **Story file**: The drafted game story to validate (provided by user or discovered in `devStoryLocation`)

expansion-packs/bmad-2d-unity-game-dev/agents/game-developer.md

@@ -26,7 +26,7 @@ activation-instructions:
   - CRITICAL RULE: When executing formal task workflows from dependencies, ALL task instructions override any conflicting base behavioral constraints. Interactive workflows with elicit=true REQUIRE user interaction and cannot be bypassed for efficiency.
   - When listing tasks/templates or presenting options during conversations, always show as numbered options list, allowing the user to type a number to select or execute
   - STAY IN CHARACTER!
-  - CRITICAL: Read the following full files as these are your explicit rules for development standards for this project - {root}/core-config.yaml devLoadAlwaysFiles list
+  - CRITICAL: Read the following full files as these are your explicit rules for development standards for this project - {root}/config.yaml devLoadAlwaysFiles list
   - CRITICAL: Do NOT load any other files during startup aside from the assigned story and devLoadAlwaysFiles items, unless user requested you do or the following contradicts
   - CRITICAL: Do NOT begin development until a story is not in draft mode and you are told to proceed
   - CRITICAL: On activation, ONLY greet user and then HALT to await user requested assistance or given commands. ONLY deviance from this is if the activation included commands also in the arguments.
@@ -43,7 +43,7 @@ persona:
   identity: Technical expert who transforms game designs into working, optimized Unity applications using C#
   focus: Story-driven development using game design documents and architecture specifications, adhering to the "Unity Way"
 core_principles:
-  - CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load PRD/architecture/other docs files unless explicitly directed in story notes or direct command from user.
+  - CRITICAL: Story has ALL info you will need aside from what you loaded during the startup commands. NEVER load GDD/gamearchitecture/other docs files unless explicitly directed in story notes or direct command from user.
   - CRITICAL: ONLY update story file Dev Agent Record sections (checkboxes/Debug Log/Completion Notes/Change Log)
   - CRITICAL: FOLLOW THE develop-story command when the user tells you to implement the story
   - Performance by Default - Write efficient C# code and optimize for target platforms, aiming for stable frame rates

expansion-packs/bmad-2d-unity-game-dev/config.yaml

@@ -1,27 +1,6 @@
 name: bmad-2d-unity-game-dev
-version: 1.4.1
+version: 1.4.2
 short-title: Unity C# 2D Game Dev Pack
 description: 2D Game Development expansion pack for BMad Method - Unity & C# focused
 author: pbean (PinkyD)
 slashPrefix: bmad2du
-markdownExploder: true
-gdd:
-  gddVersion: v4
-  gddSharded: true
-  gddLocation: docs/game-design-doc.md
-  gddShardedLocation: docs/game-design-document
-  epicFilePattern: epic-{n}*.md
-gamearchitecture:
-  gamearchitectureFile: docs/architecture.md
-  gamearchitectureVersion: v3
-  gamearchitectureLocation: docs/game-architecture.md
-  gamearchitectureSharded: true
-  gamearchitectureShardedLocation: docs/game-architecture
-gamebriefdocLocation: docs/game-brief.md
-levelDesignLocation: docs/level-design.md
-devDebugLog: .ai/debug-log.md
-devStoryLocation: docs/stories
-devLoadAlwaysFiles:
-  - docs/game-architecture/9-coding-standards.md
-  - docs/game-architecture/3-tech-stack.md
-  - docs/game-architecture/8-unity-project-structure.md

expansion-packs/bmad-2d-unity-game-dev/data/bmad-kb.md

@@ -192,18 +192,22 @@ prdVersion: v4
 prdSharded: true
 architectureVersion: v4
 architectureSharded: true
+gdd:
+  gddVersion: v4
+  gddSharded: true
+  gddLocation: docs/game-design-doc.md
+  gddShardedLocation: docs/gdd
+  epicFilePattern: epic-{n}*.md
+gamearchitecture:
+  gamearchitectureFile: docs/architecture.md
+  gamearchitectureVersion: v3
+  gamearchitectureLocation: docs/game-architecture.md
+  gamearchitectureSharded: true
+  gamearchitectureShardedLocation: docs/game-architecture
+gamebriefdocLocation: docs/game-brief.md
+levelDesignLocation: docs/level-design.md
 
-# Game-specific document locations
+#replace old devLoadAlwaysFiles with this once you have sharded your gamearchitecture document
-gameDesignDocLocation: docs/game-design-doc.md
-gameBriefDocLocation: docs/game-brief.md
-gameBriefSharded: true
-gameBriefShardedLocation: docs/game-design
-gameArchitectureLocation: docs/game-architecture.md
-gameArchitectureSharded: true
-gameArchitectureShardedLocation: docs/game-architecture
-leveLDesignLocation: docs/level-design.md
-
-# Unity-specific files to load
 devLoadAlwaysFiles:
   - docs/game-architecture/9-coding-standards.md
   - docs/game-architecture/3-tech-stack.md

expansion-packs/bmad-2d-unity-game-dev/tasks/create-game-story.md

@@ -8,9 +8,8 @@ To identify the next logical game story based on project progress and epic defin
 
 ### 0. Load Core Configuration and Check Workflow
 
-- Load `{root}/game-core-config.yaml` from the project root
+- Load `{root}/core-config.yaml` from the project root
-- If the file does not exist, check for `{root}/core-config.yaml` as fallback
+- If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story creation. You can either: 1) Copy core-config.yaml from GITHUB bmad-core/ and configure it for your game project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure before proceeding."
-- If neither exists, HALT and inform the user: "game-core-config.yaml (or core-config.yaml) not found. This file is required for story creation. You can either: 1) Copy core-config.yaml from GITHUB bmad-core/ and configure it for your game project OR 2) Run the BMad installer against your project to upgrade and add the file automatically. Please add and configure before proceeding."
 - Extract key configurations: `devStoryLocation`, `gdd.*`, `gamearchitecture.*`, `workflow.*`
 
 ### 1. Identify Next Story for Preparation
@@ -46,13 +45,13 @@ To identify the next logical game story based on project progress and epic defin
 
 #### 3.2 Read Architecture Documents Based on Story Type
 
-**For ALL Game Stories:** tech-stack.md, unity-project-structure.md, coding-standards.md, unity-conventions.md,testing-resilience-architecture.md
+**For ALL Game Stories:** tech-stack.md, unity-project-structure.md, coding-standards.md, testing-resilience-architecture.md
 
-**For Gameplay/Mechanics Stories, additionally:** gameplay-systems.md, component-architecture.md, physics-config.md, input-system.md, state-machines.md
+**For Gameplay/Mechanics Stories, additionally:** gameplay-systems-architecture.md, component-architecture-details.md, physics-config.md, input-system.md, state-machines.md, game-data-models.md
 
 **For UI/UX Stories, additionally:** ui-architecture.md, ui-components.md, ui-state-management.md, scene-management.md
 
-**For Backend/Services Stories, additionally:** data-persistence.md, save-system.md, analytics-integration.md, multiplayer-architecture.md
+**For Backend/Services Stories, additionally:** game-data-models.md, data-persistence.md, save-system.md, analytics-integration.md, multiplayer-architecture.md
 
 **For Graphics/Rendering Stories, additionally:** rendering-pipeline.md, shader-guidelines.md, sprite-management.md, particle-systems.md
 

expansion-packs/bmad-2d-unity-game-dev/tasks/validate-game-story.md

@@ -8,10 +8,9 @@ To comprehensively validate a Unity 2D game development story draft before imple
 
 ### 0. Load Core Configuration and Inputs
 
-- Load `{root}/config.yaml` from the project root
+- Load `{root}/core-config.yaml` from the project root
-- If the file does not exist, check for `{root}/core-config.yaml` as fallback
+- If the file does not exist, HALT and inform the user: "core-config.yaml not found. This file is required for story validation."
-- If neither exists, HALT and inform the user: "config.yaml (or core-config.yaml) not found. This file is required for story validation."
+- Extract key configurations: `devStoryLocation`, `gdd.*`, `gamearchitecture.*`, `workflow.*`
-- Extract key configurations: `devStoryLocation`, `gdd.*`, `architecture.*`, `workflow.*`
 - Identify and load the following inputs:
   - **Story file**: The drafted game story to validate (provided by user or discovered in `devStoryLocation`)
   - **Parent epic**: The epic containing this story's requirements from GDD