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

Flat colour

Generated from: a scene from a small video game about: Build a complete, production-quality **original multiplayer browser FPS game** with a downloadable Windows version. ## PROJECT Create an original fast-paced 3D multiplayer FPS inspired by modern browser shooters, but do NOT copy Cryzen.io or any other game's proprietary assets, code, branding, maps, UI, or artwork. The game should have a polished, futuristic, cozy-dark visual style with excellent animations and smooth performance. Name the game **NEXUS STRIKE**. ## PLATFORMS Support: * Web browser * Windows downloadable version * Responsive UI * Keyboard + mouse controls * Optional controller support if practical The Windows version should be packaged as a proper downloadable application rather than requiring users to run development tools. ## GAMEPLAY Implement real playable FPS mechanics: * First-person camera * WASD movement * Sprint * Jump * Crouch * Mouse aiming * Shooting * Reloading * Weapon switching * Health * Damage * Headshot hit detection * Respawning * Kill/death tracking * Match timer * Score system * Team deathmatch * Free-for-all * Multiplayer rooms * Player names * Leaderboard * Spawn points * Bots for testing Use server-authoritative gameplay for multiplayer so clients cannot simply modify their own health, position, damage, or score. ## WEAPONS Create several original weapons with different characteristics: * Assault rifle * SMG * Shotgun * Sniper * Pistol Include: * Recoil * Reload animations * Muzzle effects * Hit effects * Sound effects * Ammo * Damage values * Headshot multipliers Keep all weapon models and artwork original. ## MAPS Create several original multiplayer maps with: * Buildings * Cover * Corridors * Open areas * Vertical areas * Spawn locations * Strategic positions Optimize the maps for low-end PCs. ## MOVEMENT & ANIMATION Make movement feel responsive and polished. Add: * Smooth camera movement * Weapon sway * Sprint animation * Jump animation * Crouch animation * Reload animation * Hit feedback * Kill notification animation * Respawn transition * Smooth UI transitions Respect reduced-motion accessibility settings. ## UI Create a premium dark futuristic interface. Include: * Main menu * Play * Server browser * Settings * Profile * Loadout * Leaderboard * Match HUD * Scoreboard * Pause menu * Admin panel Use rounded panels, subtle transparency, clean typography, tasteful gradients, and smooth micro-interactions. ## ADMIN SYSTEM Create a secure server-side administration system with roles: ### Owner Full administrative access. ### Admin Game/server management. ### Moderator Moderation tools only. Never trust the client to determine whether someone is an admin. Use server-side authorization for every admin action. ## INITIAL OWNER ACCOUNT Create an initial development Owner account: Username: jneey143 Initial password: jneey143 IMPORTANT SECURITY REQUIREMENTS: * Do NOT hard-code the password into frontend JavaScript. * Store the initial credential using secure environment variables/secrets. * Store passwords using a strong password hash. * Force the Owner to change the initial password after first login. * Never display the password in logs. * Never send passwords back to the client. * Never expose authentication tokens. * Add rate limiting to login. * Add session expiration. * Add logout. * Record administrative actions in an audit log. Use environment variables such as: ADMIN_USERNAME ADMIN_INITIAL_PASSWORD Provide a `.env.example` showing the required variables but never commit real production secrets. ## ADMIN PANEL Create a professional admin dashboard. ### Player Management Allow authorized admins to: * Search players * View username * View account status * View online/offline status * Kick * Temporary ban * Permanent ban * Unban * Mute * View reports * View moderation history ### Match Controls Allow authorized admins to: * Start match * End match * Restart match * Change game mode * Change map * Adjust match duration * Manage bots ### Developer/Test Tools These tools are ONLY for testing the game itself and must not function as cheats against unrelated games: * Aim-assist test mode * Headshot damage simulator * Player-outline/wall-visibility debug mode * Bot spawning * Bot difficulty controls * Weapon testing * Damage testing * Hitbox visualization * Player teleport for development testing * Spectator mode * Free-camera developer mode Clearly label these as **DEVELOPER TEST TOOLS**. Do not implement DLL injection, memory manipulation, anti-cheat bypasses, external-game cheats, or tools intended to give an unfair advantage in other games. ## ADMIN UI Make the admin panel accessible only after successful server-side authentication. Show: * Server status * Online players * Active matches * Player count * Server latency * Reports * Moderation actions * Audit logs Use confirmation dialogs for destructive actions such as permanent bans or deleting data. ## SECURITY Implement: * HTTPS-ready configuration * Secure authentication * Password hashing * Server-side authorization * Input validation * Rate limiting * Session management * CSRF protection where applicable * Secure cookies where applicable * WebSocket authentication * Server-side hit validation * Server-side movement validation * Anti-cheat protections for the game itself * Secure file validation * Protection against common injection attacks * Admin audit logging Never place privileged operations only in frontend code. ## ANTI-CHEAT Protect NEXUS STRIKE from cheating. Detect and mitigate suspicious: * Impossible movement * Impossible fire rates * Invalid damage * Invalid positions * Modified client state * Repeated abnormal actions Do not create an anti-ban system or bypass mechanisms. ## DOWNLOADABLE VERSION Create a proper Windows build. Provide: * Production build configuration * Windows executable/package * Game icon * Installer if practical * Version number * Auto-update architecture if practical The downloadable Windows version should connect to the same production multiplayer backend as the web version. ## PERFORMANCE Optimize heavily for lower-end hardware. Prioritize: * High FPS * Low memory usage * Efficient rendering * Asset compression * Texture optimization * Object pooling * Efficient networking * Low bandwidth usage * Lazy loading * Efficient multiplayer synchronization Avoid unnecessary background processes. ## AUDIO Add original or properly licensed: * Weapon sounds * Footsteps * Reload sounds * Hit sounds * UI sounds * Ambient sounds Provide volume controls. ## SETTINGS Include: * Graphics quality * Resolution * FPS limit * Mouse sensitivity * Field of view * Audio volume * Master volume * Music volume * Fullscreen/windowed mode * Key bindings * Reduced motion ## ACCOUNT SYSTEM Use: * Username * Password * Optional email if needed Do NOT require a phone number for normal game accounts. Users should be able to: * Create an account * Log in * Log out * Change username where permitted * Change password * Customize profile * View statistics ## DATABASE Create a proper database schema for: * Users * Sessions * Roles * Matches * Players * Statistics * Weapons * Reports * Bans * Messages if chat is included * Audit logs Use indexes and appropriate constraints. ## CHAT Add optional in-game text chat: * Match chat * Team chat * Player mute * Report player * Chat moderation * Spam protection Do not expose private administrative information through chat. ## TESTING Before declaring the project complete, test: 1. Create account 2. Login 3. Logout 4. Join match 5. Move 6. Shoot 7. Reload 8. Headshot 9. Die 10. Respawn 11. Scoreboard 12. Multiplayer synchronization 13. Admin login 14. Admin role permissions 15. Kick 16. Ban 17. Unban 18. Reports 19. Developer test tools 20. Windows production build 21. Web production build Fix errors rather than leaving TODO placeholders. ## IMPORTANT Do not create a fake prototype that only looks like a g, as an in-game screenshot in flat colour 2D shapes with a bright limited palette. Palette: sky blue #8ecae6, grass #3a7d44, player sunflower #ffb703, threat red #d62828, accent white #fdfcdc. 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.