Design goal
Make understanding and manipulating hidden systems feel like an adventure.
Intended audience
Players drawn to environmental puzzles, exploration, and mysteries solved through experimentation.
← All game studies
CONCEPT STUDY / Technical abilities & environmental puzzles
RE:FRAME
Understand a world that appears impossible, then learn how to influence it.
Design goalMake understanding and manipulating hidden systems feel like an adventure.
01 / PROJECT SNAPSHOT
Game Concept Statement
A single-player third-person action-adventure where Ahmed is pulled into a mysterious world connected to the FRAME experiment and uses technical abilities such as Inspect, Debug, Rewire, Simulate, and Rebuild to explore, traverse, solve environmental puzzles, and uncover the world's true nature.
- Genre / mode
- Single-player third-person action-adventure
- Stage
- Concept / design development
- Case-study focus
- Technical abilities & environmental puzzles
- Available material
- Concept artwork & design document
The design challenge
How can technical abilities become readable physical interactions without requiring technical vocabulary?
Player promise
Understand a world that appears impossible, then learn how to influence it.
02 / CORE GAMEPLAY LOOP
From action to experience.
- 01Arrive & explore
- 02Observe a problem
- 03Inspect hidden relationships
- 04Experiment with a tool
- 05Change the environment
- 06Discover a clue or route
Concept loop: the next challenge returns the player to observation and a new decision.
03 / SYSTEM DESIGN
What creates the experience.
Design intent and rules to validate in a prototype.
Inspect & diagnose
Reveal hidden traces and relationships so players can form a hypothesis about an obstacle.
Rules & design considerations
Current direction
The first glasses interaction exposes a connection that can open a route. Diagnosis supports the current Debug concept.
What needs testing
The reveal should clarify a problem without automatically giving away its solution.
Rewire & experiment
Change a relationship between world elements to alter a route or encounter.
Rules & design considerations
Current direction
The GDD proposes connections such as door/control, light/source, and machine/target. Exact interaction rules need a prototype.
What needs testing
Communicate valid targets, invalid actions, and resulting world changes clearly.
Earned tools & transformation
Expand what Ahmed can understand and influence through equipment earned during the journey.
Rules & design considerations
Current direction
Glasses precede the glove, pack, and drone. Simulate influences phenomena; Rebuild is reserved for major transformations.
What needs testing
Introduce abilities gradually so later tools deepen exploration rather than overwhelm it.
04 / VISUAL DIRECTION
Inside the world.
Concept visuals communicate the intended experience; they are not evidence of a finished playable build.
05 / DEVELOPMENT & VALIDATION
The next playable question.
First prototype target
A planned 10–15 minute slice: Ahmed’s room, the FRAME anomaly, arrival, the workshop, glasses discovery, one Inspect interaction, and a small encounter.
Planned playtest
Observe whether a player can explain the first puzzle without Technical Art terminology and still enjoys exploration before acquiring the glasses.
Next design step
Build one greybox puzzle, document its interaction states, and capture a before-and-after playtest revision. The current concept adds Debug; the attached earlier GDD also explores Shader Shift and Optimize.
Evidence & iteration status
This case study currently presents concept design and visual material. Playable builds, implementation breakdowns, and measured playtest revisions are not yet included.
06 / DESIGN DOCUMENTATION
Explore the full design.
RE:FRAME GDD
GDD v0.1 / earlier ability exploration. The statement above defines the current concept direction.