Escape Room Brief Command Center

Core Game Scope

• Single-player 3D escape room demo
• Conventions of a real-world escape room
• Average run fits 5 to 10 minutes

Input and Access

• Keyboard and mouse support
• Gamepad support
• Subtitles and colour vision options

UX and Presentation

• Main menu with accessibility options
• Pause menu with resume and quit
• At least one cutscene, plus audio and animation

Strategic Direction

• Anchor the entire experience around science-led time travel, with the theme obvious from the opening scene to the final objective.
• Prioritize originality over generic room concepts; the client explicitly requested something distinctive and memorable.
• Treat title and room naming as a conversion lever, since customers often book on concept strength before reading full descriptions.
• Use props, scenery, and environmental storytelling to keep puzzle logic grounded in the world, not detached from it.

Puzzle Experience Standards

• Default to a clear linear flow for readability and pacing, with optional controlled branching only where it improves engagement.
• Do not use red herrings or puzzles requiring specialist outside knowledge; each step must be readable in-context.
• Avoid long, repetitive, or tedious interactions; puzzle variety and tempo control are critical to sustained player focus.
• Keep progression signposted with clear goals, visible interactables, and environmental blocking for non-playable areas.

Time Allocation

• 15 in-class hours each week (120 total)
• 6 independent-study hours each week (48 total)
• Plan fixed weekly review points to evidence AC2 process
• Leave export/package time before final submission

Risk control: lock “must-have” features first (controls, accessibility, menus), then puzzle polish.

Pre-Production Doc

.docx, submitted on Pod for the pre-production checkpoint.

Production Doc

.docx, includes implementation evidence and post-production reflection.

Packaged Build

.exe demo, fully functional and testable by assessor/client.

Project + Assets

UE5 .zip and raw asset files (models, textures, UI, audio, etc.).

What the Brief Is Really Asking For

• Create a focused single-player 3D escape room experience with a complete gameplay loop and clear objective.
• Deliver a polished demo that respects real-world escape room conventions while using digital strengths where useful.
• Keep scope disciplined so the core experience is stable, accessible, and playable within the intended runtime.
• Show that design, technical implementation, and documentation are connected into one coherent production process.

What Each Guidance Section Expects

• Investigation: evidence-based interpretation of the brief plus primary, secondary, market, and accessibility research that informs decisions.
• Idea Generation: multiple viable concepts, recorded team decision-making, and clear rationale for selected direction.
• Role Deliverables: artist work must prove visual language and environment planning; programmer work must prove interaction and system planning.
• Shared Team Evidence: treatment, Trello/process tracking, and contribution clarity must demonstrate professional collaboration.

How the Work Is Judged Across AC1-AC5

• AC1: quality of research and how directly it informs concept and scope decisions.
• AC2: visible problem-solving process through iteration, testing, review, and refinement.
• AC3: technical execution quality, control reliability, and production consistency.
• AC4/AC5: professionalism, planning discipline, and communication clarity in documents and presentation.