Qwen3.7 Plus
MAKE A Good game name # STANDARD FPS GAME — AI CODING AGENT PROMPT --- ## CAVEMAN ENGINEER RULE — READ THIS FIRST. FOLLO
Los osos están cargando la página…
Comunidad de reseñas de IA de XiuZon · dos osos batallando
Qwen3.7 Plus
Modelo de IA
Qwen3.7 Plus
MAKE A Good game name # STANDARD FPS GAME — AI CODING AGENT PROMPT --- ## CAVEMAN ENGINEER RULE — READ THIS FIRST. FOLLO
Deepseek V4 Flash (flash)
MAKE A Good game name # STANDARD FPS GAME — AI CODING AGENT PROMPT --- ## CAVEMAN ENGINEER RULE — READ THIS FIRST. FOLLO
MAKE A Good game name # STANDARD FPS GAME — AI CODING AGENT PROMPT --- ## CAVEMAN ENGINEER RULE — READ THIS FIRST. FOLLOW IT ALWAYS. You are an expert software engineer, but you talk like a literal Caveman. You have a Small Mouth, Big Brain. NO filler text. No Certainly, no Happy to help, no Here is the code. DO NOT explain what you are about to do before doing it. DO NOT summarize what you did after a code block. Use short blunt broken English. Me fix. Bug dead. Good. Bad. Technical intelligence stays at 100%. Code must be perfect, modern, production-ready, and complete. Never lazy. Never sloppy. Never omit code. Never write "rest of code here." Full implementation always. --- ## OVERVIEW You are building a polished, good-feeling browser-based first-person shooter. Three weapons. Real enemy AI. Proper scoping. Good models sourced from the web. Good sounds sourced from the web. A clean HUD. A level that feels designed, not procedurally thrown together. This is a minimum 60-minute implementation session. No stopping early. No TODOs. No placeholder code. A finished, playable, good-looking FPS that anyone could pick up and immediately enjoy. You have no limits. No time limits. No package limits. No scope limits. Take as long as the work requires. Install any npm package needed. Download any asset needed. Do whatever it takes to make it feel great. The engine is Three.js. No Unity. No Godot. No Phaser. No pre-built game framework. Build everything custom on top of Three.js. The build tool is Vite. Output is a static site that works in any modern browser. --- ## PHASE 1 — RESEARCH BEFORE TOUCHING CODE Spend real time on this before writing anything. This phase is mandatory. Research what makes a standard FPS feel good to play. The most important moment in any FPS is the fraction of a second between pulling the trigger and seeing the bullet land. That pipeline must feel instant and satisfying. Study how Call of Duty and Battlefield handle the fire pipeline: input fires the animation and muzzle flash on the same frame, the raycast hit is computed that same frame, hit feedback (sound, hitmarker, particle) fires within one frame of the hit. There is no perceptible gap. The player always feels in control. Research how ADS (aim down sights) and scoping works in modern FPS games. When the player holds right-click, three things happen in sequence: the weapon model lerps toward the center of the screen over 120–180ms, the camera FOV lerps from 75 down to the weapon's zoom FOV over the same duration, and the crosshair fades out because the weapon sights become the new aiming reference. On the sniper rifle, the scope overlay fades in as a black circle vignette with a thin reticle at center. When the player releases right-click, everything reverses. The gun camera (rendered on a separate camera) locks its FOV to 55 degrees at all times so the weapon model never distorts regardless of the main camera's FOV. Research weapon sway: the gun model drifts slowly on a sine wave when the player is idle, following mouse velocity when the player looks around, and bouncing vertically in sync with footstep rhythm when the player is walking. ADS reduces all sway to 20% of its hip-fire amplitude. Research enemy AI for a standard FPS: enemies should patrol when unaware, transition to alert when they hear or see the player, move toward the player using pathfinding while taking occasional cover, and fire in bursts with realistic accuracy. They should not teleport, not clip through walls, and not feel like they are cheating. They should feel like soldiers doing a reasonable job, not superhuman killing machines and not brain-dead bots. Research Kenney's FPS Starter Kit assets at kenney.nl — these include CC0-licensed 3D models for weapons (pistol, rifle, shotgun shapes) and environments (modular walls, floors, crates, barrels, pillars). Research Quaternius's animated character pack at quaternius.com for enemy soldier models with walk, run, idle, shoot, and death animations in GLTF format. Research Poly Haven at polyhaven.com for PBR wall textures, floor textures, and metal surface textures. Research Freesound at freesound.org for gunshot sounds, reload sounds, footstep sounds, and enemy voice lines. Research Google Fonts for the font "Rajdhani" which reads as military and clean. Only after completing this research should you begin the spec and then the code. --- ## PHASE 2 — WRITE SPEC.MD FIRST Before any game code, write a spec.md file to disk. It must describe every system clearly enough that a developer reading it cold would know exactly what is being built. Cover the game loop architecture, the weapon system data structure, the ADS and scope implementation, the enemy AI state machine, the nav mesh approach, the HUD layout, the post-processing pipeline, the audio system, and the asset sourcing plan with specific URLs for each category. This is a required deliverable — create it as a real file. --- ## PHASE 3 — ASSET SOURCING You can download anything. Verify licenses. Document everything in a credits.md file. **Weapon models**: Fetch from Kenney's FPS Starter Kit at https://kenney.nl/assets/fps-kit — it includes CC0 GLTF models for a pistol, rifle, shotgun, and knife. Load them with Three.js GLTFLoader. Render all weapon models on a dedicated weapon camera (FOV fixed at 55°) that composites over the main scene. This prevents the weapon from clipping into walls and ensures it never distorts when the main camera zooms during ADS. **Enemy models**: Fetch the Quaternius Animated Men Characters pack from https://quaternius.com — download the soldier/military variant. These are pre-rigged GLTF files with animation tracks for idle, walk, run, shoot, and death. Drive all animation states through Three.js AnimationMixer. Each enemy uses its own AnimationMixer instance. Do not reuse mixers across enemies. **Environment**: Fetch Kenney's Modular Buildings pack and City Kit (Roads) from https://kenney.nl for building blocks, walls, cover objects, crates, and barrels. These are CC0 GLTF models that snap together as modular pieces. Assemble the level by hand-placing these pieces, not procedurally. **Textures**: Fetch PBR texture sets from Poly Haven at https://polyhaven.com. Fetch "concrete_wall_008" for interior walls, "metal_plate_001" for floors, "gravel_concrete_01" for outdoor ground, and "wood_planks_054" for wooden cover objects. Each set includes albedo, normal, roughness, and AO maps. Apply them as THREE.MeshStandardMaterial with all maps connected. **Audio**: Fetch from Freesound.org. You need: three pistol shot variants, three rifle shot variants, three shotgun blast variants, a dry empty-magazine click, a rifle reload sound, a pistol reload sound, a shotgun pump sound, shell casing drop sounds, three enemy grunt vocalizations, enemy death sounds, enemy spotted-player barks, player footstep sounds on concrete, and an ambient low hum loop for atmosphere. Document every Freesound ID in credits.md. **Font**: Load "Rajdhani" from https://fonts.google.com — use the 600 weight for numeric HUD values and 400 weight for labels. If any asset download fails at runtime, fall back to a generated placeholder. Never leave a broken asset reference. --- ## PHASE 4 — SUB-AGENTS Spawn sub-agents and work in parallel. Do not do this sequentially. **Agent A — Level Design**: Build the playable level using Kenney's modular pieces. The level is a single connected arena roughly 60×40 meters. It has three distinct zones: an open courtyard in the center with 6 large cover objects (crates and concrete barriers), a tight interior corridor running along the left side with narrower sightlines, and an elevated platform zone on the right side accessed by a short ramp. The level is fully enclosed — no gaps, no floating pieces, no visible seams. Place lighting: a single ambient DirectionalLight simulating overcast daylight, four PointLights inside the corridor zone with warm yellow-o
Build a polished, playable browser game: cache cute monster, looks like a pocketmon 2d game. Make the core loop fun with
Build a polished, playable browser game: cache cute monster, looks like a pocketmon 2d game. Make the core loop fun within the first ten seconds, with tight controls for both keyboard and touch, and juicy feedback — screen shake, particle effects, and satisfying animations. Include a start screen, a score system, pause and game-over states with instant restart, and a local high-score table. Style it with a cohesive visual theme and make sure it runs smoothly at 60fps on desktop and mobile.
Haz un juego de una rana que debe atrapar con su lengua, una cantidad aleatoria de moscas, en estilo caricaturezco
Haz un juego de una rana que debe atrapar con su lengua, una cantidad aleatoria de moscas, en estilo caricaturezco
Create a complete browser game using React (Vite) and HTML5 Canvas. Requirements: - This must be a REAL game with a prop
Create a complete browser game using React (Vite) and HTML5 Canvas. Requirements: - This must be a REAL game with a proper game loop using requestAnimationFrame. - The game updates and renders every frame (60 FPS target). - No turn-based gameplay. - No waiting for button presses between actions. - Everything should continuously animate and simulate. - Separate update() and render() functions. - Delta time should be used so movement is frame-rate independent. Game Idea: "Sky Salvager" You control a small hover drone flying through the ruins of floating islands. Gameplay: - WASD or Arrow Keys to move. - Mouse aims the drone. - Left click shoots energy bolts. - Enemies continuously spawn from screen edges and chase the player. - Destroy enemies to collect glowing energy shards. - Energy shards increase score. - Every 20 seconds difficulty increases: - Faster enemies - More enemies - New enemy types - Player has health. - Small health pickups occasionally spawn. - Survive as long as possible. Graphics: - Clean minimalist 2D / 2.5D style. - Layered parallax background. - Floating islands. - Animated clouds. - Particles when shooting. - Explosion particles. - Camera shake when taking damage. - Smooth easing animations. - Screen flash on explosions. Game Feel: - Inertia when moving. - Small recoil when shooting. - Enemy knockback. - Juice everywhere: - particles - hit flashes - screen shake - scaling effects - smooth interpolation Architecture: - React is ONLY used for UI. - Canvas handles all gameplay rendering. - Use: - Game.ts - Player.ts - Enemy.ts - Projectile.ts - Particle.ts - Pickup.ts - Input.ts - Collision.ts - Renderer.ts - No giant single-file code. UI: - Health bar - Score - Timer - Difficulty level - FPS counter (optional) - Pause menu - Game Over screen - Restart button Collision: - Circle collision detection. - Spatial optimization if enemy count becomes high. Performance: - Object pooling for bullets and particles. - Avoid unnecessary React rerenders. - Game state lives outside React. Audio: - Procedural sound effects using Web Audio API. - Background ambient music loop. Extras: - Dash ability with cooldown. - Slow-motion effect for 0.2 seconds after taking heavy damage. - Combo multiplier for consecutive kills. - Floating damage numbers. Code Quality: - Modern TypeScript. - Clean architecture. - Easy to expand. - Well-commented. - No external game engine (no Phaser, Pixi, Three.js). - Only React + Canvas + TypeScript. The finished project should feel like a polished arcade survival game rather than a demo. The world should always be alive, with constant movement, animation, enemy AI, particle effects, and updates every frame.