dead-air/game-planning
Watch
2
0
Fork
You've already forked game-planning
 1
Code Issues 19 Pull requests Projects Releases Packages Wiki Activity Actions

Zone/map design: connected areas, fog traversal, earned shortcuts #22

New issue
Open
opened 2026-10-18 16:11:20 +00:00 by muse-lantern · 0 comments
muse-lantern commented 2026-10-18 16:11:20 +00:00
Member
Copy link

Purpose

Design the structure of the playable zone — how areas connect, how traversal
works, and how exploration is rewarded. Individual area ideas and mechanics
go as comments below.

The ITR1 model (v2.x–2.7)

Smaller maps connected to each other, with a natural risk/reward progression:
"this area I can loot safely and get XYZ look from here, but THAT area I can
get more loot at higher risk."

Fog traversal

The areas are surrounded by fog. Walking into the fog brings you out in a
different location — potentially on the other side of the zone entirely.

Example: enter a zone, go left ten feet, walk into the fog, come out near a
path to another zone on the far side. Saves fifteen minutes of walking and
the ammo/stims you would have burned on threats along the way.

This felt earned. You discovered it by exploring, not by being told.

Diegetic hinting

The only hint of the fog mechanic in ITR1 was a note written by an old alpha
tester — written in-character as an explorer, before the feature was even
implemented. No tutorial. No UI prompt. Just a rumor from someone who was
there before you.

Design principles

  • Connected areas, not one big map. Smaller zones with clear identity.
  • Risk/reward gradient. Safe looting here, better loot at higher risk there.
  • Fog as traversal, not a wall. The boundary is a mechanic, not a barrier.
  • Shortcuts are earned through exploration. No markers, no tutorials.
  • Hints are diegetic. In-world notes, rumors, environmental storytelling.
    Never a popup that says "DID YOU KNOW YOU CAN WALK INTO THE FOG?"

Open questions

  • How does fog traversal fit our setting? (Anomaly logic — the fog IS the anomaly?)
  • Does the fog behave differently in different areas?
  • Are there risks to using the fog? (Wrong exits? Something in the fog?)
  • How does this interact with the "cannot leave" premise (#4)?
## Purpose Design the structure of the playable zone — how areas connect, how traversal works, and how exploration is rewarded. Individual area ideas and mechanics go as comments below. --- ## The ITR1 model (v2.x–2.7) Smaller maps connected to each other, with a natural risk/reward progression: "this area I can loot safely and get XYZ look from here, but THAT area I can get more loot at higher risk." ## Fog traversal The areas are surrounded by fog. Walking into the fog brings you out in a different location — potentially on the other side of the zone entirely. Example: enter a zone, go left ten feet, walk into the fog, come out near a path to another zone on the far side. Saves fifteen minutes of walking and the ammo/stims you would have burned on threats along the way. **This felt earned.** You discovered it by exploring, not by being told. ## Diegetic hinting The only hint of the fog mechanic in ITR1 was a note written by an old alpha tester — written in-character as an explorer, before the feature was even implemented. No tutorial. No UI prompt. Just a rumor from someone who was there before you. --- ## Design principles - **Connected areas, not one big map.** Smaller zones with clear identity. - **Risk/reward gradient.** Safe looting here, better loot at higher risk there. - **Fog as traversal, not a wall.** The boundary is a mechanic, not a barrier. - **Shortcuts are earned through exploration.** No markers, no tutorials. - **Hints are diegetic.** In-world notes, rumors, environmental storytelling. Never a popup that says "DID YOU KNOW YOU CAN WALK INTO THE FOG?" --- ## Open questions - How does fog traversal fit our setting? (Anomaly logic — the fog IS the anomaly?) - Does the fog behave differently in different areas? - Are there risks to using the fog? (Wrong exits? Something in the fog?) - How does this interact with the "cannot leave" premise (#4)?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
dead-air/game-planning#22
No description provided.