Design goal
Make knowledge change how the player acts, grows, and shapes the world.
Intended audience
Players who enjoy exploration, consequential choices, and character growth through discovery.
← All game studies
CONCEPT STUDY / Systems, progression & choice
Arena: Saha
Become capable because you understood the world.
Design goalMake knowledge change how the player acts, grows, and shapes the world.
01 / PROJECT SNAPSHOT
Game Concept Statement
A single-player action-adventure game set in an original world shaped by culture, conflict, and player choice, where Tariq explores, fights, builds relationships, and uses Intelligence to influence his abilities, decisions, and the unfolding story.
- Genre / mode
- Single-player action-adventure
- Stage
- Concept / design development
- Case-study focus
- Systems, progression & choice
- Available material
- Concept artwork & design document
The design challenge
How can knowledge unlock meaningful options without becoming a universal solution or a number to farm?
Player promise
Become capable because you understood the world.
02 / CORE GAMEPLAY LOOP
From action to experience.
- 01Explore
- 02Investigate
- 03Understand & choose
- 04World responds
- 05Train & prepare
- 06Face a major challenge
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.
Intelligence & learning
Discovery, evidence, and learned world rules create opportunities for training, interpretation, and access.
Rules & design considerations
Current direction
A discovered skill is an opportunity, not instant mastery; training and practice turn it into a useful ability.
What needs testing
Keep persistent knowledge distinct from any spendable resource; that economy remains an open design decision.
Relationships & consequences
Trust and disagreement change what companions share and which routes or opportunities remain available.
Rules & design considerations
Current direction
Tariq is the playable protagonist. Companions have independent goals and limits rather than simply dispensing skills.
What needs testing
Make the cause of a changed relationship understandable without reducing it to a good/evil score.
Encounters as examinations
A major encounter tests observation, preparation, movement, and learned regional rules.
Rules & design considerations
Current direction
The Archivist concept combines misleading evidence, material changes, combat, and a final consequential choice.
What needs testing
Knowledge should support a smarter approach without making a single discovery mandatory.
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
One compact Al-Madinah district, one investigation, one relationship conflict, one Intelligence interaction, contextual skill offers, and the Archivist encounter.
Planned playtest
Observe whether players use evidence to change a decision and can explain the resulting relationship or ability change.
Next design step
Build an Intelligence specification, a decision flowchart, and one encounter prototype. Record what players understood before tuning thresholds and consequences.
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.
Arena: Saha GDD
Working GDD v0.3. The statement above defines the current concept direction.