Skip to content
SEELE

Seele AI · Focused prototype production

Build a Horror FPS prototype with a focused gameplay loop

Turn exploring a dark facility, managing scarce light and supplies, reacting to scares, and escaping an enemy pursuit into an original Horror FPS prototype with clear timing, feedback, and decisions.

Wide three-quarter 3D gameplay scene of flashlight-lit corridors, locked doors, hiding alcoves, supplies, and branching routes in a coherent cinematic abandoned research hospital at night with an original first-person survivor, handheld flashlight, worn corridors, emergency red lights, locked doors, scattered supplies, and an indistinct pursuing creature world, no interface
Action moment showing flickering lights, sudden silhouettes, creature pursuit, and blocked passages resolving clearly in the same cinematic abandoned research hospital at night with an original first-person survivor, handheld flashlight, worn corridors, emergency red lights, locked doors, scattered supplies, and an indistinct pursuing creature world, no text
Hero moment where visibility, resource scarcity, pursuit distance, and escape-route choices escalates around the player in the same coherent world, no HUD

Visible prototype result

Review the core loop before expanding content

Start with one bounded scene, one clear player goal, and a small number of meaningful interactions. Inspect controls, feedback, pacing, and consequences before scaling.

Over-the-shoulder game creator reviewing the original Unity Horror FPS scene in a professional game workspace on a large monitor, scene viewport dominant, tool controls abstract and unreadable

Built for early validation

Turn the brief into concrete evidence

Readable interaction language

Use flashlight-lit corridors, locked doors, hiding alcoves, supplies, and branching routes to distinguish actions, states, and consequences.

Visible game pressure

Show flickering lights, sudden silhouettes, creature pursuit, and blocked passages through in-world motion and staging rather than a fake HUD.

Bounded prototype loop

Connect introduction, escalation, recovery, and a clear finish around exploring a dark facility, managing scarce light and supplies, reacting to scares, and escaping an enemy pursuit.

Unity Horror FPS FAQ

Questions before you build

What is Horror FPS?

Horror FPS is a focused Unity browser-game prototype for testing exploring a dark facility, managing scarce light and supplies, reacting to scares, and escaping an enemy pursuit. A first build keeps one objective, compact rules, readable feedback, and a bounded play session. It is not production-ready without code review, device testing, accessibility work, asset-rights review, and human playtesting.

How do I prototype a horror first-person survival game?

Start with one playable scene and implement the smallest loop for exploring a dark facility, managing scarce light and supplies, reacting to scares, and escaping an enemy pursuit. Add input response, state changes, success and failure feedback, and only the progression needed to answer the first design question. Avoid expanding content until players understand the core interaction.

What should the first horror first-person survival game brief include?

Include the player goal, camera, controls, core rules, layout, feedback, target browser, and success condition. Also define performance limits, failure behavior, accessibility needs, asset direction, and the evidence the prototype should produce. Exact implementation choices still require engineering review in the target Unity stack.

What can I test with an early horror first-person survival game build?

An early build can test input clarity, visual readability, pacing, difficulty, feedback, and whether the central decision is engaging. Keep the session short and inspect hesitation, failure, recovery, and strategy moments. Broad progression, monetization, multiplayer, and content variety should be tested separately.

What are the limits of an AI-generated horror first-person survival game?

AI can accelerate visual and interaction exploration, but it cannot prove balance, accessibility, browser performance, stability, or player enjoyment. Creators must inspect generated code and assets, profile real devices, tune values, test edge cases, and run representative playtests. Generated scenes are prototype evidence rather than a claim of production readiness.

How do I start Horror FPS with Seele AI?

Describe the smallest playable scene that can validate exploring a dark facility, managing scarce light and supplies, reacting to scares, and escaping an enemy pursuit. Name visual style, player actions, rules, hazards, feedback, objective, failure state, target device, and the decision to validate. Keep the first request narrow so revisions remain tied to the gameplay question.

From idea to first result

Start building with Seele AI

Turn your idea into an interactive experience you can test and improve.

Get started for free