Skip to content
SEELE

Seele AI · Create

3D FPS Game

Move from a broad creation goal to a clearer playable direction faster in Seele AI.

A 3D FPS game prototype needs a real first-person combat loop: mouse look, movement, firing, reloads, damage feedback, enemies, and a restartable objective. For multi-weapon play, specify numbered weapon slots, cycling behavior, per-weapon ammo, fire rate, recoil, and HUD state. The hero visual is a SEELE-supplied thematic concept image. It illustrates a desert FPS direction; it is concept art, not gameplay and not proof of a generated SEELE result. Independent gameplay proof is shown below from Operation Ironhold, an open-source browser FPS built with Three.js r128. The screenshot visibly shows first-person combat, an M4 viewmodel, health and armor, ammo, targets, and four weapon slots. It is third-party, MIT-licensed, and not created by, generated by, or affiliated with SEELE. Source: https://github.com/StarKnightt/operation-ironhold ; live demo: https://starknightt.github.io/operation-ironhold/ ; license: https://github.com/StarKnightt/operation-ironhold/blob/main/LICENSE . This reference verifies browser Three.js FPS and multi-weapon feasibility only; SEELE output still requires playtesting.

Intent → iteration → handoff
Thematic desert first-person shooter concept with ruins, rifle, opponents, and bright combat effects; concept art, not gameplay.
SEELE-supplied thematic concept image; illustrative concept art, not gameplay and not proof of a generated SEELE result.

The working loop

Build The Combat Loop In Three Focused Passes

01

Specify The FPS Rules

Describe the desert arena, first-person controls, enemies, objective, retro HUD, and exact weapon slots. Seele turns the request into a scoped browser-game plan.

Outcome
A Three.js FPS generation brief.
02

Generate The Playable Slice

Run the exact starter prompt and keep weapon switching, firing, reloads, damage, and restart behavior in scope. Seele creates an editable first-pass prototype for browser testing.

Outcome
A playable combat-loop draft.
03

Playtest Every Weapon

Verify pointer lock, movement, each weapon slot, ammo transitions, hit feedback, win/loss state, and mobile fallback messaging. Seele applies focused revisions while preserving the tested loop.

Outcome
A reviewed multi-weapon FPS prototype.

What leaves the page

What The First Build Should Include

Three.Js FPS Scene

A first-person desert arena with pointer-lock camera, movement, collision, enemies, and a clear objective.

Multi-Weapon Combat

Distinct rifle, shotgun, sidearm, and sniper slots with switching, ammo, reload, recoil, and fire behavior.

Retro HUD And Review Checklist

Health, armor, ammo, timer or objective state, active weapon feedback, restart path, and human playtest checks.

Fit and limits

Best For And What Still Needs Review

Best for

  • Testing a Three.js FPS combat loop
  • Comparing weapon feel and switching clarity
  • Iterating a desert arena and retro HUD

Still needs human review

  • Gameplay balance and difficulty
  • Browser performance, accessibility, and touch fallback
  • Asset, code, audio, and third-party license compliance
  • Security and production deployment

Before you start

FAQ

Can Seele AI create a Three.js FPS game from a prompt?

It can create an editable browser-game prototype from a focused brief. Test movement, pointer lock, combat, failure states, and performance before treating the result as production-ready.

How should I request multi-weapon switching?

Name each weapon slot and define keyboard numbers, mouse-wheel cycling, magazine and reserve ammo, reload rules, fire rate, recoil, range, and active-weapon HUD feedback.

What makes the gameplay proof independently verifiable?

The proof screenshot comes from the public Operation Ironhold repository and live GitHub Pages demo. The project documents Three.js r128, four switchable weapons, combat controls, and an MIT license. It is third-party and non-SEELE.

Is the desert hero image real gameplay?

No. It is a SEELE-supplied thematic concept image used to communicate the desert FPS direction. It is not gameplay and not evidence of a SEELE-generated game.

Will a generated FPS work on mobile?

Pointer-lock FPS controls are primarily desktop-oriented. A production version needs an explicit touch-control design or a clear unsupported-device fallback, plus responsive layout testing.

What should I playtest before publishing?

Test all weapon slots, fire and reload behavior, ammo state, collision, enemies, damage and death, win/loss conditions, restart flow, frame pacing, audio permissions, accessibility, and asset licenses.

Next move

Build 3D FPS Game faster in Seele AI

Turn a rough creation goal into a clearer prompt, direction, and next step inside Seele AI.

Open Workspace