Remix

Make your own version of Haunted Mansion Escape

Get an exact, working copy in your account, then change anything with chat.

Original by Madhava goddendla

What would you change?

Start free with 40 credits. No card needed.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.

# Create a New 3D Horror-Adventure Game from Scratch

Create a **new project from scratch** in this account. This is a new build of the game concept described below. Do not repair, import, or depend on a project from another account. Build a playable 3D game—not just a design document, static mock-up, or menu.

# Credit limit and delivery

My maximum budget is **10 Emergent credits**. Do not purchase credits, enable paid usage, or exceed this limit.

First check what can realistically be built within the limit. Then start implementing the highest-priority playable version. Avoid repeated planning runs and unnecessary rewrites. If the full scope cannot fit within 10 credits, stop before exceeding the limit and report what is playable, what remains unfinished, and how many credits were used.

Build priorities:

1. A project that loads and starts reliably.
2. A playable 3D mansion with connected floors and stairs that work.
3. The opening, exploration, core escape puzzle, ghost encounter, and ending.
4. The specified rooms, clues, objects, and exterior gate.
5. More animated scenes, optional mysteries, and polish.
6. Real online multiplayer, only if the remaining credits and technical setup permit it.

The full specification is the intended game. Do not claim a feature is complete unless it has actually been implemented and verified.

# 1. Game concept and visual direction

**Working title:** *Nightfall: The House That Repeats*

Create a serious, frightening, realistic 3D horror-adventure. Use believable human proportions, expressive faces, detailed clothing, natural character movement, grounded architecture, realistic materials, atmospheric lighting, and well-composed camera shots.

The visual ambition is the general level of polish, animation, environmental detail, and world presentation associated with a large modern action-adventure game. Use GTA 6 only as a broad quality reference. Do not copy its story, characters, branding, map, or assets.

The game should feel like a substantial, explorable place, not a tiny room. Build a medium-sized house and surrounding property that work together as one map. Keep the art detailed but optimized for phones and PCs.

Use character models that look human and animated. Do not use default block-shaped people or leave the world as a gray floor with a few simple boxes. Use original or properly licensed assets. If the platform cannot generate a requested asset, make the closest polished original version and state the limitation.

Use an over-the-shoulder third-person camera so players can see the character, movement, hiding, and scares. Allow camera sensitivity and distance adjustments. If first-person view is feasible, it can be an optional camera setting.

# 2. Main characters

Keep all three names and spellings:

- **Uthej:** alert, direct, and observant. His room contains visible U.S. dollars and an important clue.
- **Karthik:** wears large round eyeglasses and has a gentle, observant appearance inspired by Nobita’s glasses. Create him as an original, believable 3D character.
- **Ranjith:** practical and courageous, but still capable of fear. Include the hidden “OG Ranjith” room as a secret creator-style Easter egg.

Give each character a distinct voice, animation style, and way of reacting to danger. Keep dialogue natural, short, and easy to follow.

# 3. Story and complete gameplay flow

The story is about an old mansion that repeats fragments of conversations through its walls and failing electrical system. Some voices help the friends understand the house. Others imitate them to lure them into danger. The ghost is real within the game.

Do not write a childish story. Keep the central mystery understandable, but let environmental clues, optional discoveries, and character conversations give the player more to uncover. Do not set a fixed number of minutes for completion. Make the game challenging through exploration, stealth, puzzles, and danger.

## Opening menu and introduction

Start with a polished title screen with the game name, a play option, settings, and solo/co-op choices if co-op is genuinely implemented.

The opening should be an animated scene, not a still image with text. Show a severe storm outside the mansion. Uthej, Karthik, and Ranjith arrive seeking shelter. Show the house and its approach clearly. The entrance closes behind them, and they discover that the way back is blocked.

Use camera movement, weather, character animation, sound, and short conversations. Let players skip or replay the scene. Provide subtitles.

Example tone for the dialogue:

- Karthik: “The gate just shut. Did either of you touch it?”
- Uthej: “No. And the lights downstairs were off a second ago.”
- Ranjith: “Then why can I hear someone coming up the stairs?”

Use these as tone examples, not mandatory lines.

## Beginning of playable exploration

Place the player in the mansion entrance. Show a brief control hint and one clear first objective. Introduce movement and interaction without a long tutorial. Let players inspect the house and notice sounds or details that feel wrong.

The first goal should lead players toward a key, service route, or clue that reveals how the house and gate work. Make it clear enough to start, but do not immediately reveal the entire escape solution.

