ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity
BMAD-METHOD/expansion-packs/bmad-wechat-mini-game-dev/checklists/game-design-checklist.md

9.5 KiB
Raw Blame History

Game Design Document Quality Checklist (WeChat Mini Game)

Document Completeness

Executive Summary

  • Core Concept - Game concept is clearly explained in 2-3 sentences
  • Target Audience - Primary and secondary audiences defined with demographics
  • Platform Requirements - WeChat Mini Game export targets and requirements specified
  • Unique Selling Points - 3-5 key differentiators from competitors identified
  • Technical Foundation - WeChat Mini Game version and language strategy (JavaScript) confirmed

Game Design Foundation

  • Game Pillars - 3-5 core design pillars defined and actionable
  • Core Gameplay Loop - 30-60 second loop documented with specific timings
  • Win/Loss Conditions - Clear victory and failure states defined
  • Player Motivation - Clear understanding of why players will engage
  • Scope Realism - Game scope achievable with WeChat Mini Game's capabilities and resources

Gameplay Mechanics

Core Mechanics Documentation

  • Primary Mechanics - 3-5 core mechanics detailed with WeChat Mini Game implementation notes
  • Object Architecture - How mechanics map to the WeChat Mini Game's object system
  • Player Input - InputMap configuration for each platform specified
  • Event Flow - Game responses using the WeChat Mini Game's event system documented
  • Performance Impact - Frame time budget for each mechanic (target 60+ FPS)

Controls and Interaction

  • Multi-Platform Controls - Desktop, mobile, and gamepad InputMap defined
  • Input Responsiveness - Requirements for game feel using the WeChat Mini Game API
  • Accessibility Options - Control remapping and accessibility in Project Settings
  • Touch Optimization - Touch events and gesture handling designed
  • Input Buffer System - Frame-perfect input handling considerations

Progression and Balance

Player Progression

  • Progression Type - Linear, branching, or metroidvania approach defined
  • Save System Design - WeChat Mini Game storage-based save/load architecture
  • Unlock System - What players unlock and how it's stored in storage
  • Difficulty Scaling - How challenge increases using export variables
  • Player Agency - Meaningful choices affecting scene flow and game state

Game Balance

  • Balance Parameters - Export variables and JSON for tuning
  • Difficulty Curve - Appropriate challenge progression with scene variations
  • Economy Design - Resource systems using the WeChat Mini Game's storage
  • Live Tuning - Hot-reload support for balance iteration
  • Data-Driven Design - JSON for configuration

Level Design Framework

Scene Structure

  • Scene Types - Different scene categories with WeChat Mini Game scene inheritance
  • Scene Transitions - How players move between scenes (loading strategy)
  • Duration Targets - Expected play time considering scene complexity
  • Difficulty Distribution - Scene variants for different difficulty levels
  • Replay Value - Procedural elements using the WeChat Mini Game's randomization

Content Guidelines

  • Scene Creation Rules - Guidelines for WeChat Mini Game scene composition
  • Mechanic Introduction - Teaching through object activation and events
  • Pacing Variety - Mix using different process modes and time scales
  • Secret Content - Hidden areas using triggers
  • Accessibility Modes - Scene overrides for assist modes

Technical Implementation Readiness

Performance Requirements

  • Frame Rate Targets - 60+ FPS with WeChat Mini Game profiler validation
  • Draw Call Budgets - Maximum draw calls per scene type
  • Memory Budgets - Scene memory limits using the WeChat Mini Game's monitors
  • Mobile Optimization - Battery usage and thermal considerations
  • LOD Strategy - Level of detail using visibility ranges

Platform Specifications

  • Desktop Requirements - Minimum specs for Windows/Mac exports
  • Mobile Optimization - iOS/Android specific WeChat Mini Game settings
  • Web Compatibility - HTML5 export constraints and optimizations
  • Console Features - Platform-specific WeChat Mini Game export templates
  • Cross-Platform Save - Cloud save compatibility considerations

Asset Requirements

  • Art Style Definition - Visual style with WeChat Mini Game import settings
  • Texture Specifications - Import presets for different asset types
  • Audio Requirements - Bus layout and compression settings
  • UI/UX Guidelines - UI element theming and responsiveness
  • Localization Plan - Translation system using the WeChat Mini Game's localization

