How sancode86/infinite-autogenerated-rpg-3d-game works
Project type and purpose
• This is a static, browser-based 3D RPG/demo game built with Three.js and Ammo.js for rendering and physics.
• No backend code—everything lives client-side: HTML, CSS, JS modules, 3D models, textures, and audio assets.
File structure
• Top-level: README.md and a single client/ folder.
• Under client/:
• index.html and game.html (entry points for menus and the main game canvas)
• css/ (styles for UI and in-game menus)
• js/ (game logic subdivided into modules: menu, options, input, physics, utils)
• js/ammo/ (Ammo.js physics engine + WebAssembly)
• utils/ (characterControls, loot, tilt, general utilities)
• models/ (glTF/GLB assets for characters, environments, items, enemies)
• audio/ (sound effects & music)
• Static config via package.json for local dev (npm scripts for live-serve).
README insights
• Game features: inventory, randomized loot & rooms, shop spawns, boss fights, cooldown abilities, movement mechanics.
• Emphasis on performance tweaks (shadowMap off).
• Uses Three.js for rendering, Ammo.js for physics, glTF/glb models from external source, audio files for effects/music.
Final recommendations
• Be exhaustive: break down the client into as many distinct logical pieces as possible.
• Data flows (e.g., “Player presses E → CharacterControls → Physics impulse → Renderer updates”).
• Performance or configuration flags (e.g., shadowMap disabled).