FPS Game Creator

Turn a game idea into a first-person shooter through a structured creation and iteration workflow. Customize the setting, visual direction, controls, and scope, then develop and test a playable implementation with clear quality checkpoints.

Choose how much you want to customize

• Quick — strongly recommended for first-time users. Provide the setting, visual style and mood, target platform, and desired level count or playtime. Special requirements are optional; the Agent designs the remaining details and offers examples when you are unsure.
• Deluxe. Define around ten key creative and gameplay decisions for more control over the result.
• Ultimate. Customize the broader production specification in depth. Best reserved for experienced users with detailed requirements; not recommended as a first project.

All three modes use the same quality requirements. Quick reduces the amount of information you need to provide, not the visual or gameplay acceptance standard.

Build around your setting

Create a tense space-station operation, forest hunt, urban mission, desert outpost, or another FPS setting. Objectives, equipment names, architecture, surface materials, lighting, interface, and audio direction should fit the chosen world. State preferences such as “no horror,” your preferred art style, or a reference experience in the brief.

Gameplay included by default

Unless the brief explicitly changes them, the first implementation should include:

• Three staged objectives with 30-second intelligence-transfer or equivalent active-defense phases.
• Progressively increasing enemy pressure across stages.
• A first-stage reward: a powerful S686-style double-barrel shotgun, or a theme-appropriate equivalent with the same close-range role.
• A second-stage reward: 300 points of armor or shielding. When depleted, it enters a repair-needed state.
• A third-stage reward: restoration of lost health, ammunition, and armor.
• Automatic reloading after the final loaded round when reserve ammunition is available.

These mechanics adapt to the requested setting; they are not restricted to a foggy forest or literal listening stations.

Responsive desktop controls

Mouse and trackpad movement directly control the view and aiming direction. Movement keys control the character's movement. The workflow includes pointer-lock handling, a fallback when pointer lock is unavailable, and input-state resets around pause, focus loss, and leaving the game area. Shooting, weapon switching, reloads, and feedback are checked together.

Quality checkpoints before full production

A representative playable scene comes first. It must include the first-person weapon and hands, a primary enemy, a close-up material, a mid-distance combat route, a distant landmark, and real firing and damage feedback.

Visual acceptance checks cover all seven core areas: weapons and hands; enemies and grounding; large surface materials; near, middle, and far spatial layers; lighting and readability; coordinated motion and combat feedback; and a consistent style across menus, gameplay, and HUD. Any failed core item means the visual gate fails. A polished menu cannot substitute for a finished game scene.

Obvious placeholder geometry, unfinished large surfaces, missing player-view evidence, or critical visual failures must be reported as a prototype rather than a finished product. The workflow requires an asset manifest recording local paths, sources, licenses, actual integration, and suitability for the intended presentation.

Testing and delivery

The Agent works toward playable game files, editable source, control instructions, asset documentation, and recorded QA findings, as supported by the development environment. Testing covers gameplay progression, rewards, weapon behavior, input, and visual presentation. Requested playtime is evaluated through actual play rather than timer padding; a ten-minute brief targets roughly 8–12 minutes for a typical first successful run, with faster experienced runs allowed.

Scope and requirements

This Agent supports first-person shooters only. It is a development Skill, not a bundled game engine or a prebuilt game. It requires a compatible Agent environment with file editing, code execution, browser testing, and access to appropriate assets. Additional asset licenses or services may be needed for a particular brief. Final quality and completion depend on the available tools, assets, and the project's scope; unmet acceptance criteria must remain clearly documented.

Example request

“Quick mode: a space station, sci-fi and tense but not horror, desktop browser with keyboard plus mouse or trackpad, one level lasting about ten minutes. You decide the rest.”