How droxus/shooter works
Project type and purpose
• From the README (“Shooter – This is just a game…”) and the presence of scene.gltf/scene.bin assets, this is a browser-based 3D shooter game built with TypeScript and a bundler (Vite).
File structure
• Top-level:
– index.html & public/ : the static web entrypoint and static asset hosting (models, textures).
– src/ : client-side TypeScript code (main.ts) and CSS.
– vite.config.js, tsconfig.json, package.json : build & dependency configuration
– docs/ : generated documentation or demo site with the same assets duplicated for docs hosting.
README for additional insights
• Minimal description; no explicit architecture section. We infer the tech stack from config files:
– Vite as dev/build server
– TypeScript for game logic
– GLTF 3D scenes (likely loaded via three.js or similar)
Elements
– Labels: “Vite Dev & Build”, “Static Asset Server”, “Browser Runtime”, “Asset Loader”, “Game Engine Core”, “Renderer”, “Input Manager”, “UI Layer”
• Build → Bundle → Browser
• Browser → Asset Server → Loader → Engine/Renderer
• Input → Game Loop → Scene Manager → Renderer
• Runtime components in another
• Data stores (GLTF/texture files) in a third