How alexcroox/battlebit-stats works
Main Components Identification
The system should be represented with these primary components:
a) Frontend Application (Nuxt.js Based)
• Static Content Management
• Interactive Features
• 3D Model Visualization
• Rendering System
b) Asset Processing Pipeline
• Tiling System
• 3D Model Processing
• Image Assets Management
┌─ Frontend Layer ─────────────────────┐
• ┌─ Pages ─────┐ ┌─ Components ────┐ │
• Maps │ │ - ModelViewer │ │
• Weapons │ │ - Map │ │
• Stats │ │ - Navigation │ │
• ┘ │ - Stats │ │
• ┘ │
• Asset Processing Layer ───────────┤
• ┌─ Map Tiler ─┐ ┌─ Asset Store ─┐ │
• Raw Maps │ │ - Weapons │ │
• Processed │ │ - Vehicles │ │
• Maps │ │ - Maps │ │
• ┘ └──────────────┘ │
• ┘
Specific Implementation Details
• The Nuxt.js architecture (pages, components, layouts)
• The map tiling system's workflow
• The 3D model viewer's integration
• The relationship between configuration files (mapConfig.ts, weaponConfig.ts, vehicleConfig.ts) and their corresponding features
Data Flow Indicators
• How raw maps flow through the tiling system to the frontend
• How weapon models are loaded into the 3D viewer
• How configuration data is used throughout the application