How akazdayo/musicarcade2 works
Key Components to Include in the System Design:
Core Game Architecture
• Main game states (MusicState and PlayState)
• Core game components (Notes, Judge, KeyMap)
• LoadMusic component to show music data handling
Platform-Specific Layers
• Create two separate deployment targets:
a. HTML5 Build (Web Platform)
b. Desktop Build (Electron wrapper)
• How the core game interfaces with each platform
Asset Management System
• Separation between:
• Music data (JSON files)
• Chart data (CSV files)
• Image assets
Server Component
• Python server component
• How it interfaces with the main game for URL-based chart loading
Use a Layered Architecture Approach
Top Layer: User Interface (Platform-specific)
Middle Layer: Game Core (Haxe Flixel Components)
Bottom Layer: Asset Management and Server
Component Relationships
Specific Elements to Include:
Core Game Components
Main.hx → MusicState.hx → PlayState.hx
• ↓
Notes.hx ← Judge.hx
• ↓
KeyMap.hx
Asset Flow
assets/data/charts ←→ LoadMusic.hx
assets/images ←→ Judge.hx
**music/*.json ←→ LoadMusic.hx**
Platform Deployment
Haxe Flixel Core
• ↙ ↘
HTML5 Build Desktop Build (Electron)
Server Integration
Python Server (main.py)
• ↕
URL-based Chart Loading
• ↕
Game Core
Build process flow
• Lime build system
• Desktop packaging with Electron
Entry points
• Web entry
• Desktop entry (main.js)
• Server entry (main.py)
Level of Detail:
• Keep high-level components visible but include subcomponents where critical
• Major data flows but avoid cluttering with implementation details
• Technology stack labels:
• Haxe Flixel
• Electron
• Python
• Asset formats (JSON, CSV)
• Clear component hierarchy
• Multiple relationship types
• Export to high-resolution formats