## Exploration and discoveries

Let the player search all accessible floors, collect clues, talk to the friends, and learn how the house works. Give the player reasons to explore optional rooms: a note, a strange object, a voice recording, a hidden passage, or a surprising sight.

Use the environment to tell the story. The player should be able to notice details such as a chair moved between visits, wet footprints leading upstairs, or a familiar voice coming from an empty room.

## Middle of the game

Include at least one significant animated scene during the middle of play. It should reveal an important part of the mansion’s history, increase the danger, and make the player reconsider what they have heard.

The scene should use actual camera and character or ghost animation with sound and dialogue. A static text panel does not count as an animated scene. Keep scenes skippable and provide subtitles.

## Escalation and final escape

As the player restores the house’s systems and approaches the exit, make the ghost more active. Add a tense search or chase sequence that uses the rooms, stairs, hiding places, and corridors.

The final objective is to operate the basement machinery and escape through the property’s main gate. Include a final animated sequence during the gate escape and a short ending that reflects clues the player found.

# 4. Mansion, grounds, and levels

Build one connected medium-sized mansion and its property, with four levels:

1. **Underground basement:** utility rooms, storage, machinery, and a service passage.
2. **Ground floor:** entrance hall, main rooms, kitchen or service area, and a clear route to the outside gate.
3. **First floor:** bedrooms and other furnished rooms, including the two specified rooms.
4. **Roof:** a place to look out over the storm and grounds. It is not an escape route. Add safe boundaries and prevent players from escaping from the roof.

Connect the floors with real, walkable stairs and landings. The player must be able to ascend and descend without getting stuck, falling through the floor, sliding away, or being blocked by invisible collision.

The exterior should look like an old, wealthy mansion from the approach, with a recognizable entrance, windows, porch, roofline, aged materials, outdoor lights, and surrounding grounds. Include a path or driveway, yard or garden, and service areas so the player can explore around the building.

The main gate must look substantial and function as the actual exit. Give it a visible frame, hinges, locking or release mechanism, working collision, and an opening animation. It must not be merely a decorative image or object.

Fill the house with varied, believable items: furniture, lamps, books, cabinets, curtains, rugs, dishes, tools, boxes, papers, pictures, and signs of age. Arrange these deliberately. Keep useful sightlines and navigation clear.

# 5. Required rooms

## Uthej’s old wealthy room

Make the first specified room feel rich but old and neglected. Include ornate furniture, aged gold details, expensive-looking objects, a **Mona Lisa painting on a wall**, and **“Uthej” sprayed on another wall**.

Add noticeably more U.S. dollar bills and cash bundles than in the earlier version: some scattered and some stacked. Include at least one clue among the room’s objects. The money should contribute to atmosphere or clue discovery, not become a meaningless collection task.

## Karthik and Sonavitha bedroom

Make the second specified room moderately furnished. Include:

- A bed where the player can hide under or inside it.
- A clear interaction to enter and leave the hiding place.
- A table with a book titled exactly **“how to flirt sonavitha”**.
- A framed image showing only **Nobita and Shizuka**.
- **“Karthik”** written directly below Nobita.
- **“Sonavitha”** written directly below Shizuka.

The bed must function as a real hiding place. The ghost can search nearby, so timing matters.

## Secret OG Ranjith room

Make a hidden room with a black background wall, large red painted **“OG”**, and small corner text **“Developed by OG Ranjith”**.

The room must be discoverable through an in-game clue. Place a necessary escape object or important mechanism clue inside. Make the reveal feel special using lighting, sound, and camera framing.

# 6. Items, clues, and escape puzzle

The player must find and use several different items to escape. Give each item a clear purpose and provide fair clues to help players find it. Avoid random fetch quests or requiring the player to search every drawer.

Use a connected puzzle such as:

1. Find a service key that opens the basement route.
2. Find two different fuses in separate rooms, including clues or items connected to Uthej’s room and the second bedroom.
3. Discover a note or visual clue showing the correct breaker or valve order.
4. Find a crank or pump handle in the OG room.
5. Use the items in the basement to restore the machinery and release the gate mechanism.
6. Go to the exterior gate and operate its real release mechanism to escape.

The exact puzzle can be adapted to the implementation, but it must require multiple useful objects and exploration on multiple floors. Make the clues consistent and solvable. If the player lacks an item, show a brief hint that identifies the missing type of object without giving away the entire solution.

Include a compact inventory with clear item names and icons. Keep it hidden or small during normal gameplay so it does not clutter the screen.

