Overview
This prompt aims to guide game developers in creating a 3D survival horror video game using Three.js and WebGL. Developers seeking structured design and implementation plans will benefit from this detailed outline.
Prompt Overview
Purpose: This document outlines the design and implementation plan for a 3D survival horror game using Three.js and WebGL.
Audience: The intended audience includes game developers and designers familiar with JavaScript and 3D graphics programming.
Distinctive Feature: The game features a unique stalking mechanic where a shadowy entity follows the player only from behind.
Outcome: Successful implementation will result in an engaging horror experience with immersive gameplay and optimized performance.
Quick Specs
- Media: Text
- Use case: Generation
- Industry: Animation & VFX, Business Communications, Content & Media Creation
- Techniques: Decomposition, Plan-Then-Solve, Structured Output
- Models: Claude 3.5 Sonnet, Gemini 2.0 Flash, GPT-4o, Llama 3.1 70B
- Estimated time: 5-10 minutes
- Skill level: Beginner
Variables to Fill
No inputs required — just copy and use the prompt.
Example Variables Block
No example values needed for this prompt.
The Prompt
Create a detailed design document and implementation plan for a 3D survival horror video game developed for PC using Three.js and WebGL.
The game is played in first person and takes place inside a maze environment defined by the following matrix representation, where:
– 1 = Wall
– 0 = Walkable space
– 2 = Exit
– 3 = Entry
“`
“12111111111111111111”,
“10100010001000100011”,
“10001000100010001011”,
“11111111111111111001”,
“10000000000001111101”,
“10111011111101000001”,
“10010010000101111101”,
“10111110110000010001”,
“10000010100101011011”,
“11011110111101000011”,
“11000010111101111011”,
“11011010100101000001”,
“10001000001101111101”,
“10111110100001001001”,
“10000010111111011101”,
“10111110000000000001”,
“10011111111111111111”,
“11010001000100010001”,
“11000100010001000101”,
“11111111111111111131”
“`
### Design Requirements
Include in your design:
– Maze Rendering and Navigation
– How to render and navigate the maze defined by the matrix in a first-person perspective using Three.js and WebGL.
– Player Mechanics
– Player mechanics for movement and interactions within the maze.
– Hostile Shadowy Entity
– Implementation of a hostile shadowy entity characterized as follows:
– Completely shadowy appearance
– Two distinct white pupils
– Behavior: stalks the player only from behind, never appearing directly in front or to the sides.
– Entity Detection Methodology
– Provide a clear methodology for detecting and handling the entity’s position relative to the player, ensuring it follows consistently from behind without surpassing the player.
– Game Mechanics
– Outline game mechanics such as survival elements, player health, objectives, and how the player can find and reach the exit.
– Optimization Techniques
– Discuss any optimization techniques needed for smooth rendering and gameplay performance.
### Implementation Steps
1. Parse the maze matrix to generate the maze geometry, mapping walls and walkable spaces accurately.
2. Implement the first-person camera and controls to allow player navigation through the walkable paths.
3. Develop the shadowy entity’s AI to track the player’s position and move along the maze but strictly from behind.
4. Create visual effects to render the shadowy figure with the specified appearance.
5. Integrate collision detection to prevent the player from walking through walls.
6. Define game state logic to manage player survival, entry point at ‘3’, and successful exit upon reaching ‘2’.
7. Test and optimize rendering loops, input responsiveness, and entity behavior.
### Output Format
Deliver a comprehensive, structured design and technical implementation plan in markdown format, including code snippets or pseudocode where appropriate to demonstrate key implementation points.
### Notes
– Assume Three.js and WebGL are the primary libraries used.
– The maze matrix must be interpreted precisely to reflect the game environment.
– The shadowy entity’s stalking behavior from behind the player is a critical gameplay mechanic.
– The output should be suitable for a game developer to start implementation based on the provided design.
Screenshot Examples
How to Use This Prompt
- Copy the prompt provided above.
- Paste it into your preferred text editor.
- Modify any sections as needed for your project.
- Use the design requirements as a checklist.
- Follow the implementation steps sequentially.
- Test and refine your game based on the output.
Tips for Best Results
- Maze Rendering: Use Three.js to create a 3D representation of the maze by parsing the matrix and generating walls and walkable spaces with appropriate geometries.
- Player Mechanics: Implement first-person controls using pointer lock API for immersive navigation, allowing movement and interaction with the maze environment.
- Shadowy Entity AI: Design the entity to track the player’s position from behind, using a distance check to ensure it never appears in front or to the sides, enhancing the horror experience.
- Game State Management: Establish logic for player health, survival objectives, and exit conditions, ensuring a clear path from entry to exit while managing player interactions with the environment.
FAQ
- What is the primary technology used for game development?
The game is developed using Three.js and WebGL for rendering 3D graphics. - How is the maze represented in the game?
The maze is represented by a matrix where '1' indicates walls and '0' indicates walkable spaces. - What is the behavior of the hostile entity?
The entity stalks the player from behind, never appearing in front or to the sides. - What are the main player mechanics in the game?
Players can navigate through the maze, interact with objects, and manage their health.
Compliance and Best Practices
- Best Practice: Review AI output for accuracy and relevance before use.
- Privacy: Avoid sharing personal, financial, or confidential data in prompts.
- Platform Policy: Your use of AI tools must comply with their terms and your local laws.
Revision History
- Version 1.0 (February 2026): Initial release.
