Made with Nano Banana 2 Lite · CC0 · 8 Oct 2026

Chunky low-poly

Generated from: a scene from a small video game about: Create the foundation of a polished mobile-first 3D FPS game. IMPORTANT: Treat this as the foundational architecture for the entire project. Do not create a throwaway prototype or a collection of disconnected demo systems. Build the systems modularly so future weapons, enemies, maps, UI, effects, and gameplay mechanics can be added without rewriting the core. CORE: - First-person 3D player controller - Mobile touch controls designed for phones - Left virtual joystick for movement - Right-side touch area for camera/look control - Jump and crouch controls - Smooth camera movement with configurable sensitivity - Proper FPS camera and player collision - Gravity and grounded detection - Sprint system with configurable speed - Sensible mobile control layout FPS FOUNDATION: - Modular weapon system - Weapon slot/inventory architecture - Shooting and raycast/projectile architecture - Hit detection - Damage system - Health system - Ammo and reload architecture - Interaction system - Crosshair - Basic FPS HUD architecture GAMEPLAY ARCHITECTURE: - Player state system - Enemy entity architecture - Basic enemy AI framework with states such as idle, patrol, investigate, chase, attack, and dead - Spawn-point system - Basic game-state manager - Pause system - Restart/death handling MOBILE PERFORMANCE: Design everything specifically for mobile hardware. - Object pooling where appropriate - Efficient collision and raycasting - Frustum culling - Distance-based update optimization - Avoid unnecessary per-frame allocations - Efficient enemy AI updates - Scalable rendering quality - Resolution/render-scale setting - FPS limit setting - Graphics-quality architecture - Keep systems lightweight and scalable VISUAL FOUNDATION: Create a clean, modern FPS presentation with proper 3D lighting, shadows, materials, atmospheric effects, and responsive weapon/camera movement. Use placeholder assets only where necessary, but structure the project so production-quality assets can later replace them without changing gameplay architecture. SETTINGS FOUNDATION: Create the architecture for: - Graphics quality - FPS limit - Render scale - Mouse/touch sensitivity - Audio volume - Master volume - Vibration toggle - Shadows toggle - Performance mode Do NOT spend time creating a large map, many weapons, detailed enemies, story content, shops, or cosmetic systems yet. The priority of this message is: 1. Correct FPS architecture 2. Mobile controls 3. Performance 4. Modularity 5. Stable foundation for future development Make the result immediately playable as a small FPS test scene so the core systems can be verified, but keep the architecture ready for the full game., as an in-game screenshot in chunky low-poly 3D with flat shaded materials. Palette: dusk violet #2b2d42, stone #8d99ae, player coral #ef8354, threat teal #2a9d8f, accent gold #f4d35e. Everything is original: never draw or resemble characters, places or logos from existing games, films or brands (no red-capped plumbers, no famous mascots), even when the idea names one. Keep the pictures honest: they promise what a small first version of this game, made in a game engine in a few days, can look like. Simple readable shapes, clear silhouettes, few flat materials, the in-game camera view. Never film stills, photoreal renders, AAA key art, detailed textures, cinematic lighting, or anything that looks like a big-studio game. No text, UI, HUD, logos or editor screens inside any image.