How trewrightserves/cube-basher works
Cube Basher is a browser-based, single-file 3D survivors-like game. The main workflow is to launch a run, move and survive while weapons fire automatically, choose in-run upgrades, and earn gold for permanent purchases between runs. The map separates run gameplay, metaprogression, and presentation/runtime concerns; these are documented capabilities, not inspected implementation modules. The README identifies index.html as the whole game and documents browser storage and CDN dependencies, but source excerpts were unavailable, so internal call relationships are omitted where wiring is uncertain.
Main entry points: index.html Game Entry
Components 15
Run Gameplay
- World and Movement
index.html - Playable Characters
index.html - Auto-Firing Weapons
index.html - Enemies and Bosses
index.html - Run Upgrades
index.html
Metaprogression
- Run Gold
index.html - Upgrade Lab
index.html - Browser Save Data
index.html
Presentation Runtime
- Game Entry
index.html - 3D Rendering
index.html - Procedural Audio
index.html
Other components
- Player
- Web Browser
- three.js CDN
- Fonts CDN
Connections 15
- Player → Game Entry: launches
- Game Entry → World and Movement: runs
- Game Entry → Playable Characters: offers selection
- Game Entry → Auto-Firing Weapons: runs combat
- Game Entry → Enemies and Bosses: runs encounters
- Player → World and Movement: moves and dodges
- Player → Run Upgrades: chooses upgrades
- Run Gold → Upgrade Lab: banks gold
- Upgrade Lab → Browser Save Data: saves purchases
- Game Entry → Web Browser: runs in
- Game Entry → three.js CDN: loads engine
- Game Entry → Fonts CDN: loads fonts
- Game Entry → 3D Rendering: renders
- Game Entry → Procedural Audio: synthesizes sound
- Web Browser → Browser Save Data: stores locally