WeChat Mini Game-Specific Architecture

Object System Design

  • Object Hierarchy - Planned object tree structure for major systems
  • Scene Composition - Reusable scene patterns and inheritance
  • Global Systems - Singleton managers and their responsibilities
  • Event Architecture - Event flow between systems
  • Group Management - Object groups for gameplay systems

Language Strategy

  • JavaScript Usage - Systems appropriate for rapid iteration
  • Plugin Requirements - Required plugins or libraries
  • Tool Scripts - Editor tools for content creation

Resource Management

  • Custom Resources - Game-specific resource classes planned
  • Preload Strategy - Resources to preload vs lazy load
  • Instance Pooling - Objects requiring pooling (bullets, effects)
  • Memory Management - Reference counting and cleanup strategy
  • Asset Streaming - Large asset loading approach

Development Planning

Implementation Phases

  • Prototype Phase - Core loop in minimal WeChat Mini Game project
  • Vertical Slice - Single polished level with all systems
  • Production Phase - Full content creation pipeline
  • Polish Phase - Performance optimization and juice
  • Release Phase - Platform exports and certification

WeChat Mini Game Workflow

  • Version Control - Git strategy for project files
  • Scene Workflow - Prefab-like scene development process
  • Asset Pipeline - Import automation and validation
  • Build Automation - WeChat Mini Game headless export scripts
  • Testing Pipeline - Testing framework integration

Quality Assurance

Performance Metrics

  • Frame Time Targets - Maximum ms per frame by system
  • Draw Call Limits - Per-scene rendering budgets
  • Physics Budget - Maximum active physics bodies
  • Memory Footprint - Platform-specific memory limits
  • Load Time Goals - Scene transition time requirements

Testing Strategy

  • Unit Testing - Unit tests for JavaScript
  • Integration Testing - Scene and event flow validation
  • Performance Testing - Profiler-based optimization workflow
  • Platform Testing - Export template validation process
  • Playtesting Plan - WeChat Mini Game analytics integration

Documentation Quality

WeChat Mini Game Integration

  • Object Documentation - Clear descriptions of object purposes
  • Event Documentation - Event flow and parameters defined
  • Export Variables - All exposed parameters documented
  • Resource Formats - Custom resource specifications
  • API Documentation - Public methods and properties described

Implementation Guidance

  • Code Examples - JavaScript snippets for complex systems
  • Scene Templates - Example scenes demonstrating patterns
  • Performance Notes - Optimization guidelines per feature
  • Common Pitfalls - Known WeChat Mini Game gotchas documented
  • Best Practices - WeChat Mini Game-specific patterns recommended

Multiplayer Considerations (if applicable)

Network Architecture

  • Multiplayer Type - P2P vs dedicated server using the WeChat Mini Game's high-level API
  • RPC Design - Remote procedure calls and synchronization
  • State Replication - What state needs network synchronization
  • Lag Compensation - Client prediction and reconciliation
  • Bandwidth Budget - Network traffic limits per player

Final Readiness Assessment

WeChat Mini Game Implementation Ready

  • Scene Planning Complete - Object hierarchy and composition defined
  • Performance Validated - 60+ FPS achievable with design
  • Language Strategy Clear - JavaScript decisions made
  • Asset Pipeline Ready - Import settings and workflow defined
  • Testing Framework - Testing strategy established

Document Approval

  • Design Review Complete - Game design validated by team
  • Technical Review Complete - WeChat Mini Game feasibility confirmed
  • Performance Review Complete - Frame rate targets achievable
  • Resource Review Complete - Team capabilities match requirements
  • Final Approval - Document baselined for development

Overall Assessment

Document Quality Rating: ⭐⭐⭐⭐⭐

Ready for WeChat Mini Game Development: [ ] Yes [ ] No

Performance Risk Assessment: Identify any design elements that may challenge 60 FPS target.

Language Recommendations: Suggest which systems should use JavaScript for optimal performance.

Key Recommendations: List critical items needing attention before WeChat Mini Game implementation.

Next Steps: Outline immediate actions for starting WeChat Mini Game development.