5c335b4b3c
Introduce the HubScreen as the main interface for managing resources, units, and mission selection, integrating with the GameStateManager for dynamic data binding. Implement the MissionBoard component to display and select available missions, enhancing user interaction with mission details and selection logic. Update the GameStateManager to handle transitions between game states, ensuring a seamless experience for players. Add tests for HubScreen and MissionBoard to validate functionality and integration with the overall game architecture.
23 lines
790 B
Markdown
23 lines
790 B
Markdown
---
|
|
description: Standards for JSON data structures (Classes, Items, Missions).
|
|
globs: assets/data/\*\*/\*.json**
|
|
---
|
|
|
|
# **Data Schema Standards**
|
|
|
|
## **Itemization**
|
|
|
|
- **IDs:** ALL CAPS SNAKE_CASE (e.g., ITEM_RUSTY_BLADE).
|
|
- **Files:** One file per item/class OR grouped by category. Consistent keys are mandatory.
|
|
- **Effects:** Use passive_effects array for event listeners and active_ability for granted skills.
|
|
|
|
## **Missions**
|
|
|
|
- **Structure:** Must match the Mission TypeScript interface.
|
|
- **Narrative:** Link to narrative/ JSON files via ID. Do not embed full dialogue in Mission JSON.
|
|
- **Rewards:** Must specify guaranteed vs conditional.
|
|
|
|
## **Classes**
|
|
|
|
- **Skill Trees:** Use the standard 30-node topology template.
|
|
- **Growth:** Define base_stats (Lvl 1\) and growth_rates.
|