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

Hand-drawn

Generated from: a scene from a small video game about: Act as a professional indie game developer, gameplay programmer, 3D game designer, and QA tester. Build a complete, playable, lightweight 3D third-person action game that runs in a desktop browser and is suitable for eventual Windows PC development. ## 1. Core gameplay * The player controls a warrior inside a small combat arena. * Use a third-person camera that follows the player smoothly. * The player can walk, run, turn, dodge, and perform sword attacks. * Enemies chase the player and attack when nearby. * Add working health bars for both the player and enemies. * The player wins after defeating all enemies. * The player loses when health reaches zero. * Include a restart button and a simple main menu. ## 2. Controls * W, A, S, D: Move. * Mouse: Rotate the camera, if supported. * Left mouse button: Attack. * Space: Dodge or roll. * Shift: Sprint. * Escape: Pause the game. Display the controls clearly on the screen. ## 3. Graphics and performance * Use a stylized low-poly 3D art style. * Create a small arena with stone walls, simple props, lighting, and atmospheric colors. * Use simple models and lightweight textures. * Avoid photorealistic graphics, expensive visual effects, huge maps, and unnecessary assets. * Target smooth gameplay on a basic Windows laptop with 8 GB RAM and integrated graphics. * Include a low-graphics mode where possible. ## 4. Game quality * Implement real movement, collision detection, attack animations or clear attack feedback, damage, enemy health, and defeat states. * Attacks must have a cooldown and must not damage enemies from unlimited distances. * Prevent the player and enemies from falling through the floor. * Ensure all buttons and controls work. * Add basic sound effects only if they can be included without requiring paid assets. ## 5. Development instructions * Build the smallest fully playable version first. * Do not create decorative screens that pretend to be gameplay. * Test movement, combat, enemy AI, health, victory, defeat, and restarting. * Fix errors before adding extra features. * If a requested feature cannot be implemented, explain why and provide a working alternative. First create the playable core game. After it works, suggest improvements one at a time., as an in-game screenshot in a hand-drawn ink and watercolour style. Palette: paper #f2e8cf, ink #283618, player tomato #bc4749, threat plum #6d597a, accent leaf #a7c957. 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.