# 7. Ghost, scares, sound, and horror

Create a terrifying main ghost with a distinctive silhouette, unsettling movement, and a recognizable way of searching. Add rare secondary apparitions or unexplained figures, but keep the main ghost memorable.

The ghost should react to player movement, noise, and hiding. Crouching, waiting, listening, and choosing when to move should matter. Give the player subtle cues that danger is nearby. Do not make the ghost know the player’s position everywhere or make every scare an unavoidable death.

Include:

- Sudden jump scares with varied timing and presentation.
- Suspense before some scares, not only loud sounds.
- Footsteps, breathing, knocks, wind, distant voices, and room-specific ambience.
- Ghost sounds that sometimes imitate one of the characters.
- Scares during exploration and at least one during the escape sequence.
- A setting to reduce sudden flashes. Do not use rapid strobing.
- Adjustable sound levels and subtitles.

Do not repeat one jump scare constantly. Make scares frightening but fair, with room to learn and react.

# 8. Controls and mobile experience

## PC controls

Support:

- WASD to move.
- Mouse to look.
- E to interact.
- Shift to run.
- C to crouch.
- A clear button to enter and leave hiding places.
- Esc to pause.

Provide adjustable look sensitivity and concise control hints when useful.

## Phone controls

Treat phone play as a primary version, not a small copy of the PC layout. Use a left movement stick, a right-side look area, and large reachable buttons for interact, run, crouch, and hide. Keep buttons away from screen edges and avoid covering the character or important action.

Add phone-specific options where supported:

- Adjustable joystick size and position.
- Adjustable look sensitivity.
- Optional gyroscope camera control.
- Optional vibration for danger, footsteps, interactions, and scares, with an easy setting to turn it off.
- Clear touch prompts when an object can be interacted with.
- Controls that avoid camera cutouts and system areas.
- A compact inventory that opens only when needed.
- Low, medium, and high graphics settings.
- Reliable pause and resume when the player switches apps or gets a call.

Use landscape as the main gameplay layout if needed, and adapt the interface properly to different phone screen sizes. Keep the playing screen uncluttered: show only essential prompts, short objective updates, subtitles when enabled, and minimal inventory information.

## Solo and online multiplayer

Solo mode must be complete from the introduction through the escape. Make conversations and clues work when one person is playing. The other characters can be AI companions or remain involved through believable radio and story scenes, depending on what the project can support.

If online co-op is technically supported and fits within the remaining credit budget, allow up to three players to play as Uthej, Karthik, and Ranjith. Include a working lobby or invite flow. Synchronize players, doors, item collection, puzzles, hiding, ghost behavior, and escape progress.

Do not show a multiplayer button that leads to a fake or unsynchronized mode. If a real online backend cannot be built within the budget, leave multiplayer unimplemented and clearly report that.

# 9. Performance and loading

Make the project load reliably and keep the game smooth on phones and PCs. Avoid unnecessary rendering and oversized assets. Reuse repeated objects where possible, compress and size textures appropriately, limit expensive dynamic lights and shadows, and load large scenes or video assets only when they are needed.

Provide graphics options if the project supports them. Low settings should reduce demanding visual effects without breaking controls or gameplay. Keep the visuals as detailed as the target device can handle.

Do not promise lag-free performance on every device. Report which phone or desktop viewport you actually used to check it, and state any remaining performance limits.

# 10. Final verification and report

Before finishing, verify the new project in its preview:

- It loads from a fresh launch and after refreshing.
- The player can walk up and down stairs and move between accessible floors.
- The outside area, mansion, and gate are visible and navigable.
- The two specified rooms and OG room contain the requested items and exact text.
- The bed hiding interaction works.
- Required objects can be collected and used in the escape puzzle.
- The ghost, audio, jump scares, and animated scenes trigger during gameplay.
- The final gate opens through the escape mechanism.
- PC controls work.
- Phone-sized controls are visible and usable.
- The roof is view-only and not an escape route.
- Solo play works through the main escape.

At the end, provide a short, honest report with:

- What is playable now.
- What you verified and how.
- Whether the opening, middle scene, and ending animation are implemented.
- Whether solo mode works from beginning to end.
- Whether online multiplayer is genuinely working or remains unimplemented.
- The credits used.
- Any remaining bugs, missing features, or performance limits.

Do not say the game is perfect, complete, or bug-free unless you can support that with actual verification.

Start fresh from this prompt

Builds a brand new app from the first prompt only, so later changes to the original are not included.