Chapter 14: Curiosity, Exploration, and the Pull of the Unknown

A player stands on a hill. In the distance, perhaps a kilometer away across rolling terrain, they see a tower. It is silhouetted against the sky. They cannot read what is on it. They cannot tell what surrounds it. They have no quest marker pointing them toward it. They have not been told they need to go there.

They start walking toward it.

This is the moment you are designing for. Not the combat, not the inventory management, not the cutscene that explains the lore. This — the unbidden, self-directed motion toward something the player has decided matters — is exploration. And the engine that drives it is curiosity.

This chapter is about how to build that engine. Not how to fill a world with content (you already know how to make content). How to build a world that pulls the player through it, one decision at a time, each decision feeling like it came from inside the player's own head rather than from your level designer's spreadsheet.

You will learn what curiosity actually is, in the cognitive sense. You will learn the technique of the visible-but-unreachable, which is the single most important tool in open-world design and which most designers use poorly. You will learn how environmental storytelling turns dead geometry into narrative bait. You will learn the trap of procedural generation that produces infinite content and zero curiosity. And you will learn from three games that built their entire identity on the question "what's around that corner?" — The Legend of Zelda: Breath of the Wild, Outer Wilds, and Metroid Prime.

By the end, you will add a hidden area to your prototype that the player must want to find — not because you put a marker on it, but because you made them wonder.

14.1 What Curiosity Actually Is

In 1994, the behavioral economist George Loewenstein published a paper called "The Psychology of Curiosity," and in it he proposed what is now called the information-gap theory of curiosity. The theory is short enough to state in one sentence: curiosity arises when a person becomes aware of a gap between what they know and what they want to know.

Read that again. There are two pieces here. The gap, and the awareness of the gap.

You can know nothing about plate tectonics and feel zero curiosity about plate tectonics, because you have no awareness of the gap. The moment someone tells you, "Did you know there's a fault line that runs through the middle of the United States that hasn't ruptured in two hundred years?" — now you have awareness, and now you have curiosity. The information was missing before. It was missing in exactly the same way before. What changed is that you noticed it was missing.

This is the entire foundation of exploration design. You are not creating content. You are creating awareness of missing content. A locked door is not interesting because of what is behind it — you have no idea what is behind it. The locked door is interesting because it announces, loudly, that something is behind it that you do not know.

💡 Intuition: Curiosity is not generated by hiding things. Curiosity is generated by hinting that things are hidden. A perfectly hidden secret that no player ever notices generates zero curiosity. A blatant, obvious-looking locked door generates enormous curiosity even if what's behind it is mundane.

Loewenstein's theory has another wrinkle that matters for design. The intensity of curiosity is not constant. It scales with the size of the perceived gap, but only up to a point. If the gap is too small — if the player almost knows the answer already — curiosity is weak ("I bet there's a few rupees behind that door"). If the gap is too large — if the player has no framework at all for what could be missing — curiosity is also weak, because the player cannot even formulate the question. Curiosity peaks in the middle: when the player knows enough to ask a specific question but not enough to answer it.

This middle-zone is the territory of exploration design. Your job is to give the player just enough context to formulate a question, and then to make that question feel answerable through their own movement.

14.2 The Pull of "What's Around That Corner?"

Walk down a corridor in any first-person game. The corridor turns left. You cannot see what is around the corner. You walk to the corner. You look around it.

You did this without thinking. The level designer did not put a quest marker around the corner. There was no objective text saying "Walk around the corner." You did it because the corner created an information gap, and you closed it.

This is the most primitive form of curiosity-driven motion in games, and it is operating constantly, beneath conscious awareness. Every sightline you do not have, every corner you have not turned, every door you have not opened is a small information gap. The game world is, from the player's perspective, mostly gaps. They fill them by moving.

The implication is that occlusion is not a constraint, it is a tool. The walls in your level are not there only to channel the player. They are there to create the curiosity that pulls the player around them. A level with no occlusion — a flat plane with all features visible from spawn — generates almost no curiosity. A level that is nothing but occlusion — a series of identical corridors that each reveal another corridor — generates curiosity that gradually exhausts itself, because the gaps are never filled with anything interesting.

The art is in the rhythm of revelation. You set up a gap. You let the player close it. The closing reveals — among other things — a new gap. Repeat. The player feels they are pulling themselves through the world; you are conducting them, but they cannot hear the music.

🎮 Play This: Boot up any first-person shooter from the late 90s — Half-Life, Quake II, the original Doom. Notice how almost every room has a sightline to the next room before you can enter it. A grate, a window, a partial wall. You see the next space before you reach it. You see something happening in it — a creature moving, a light flickering, a door closing. By the time you arrive, you already wanted to be there. This is the fundamental rhythm of pre-modern level design and it still works.

14.3 The Visible-but-Unreachable

In 2017, The Legend of Zelda: Breath of the Wild was released, and a generation of open-world designers finally understood a technique that had been in front of them for years.

The technique is this: you can see it, but you cannot reach it yet.

The Sheikah Towers in Breath of the Wild are tall, distinctive structures visible from miles away. Each one stands at a unique angle. Each one has a glowing tip that pulses in a way no other object in the world pulses. From any high point in the world — and the world is full of high points, because the designers placed them there for this purpose — you can see one or more towers in the distance.

You did not need to be told to climb the towers. You looked at them, you wanted to know what they were, and you walked toward them. When you got there, you climbed them. From the top, you saw more towers. The cycle restarted.

This is the visible-but-unreachable executed at the scale of an entire game world. But it operates at every scale. A treasure chest sitting on a ledge you cannot yet reach. A cave entrance halfway up a cliff. A floating platform with something glowing on it. The mountain in the distance with snow on the peak. Each of these is a contract: you can see this. The game is acknowledging that you can see it. The game is promising that you can, eventually, reach it.

The contract is the critical part. If the player suspects that the visible-but-unreachable thing is just decoration — that the cave they can see in the cliff face is a texture, not a place — they stop trusting the world, and the technique collapses. Breath of the Wild maintains the contract obsessively: virtually every distinct visual feature in the world is reachable, and reaching it produces something, however small.

⚠️ Common Pitfall: Designers love to add visible-but-unreachable elements as set dressing. A castle on a distant mountain that the player can never visit. A glowing portal in the sky that is only there for atmosphere. Players notice these. Players walk toward them. When they cannot reach them, they feel betrayed, and they begin to suspect that all of your world is set dressing. One unreachable promise can poison the credibility of a hundred reachable ones.

The visible-but-unreachable works because it stages curiosity in time. You see the thing now. You will reach it later. In between, the thing exists in your head, growing more interesting with every glance. By the time you finally arrive, you have a relationship with the place. It is not a location the game pushed at you; it is a location you decided to visit.

14.4 Sightlines: The Hidden Skill of Level Design

A sightline is a line of sight from where the player currently is to something they can see. Sightline design — the deliberate composition of what the player can and cannot see from any given position — is, in the opinion of many practitioners, the single most undervalued skill in level design.

A well-composed sightline does several things at once:

• It reveals an objective without naming it ("there's something over there").
• It establishes scale ("that thing is big and far").
• It creates an itinerary ("I will go there next").
• It rewards movement ("I can see more now than I could a moment ago").

The key tools of sightline design are elevation, framing, and silhouette.

Elevation lets you stack sightlines vertically. A player at the bottom of a valley sees only the immediate surroundings. A player on the ridge above sees the valley below and the mountains beyond and a distant tower. The reward for climbing is informational: you bought new gaps to close.

Framing uses world geometry to point the camera. A natural archway frames a distant landmark. A break in the trees reveals a glowing ruin. A gap between two buildings funnels the eye toward a horizon. The player's gaze is being directed without any UI element doing the directing.

Silhouette is what makes a distant thing legible. From a thousand meters away, the player cannot see textures or details. They see shape. A landmark with a distinctive silhouette — a leaning tower, a needle of rock, a glowing ring — registers from far away. A landmark with a generic silhouette is invisible at distance even if it is enormous.

✅ Best Practice: When you place an important location in your world, walk away from it (in-engine) and look back from every direction the player might approach. If you cannot recognize it from a kilometer away by silhouette alone, it is not a landmark. It is a place. Landmarks pull players toward them. Places merely exist when reached.

Here is a simple sightline implementation: when the player crests a hill, the camera briefly pans to point at a distant landmark, then returns to player control. This is heavy-handed (and modern games tend to avoid it), but it makes the technique explicit:

# Sightline.gd - Camera reveal of a distant point of interest
extends Area3D
class_name Sightline

@export var target_node: Node3D
@export var pan_duration: float = 1.5
@export var hold_duration: float = 0.8

var triggered: bool = false

func _ready() -> void:
    body_entered.connect(_on_body_entered)

func _on_body_entered(body: Node3D) -> void:
    if triggered or not body.is_in_group("player"):
        return
    triggered = true
    var camera: Camera3D = get_viewport().get_camera_3d()
    if camera and target_node:
        var original_basis: Basis = camera.global_transform.basis
        var look_target: Vector3 = target_node.global_position
        var tween: Tween = create_tween()
        tween.tween_method(_pan_camera.bind(camera, look_target),
            0.0, 1.0, pan_duration)
        tween.tween_interval(hold_duration)
        tween.tween_method(_restore_camera.bind(camera, original_basis),
            0.0, 1.0, pan_duration)

func _pan_camera(t: float, camera: Camera3D, target: Vector3) -> void:
    var current: Vector3 = camera.global_position
    camera.look_at(current.lerp(target, t), Vector3.UP)

func _restore_camera(t: float, camera: Camera3D, basis: Basis) -> void:
    camera.global_transform.basis = camera.global_transform.basis.slerp(basis, t)

In a finished game you would hand control back to the player smoothly, fade in/out the cinematic bars, and only trigger this on first crest. But the underlying idea is the same: at certain moments, your level briefly takes control of the player's gaze and points it at something. You are buying their curiosity in advance for a place they have not yet decided to visit.

🎯 Tradeoff Spotlight: Forced camera pans are intrusive but reliable. They guarantee the player sees the landmark. Subtle environmental framing — letting world geometry do the pointing — is invisible but unreliable. Some players will miss it. The right choice depends on how essential the landmark is. Critical to progression? Force the pan. Optional but rewarding? Let geometry do the work. Easter egg? Hide it entirely and let the curious players find it.

14.5 Locked Doors and the Promise of the Unknown

A locked door is an information gap with a key.

The locked door is one of the oldest design elements in games and one of the most reliable. Adventure on the Atari 2600 had locked doors. The Legend of Zelda in 1986 had locked doors. Every dungeon-crawler in the four decades since has had locked doors. The reason is simple: a locked door does exactly what curiosity design requires. It announces the presence of a hidden space, it makes the player aware of the gap, and it gives them a goal that, when accomplished, will close the gap.

Notice what the locked door does not do: it does not require the player to want what is inside. The chest behind the door might contain rupees, or a sword, or a piece of plot, or nothing at all. The motivation to open the door is not generated by the content on the other side — the player does not know what is on the other side. The motivation is generated by the fact of the door itself.

This is a profound insight that newer designers often miss. You do not need to make the reward exciting in order to motivate the player to seek it. The seeking is its own reward, generated by the gap. Once the player is seeking, you have a window — they will keep looking even if intermediate rewards are modest, because the act of looking is producing the dopamine, not the loot.

This is also why "treasure chest fatigue" is real and dangerous. If every chest in your game contains rupees, players still seek them out for a while, because the chest-as-information-gap functions even when the chest-as-reward is boring. But eventually the player learns: the gap is fake. The chest does not contain new information; it contains a number that goes up. At that point, the chests stop pulling. The locked doors stop pulling. Curiosity collapses.

💀 Design Autopsy: Assassin's Creed Unity (2014) populated its open-world Paris with hundreds of collectible chests. Many of them required side activities to open. Some of them required external app integration. Most of them contained generic gold or generic crafting materials. The design used the form of curiosity-design — chests, locks, gaps — without honoring the underlying function. Players began to ignore the chests, then the side activities, then significant portions of the world. The world had become noise. The lesson: the curiosity contract requires informational payoff, not just numerical payoff. A small piece of lore, a unique trinket with a story, a glimpse of a new mechanic — these honor the contract. A repeat of the last fifty rewards does not.

14.6 Environmental Storytelling: Curiosity Without Cutscenes

There is a room. The door is broken inward. A chair is tipped over. A bowl of food sits on the table, half-eaten. Dried blood on the floor leads toward the back door, which is open. A child's toy lies in the doorway.

You have just been told a story. No one spoke. No cutscene played. No quest log updated. The world told you the story by being arranged in a particular way, and your mind — pattern-matching, gap-filling — assembled the narrative.

This is environmental storytelling, and it is one of the most powerful techniques in the curiosity toolkit, because it weaponizes the player's own cognition. You are not telling them the story; you are providing the evidence and letting them tell themselves the story. The story they construct is more vivid than any story you could have told them, because it is theirs.

🚪 Threshold Concept: Environmental storytelling is not "decoration that happens to suggest narrative." It is the deliberate authoring of evidence in physical space such that the player can reconstruct events that occurred before they arrived. The skill is curatorial: you choose what evidence to leave behind and what to omit. Too much and the story becomes obvious (and boring). Too little and the player sees random props (and ignores them). The sweet spot is just enough evidence to formulate a question, not enough to answer it.

This is information-gap theory applied to narrative. The half-eaten bowl creates the gap: who was eating this and why did they stop? The trail of blood creates a hypothesis: they were attacked or hurt. The child's toy creates a complication: there was a child here too — what happened to them? The player's mind runs ahead of the evidence, generating possibilities, and they are pulled forward through the world looking for more evidence to confirm or refute their hypotheses.

The Last of Us uses this constantly. Bioshock built its entire narrative method on it. Dark Souls tells most of its lore through environmental arrangement and item descriptions, refusing almost entirely to have characters explain anything. Half-Life 2 tells you about the history of City 17 by letting you walk through the train station.

The technique has rules:

• Each scene should suggest a single primary event. Multiple overlapping stories in one room produce noise, not narrative.
• Evidence should be readable in any order. The player will not enter from the door you imagined. Make sure the story decodes from any approach.
• The interesting question should be implied, not stated. A note that says "I think the child escaped through the back" tells you the answer. The toy in the doorway implies a question and lets you answer it.
• Resist the temptation to confirm. Players who reconstruct a narrative that turns out to be wrong feel cheated. But players who reconstruct a narrative that is never confirmed or denied feel they have a personal interpretation. Ambiguity is a feature.

🔗 Connection: Environmental storytelling depends heavily on the affordance design from Chapter 9 and the visual hierarchy from Chapter 10. The chair must read as a chair. The blood must read as blood. The toy must read as a child's toy. If your player cannot identify the elements, the narrative cannot assemble. Storytelling through environment requires excellent readability of the environment itself.

14.7 The Exploration-Exploitation Tradeoff

In machine learning and operations research, there is a concept called the exploration-exploitation tradeoff. It comes up whenever an agent must decide between using what it already knows works (exploitation) and trying something new in case it works better (exploration).

This concept maps almost perfectly onto open-world game design.

A player in your world has accumulated knowledge: they know there is a town to the east where they can sell goods, a forest to the west where they can farm enemies, a quest in the south they have not finished. At any given moment, they must choose between exploiting (going to the town, finishing the quest, farming the forest — known returns) and exploring (heading north into territory they have never seen, where unknown things might be).

If your game tilts too far toward exploitation, the player will optimize. They will grind the known returns. They will stop exploring because exploration is risky and the known returns are reliable. Your beautiful open world becomes a series of efficient routes between known nodes. The world is dead.

If your game tilts too far toward exploration, the player feels they are wandering aimlessly. Nothing they do has lasting value because they keep finding new things and abandoning the old. Your beautiful open world becomes a wash of half-engaged surfaces.

The tilt mechanism is in your hands. Some levers:

• Diminishing returns on exploitation. The forest becomes less rewarding the more you farm it. The quest, once completed, does not regenerate. The town has nothing new to sell after a while. This pushes the player toward exploration.
• Compounding rewards from exploration. Discovering a new region unlocks a new resource, a new shop, a new quest line. Exploration is not just "see new place" — it is "expand the set of things you can do."
• Visible long-tail rewards. The visible-but-unreachable (Section 14.3) is partly an exploration motivator: it signals "there are returns out here you have not yet collected."
• Penalty-free exploration. If exploration is dangerous in ways that wipe out exploitation gains (death penalties, stamina exhaustion), players will exploit. If exploration is cheap (fast travel, low penalty for death, abundant resources), they will explore.

🧩 Productive Struggle: Pick an open-world game you have played extensively. Recall the last 30 minutes of play before you stopped. How much of that time did you spend exploiting (visiting known places, doing known activities) versus exploring (going somewhere new)? Which one was the game's economy pushing you toward? Did the design you experienced match the design the game was clearly trying to encourage? If it did not, where was the gap?

14.8 Procedural Generation and the Curiosity Trap

If curiosity is generated by gaps, and a procedural generator can create infinite gaps, then a procedural generator can create infinite curiosity.

This is what No Man's Sky promised in 2016. Eighteen quintillion planets, each procedurally generated with unique terrain, flora, and fauna. The promise was that the curiosity engine would never run out of fuel.

It did. Almost immediately. And the failure illustrates something important about how curiosity actually works.

Procedural generation produces variety, but variety is not the same as novelty, and novelty is not the same as meaning. A procedural planet with red rocks instead of blue rocks and four-legged creatures instead of three-legged creatures is technically different from the previous planet, but the player's mind, after the first dozen planets, stops registering the differences. The gaps the procedural generator is producing are not gaps the player cares about closing.

What went wrong, in information-gap terms? The gaps were too small. The player already knew, after planet five, what a planet would contain: terrain, plants, animals, resource nodes, points of interest, occasional structures. The novel information on planet six was a small permutation of variables within a known schema. The gap was the size of "what color will the rocks be?" — and curiosity does not fire for gaps that small.

Compare this to a hand-designed world. Dark Souls' Lordran is much smaller than a single No Man's Sky planet. But every region in Lordran contains things you have not seen before — new enemy types, new architectures, new mysteries, new tonal shifts. The gaps are large because the human designer chose them to be large.

⚠️ Common Pitfall: Procedural generation does not solve the content problem. It scales it. If your hand-designed content is dull, procedurally generating more of it produces vast quantities of dull content. If your hand-designed content is rich, procedural variation can extend it — but the variation must be on dimensions the player cares about, not just the dimensions easiest for the algorithm to vary.

The games that have succeeded with procedural exploration tend to combine procedural variation with hand-authored grammars. Spelunky generates levels procedurally, but the building blocks are hand-designed and the rules of combination produce reliably interesting situations. Hades uses procedural room ordering to keep runs varied while every room itself is hand-designed. Minecraft's procedural world is dull on a moment-to-moment basis but interesting because the player brings the meaning (they decide where to build, what to mine, what to seek). The algorithm here provides raw material; meaning comes from elsewhere.

The honest lesson is: if you are betting your game on procedural generation as the curiosity engine, you are probably going to lose that bet. Procedural systems can support curiosity (by removing repetition, by enabling emergent situations) but they rarely generate it on their own. The gaps the player cares about are usually authored.

14.9 Gated Exploration: The Metroidvania Pattern

In 1986, Metroid did something that would become an entire subgenre. It built a single connected world — not a series of separated levels — and locked off most of it. The player could see passages they could not enter, ledges they could not reach, doors they could not open. As they progressed, they acquired abilities (the morph ball, the bombs, the high jump, the wave beam) and the previously inaccessible areas opened up.

This pattern, now called the Metroidvania structure (after Metroid and Castlevania: Symphony of the Night), is one of the most curiosity-dense designs ever invented. Why? Because it weaponizes memory.

When you enter a room early in Super Metroid and notice a high ledge you cannot reach, the game is not just creating an information gap. It is creating an information gap that you will carry with you for hours. You will remember that ledge. You will think about it occasionally. You will, eventually, get the high jump boots. The moment you get them, you know exactly where to go. You retrace your steps to that ledge. You jump up. The room reveals its secret.

This is one of the most profound rewards a game can deliver: a payoff to a question you asked yourself hours ago. It feels like the game knew you would remember. It feels like the world has been waiting for you. It is, in fact, the player's own pattern recognition closing a loop they themselves opened.

📐 Project Checkpoint: Look at your prototype. Pick three locations where the player will currently pass through, and ask yourself: is there a visible-but-currently-unreachable element here? An obvious ledge they cannot yet jump to, a door they cannot yet open, a passage blocked by something they cannot yet remove? If not, can you add one? You do not need to give them the ability to overcome it in this chapter — adding the gap now and resolving it later is the whole technique. The gap will sit in the player's mind, working for you, even when they are not on screen.

The Metroidvania structure also illustrates a subtle point about progression design. The new ability is not the reward. The new ability is the key — the reward is the ability to go back and answer questions you had forgotten you were asking. This means abilities should always unlock previous curiosity, not just new content. An ability that only matters going forward is mechanically useful but does not create the Metroidvania feeling. An ability that opens dozens of doors you remember from earlier creates a flood of revelation that is one of the genre's signature pleasures.

14.10 The "Notice → Approach → Discover → Understand" Loop

Underneath all of these techniques is a single repeated cognitive loop. It is worth naming it explicitly:

1. Notice. The player perceives that something exists. A glow on the horizon, a strange shape in the wall, a sound from beyond a hill. The information gap opens.
2. Approach. The player moves toward the thing. This is where most exploration time is spent. The approach is itself part of the experience — the building anticipation, the gradual reveal as the thing becomes more visible.
3. Discover. The player arrives. The thing is now in front of them. It is identifiable. The first phase of the gap closes: what is it? is answered.
4. Understand. The player figures out what the thing means. How does it work? What is its place in the world? How does it connect to other things? This is the deeper closure: what does it imply? is answered.

If you can identify each of these four phases for every exploration target in your game, you can debug your curiosity design. Failing exploration usually fails at one of these specific points:

• Notice failure. The player walks past the thing without registering it. The visual call-out was insufficient. Your sightline was wrong, your silhouette was wrong, your lighting did not draw the eye.
• Approach failure. The player notices but does not bother to approach. The cost-to-payoff ratio felt wrong, or there was no clear path, or the approach itself was tedious.
• Discover failure. The player arrives but cannot tell what they have found. The thing is not legible at close range. It looks like more terrain.
• Understand failure. The player discovers but does not grasp the meaning. The thing exists, but it does not connect to anything they care about. It is just a thing.

🪞 Learning Check-In: Pick one piece of "discoverable content" in your prototype — a hidden item, a side area, a piece of environmental storytelling. Walk through the four phases for it. Where does a hypothetical first-time player most likely fail? If you are not sure, that is a sign that you have not designed the exploration consciously. The fix is usually small: a better silhouette, a clearer approach, a more legible reveal, a meaningful connection.

14.11 Hidden Areas and Secrets as Currency

Secrets are exploration's purest currency. A secret is an area, item, or piece of content that the game does not announce, does not mark on the map, does not require for completion, and does not draw attention to. It exists for the curious to find.

The economics of secrets are interesting. A secret has value to the player in inverse proportion to its visibility. A secret that the game points at with a glowing arrow is not really a secret — it is a side-quest. A secret that the game hides so well that no player ever finds it is wasted content. The sweet spot is in between: the secret is hidden, but there is just enough hint that an attentive player can notice the gap.

The hint can be:

• Visual. A patch of wall that is slightly different from the surrounding wall (a different texture, a different shade, a slight crack).
• Auditory. A faint sound coming from a wall that should not have anything behind it.
• Behavioral. An NPC who looks toward a particular direction every time you enter the room. A bird that always lands at a particular spot.
• Structural. A geometry pattern that breaks the convention of the rest of the level. A symmetrical room with one asymmetric element.

Here is a simple secret-area implementation: a destructible wall that can be broken to reveal a hidden chamber, with a subtle visual tell that distinguishes it from the surrounding wall:

# SecretArea.gd - Hidden area behind a destructible wall with a visual tell
extends StaticBody3D
class_name SecretArea

@export var hit_points: int = 1
@export var reveal_emission: float = 0.15
@export var hidden_loot_scene: PackedScene
@export var hidden_loot_position: Vector3 = Vector3.ZERO

@onready var mesh: MeshInstance3D = $MeshInstance3D
var revealed: bool = false

func _ready() -> void:
    # Subtle emission tells the curious player something is different here
    var mat: StandardMaterial3D = mesh.get_active_material(0).duplicate()
    mat.emission_enabled = true
    mat.emission = Color(0.4, 0.3, 0.2)
    mat.emission_energy_multiplier = reveal_emission
    mesh.set_surface_override_material(0, mat)
    add_to_group("destructible")

func damage(amount: int) -> void:
    hit_points -= amount
    if hit_points <= 0 and not revealed:
        _reveal()

func _reveal() -> void:
    revealed = true
    if hidden_loot_scene:
        var loot: Node3D = hidden_loot_scene.instantiate()
        get_parent().add_child(loot)
        loot.global_position = global_position + hidden_loot_position
    queue_free()

The reveal_emission value here is critical. Set it too high and every player sees the wall is different — it stops being a secret. Set it to zero and no player ever notices — it stops being findable. The default 0.15 is a starting point; you will need to tune it against your level's lighting.

🎓 Advanced: The best secrets in the medium are not just hidden things you find. They are hidden things that recontextualize what you already saw. Fez hides a second writing system that, once decoded, reveals that text you have been seeing throughout the game has been spelling out clues. The Witness hides environmental puzzles that, once you learn to see them, change how you look at every previous area. These secrets convert the entire game into a different game. They are the most powerful possible reward for curiosity, because they retroactively rewrite the experience.

14.12 Landmark-Based Navigation

Ask a player who has finished an open-world game how they got from one place to another, and they will probably not say "I went 230 meters east-southeast." They will say "I went past the broken bridge, then up the hill with the dead tree, then I cut left at the lighthouse."

Players navigate by landmarks. Always. This is not a quirk of gamers — it is how human spatial cognition works. We do not store coordinates; we store relationships between distinctive features.

The implication for design is that your world's navigability is a function of its landmark density and landmark distinctiveness. A world full of generic terrain is unnavigable even if it is small. A world with a strong skyline of distinct features is navigable even if it is huge.

Breath of the Wild is, geographically, larger than most open-world games of its era, and yet players consistently report being able to find their way around it. The reason is that every region has multiple distinctive landmarks. Mount Hylia is a snow-capped peak with a specific shape. Death Mountain is an active volcano with a glowing top. Hyrule Castle dominates the central plateau. The Sheikah Towers stand at distinct angles in each region, like signatures. From anywhere in the world, you can see at least two or three distinct landmarks, and they triangulate your position.

⚡ Quick Reference: Three rules for landmark design: 1. Distinctive silhouette. It must be readable from far away by shape alone. 2. Visible from multiple angles. A landmark only visible from one direction is half a landmark. 3. Memorable name or association. Players will refer to it. Make sure they have a way to refer to it that is shorter than its description.

This last rule is subtle but important. If your landmark requires the player to say "the tower with the kind of curved roof, you know, the one to the east of the swamp," they will not refer to it. They will refer to "the curved tower" if it is the only curved tower in the region, or "Watcher's Spire" if you named it. The shorter the reference, the more often it gets used, the more central it becomes to the player's mental map.

14.13 Three Games That Built Themselves on Curiosity

Three short studies. Each takes the principles of this chapter further than most designers would think possible.

Outer Wilds (2019) is, structurally, a game with no progression mechanics. You do not gain abilities. You do not level up. You do not collect equipment. The only thing you gain is knowledge. And the only mechanic that exists in the game is applying that knowledge to figure out what to do next. It is curiosity as the entire game. There is a moment, deep in the game, where you realize that something you saw and dismissed in the first ten minutes was actually the key to a major mystery. The realization is purely informational — nothing in your character has changed. But the meaning of the world has changed completely, because you can now see what you were always looking at.

Breath of the Wild (2017) treats the entire world as a single curiosity-generation engine. The Sheikah Towers, the shrines, the koroks, the unmarked points of interest — all of these exist to give the player a near-constant stream of "I see a thing → I will go to the thing." The case study at the end of this chapter goes deeper. For now: Breath of the Wild is what happens when a designer takes the visible-but-unreachable principle and applies it everywhere, ruthlessly, at every scale.

Metroid Prime (2002) added a single mechanic — the scan visor — that turned the entire world into an investigation. Almost every object in the game can be scanned, and scanning reveals lore, mechanical hints, or biological information. The game thus rewards the player for stopping and looking at things, which is exactly what most games discourage. The result is one of the most narratively rich game worlds of the early 2000s, told almost entirely through environmental detail. The case study covers this in depth.

🔄 Check Your Understanding: What do these three games have in common, mechanically? They differ in genre (puzzle, action-adventure, FPS), in setting, in tone. But they share a core design principle. Take a minute and try to articulate it in one sentence before reading on.

The principle: the act of noticing and investigating is itself the reward. None of these games punishes you for stopping to look. None of them puts a quest marker on the thing you should investigate. All of them assume the player will be intrinsically motivated to explore and reward that motivation directly. They trust the player's curiosity as the engine of play.

14.14 Rewarding Curiosity Without Punishing It

A final principle, which is easy to state and hard to live up to: reward the curious player, but do not punish the player who is not curious.

This sounds obvious. It is violated constantly. A side area requires a thirty-minute detour and contains an item the player needs for the main quest — they were punished for not exploring. A boss is much harder if you missed an optional power-up two regions back — they were punished for not exploring. A late-game door requires a key found in an area you had no reason to revisit — they were punished for not exploring.

In each case, the designer thought they were rewarding the curious player. They were not. They were requiring exploration and disguising it as optional. The player who chose to focus on the main path was retroactively punished for that choice. They will, next time, explore everything obsessively, because they cannot trust the game to label optional content as truly optional.

The right pattern is: optional content is genuinely optional. It contains things that make the curious player's experience richer, but never things that the non-curious player needs to succeed. The richness is the reward. Skipping it is a real choice, not a mistake.

This trust matters because curiosity is fragile. A player who feels they are being punished for not exploring stops trusting the world. A player who trusts the world will explore more, because they know that exploration is genuinely a choice and that choices are honored.

📝 Note: This principle has a corollary for difficulty. If exploration produces power increases (better weapons, more stats, additional abilities), then the game's difficulty curve must be tuned for the non-exploring player. The exploring player will be over-leveled, which is fine — that is their reward for exploring. The non-exploring player should still be able to win. If your game can only be beaten by players who collected 80% of optional power-ups, you have built optional content that is actually mandatory, and you have lied to your player about the choice you offered them.

14.15 Putting It Together: Add Curiosity to Your Prototype

Two additions to your prototype this chapter:

A hidden area accessible through curiosity. Choose a location in your prototype. Add a destructible wall using the SecretArea.gd pattern above. Tune the reveal_emission so that an attentive player can notice the wall is different but a casual player will pass it by. Behind the wall, place something small but meaningful — a piece of unique loot, a glimpse of the next area, a piece of environmental storytelling. The reward should honor the curiosity: it should not be more of what the player already has, but something new the player has not seen.

A sightline pulling the player forward. Choose a transition point in your level — a place where the player crests a hill, exits a building, or rounds a corner. At that moment, a distant landmark should be visible. Use the Sightline.gd pattern above (or a more subtle version) to ensure the player notices it. The landmark should be a place the player will eventually visit, not just decoration. The contract is: you see it now, you will reach it later. Honor it.

When you test, watch a player who has not seen the prototype before. Do they notice the secret wall? Do they walk toward the distant landmark without prompting? If yes, your curiosity design is working. If no — if they walk past the wall without registering it, or if they crest the hill and turn the other way — your design is not working yet, and you have something specific to fix.

You started this chapter with a player on a hill, looking at a tower they had not been told to visit. You should now understand why they walk toward it. It is not because the tower is interesting. It is because the tower has announced its existence in a way that creates an information gap, and the human mind, faced with an information gap, moves to close it.

Your job, as a designer, is to keep announcing existences. To keep promising and delivering. To trust the player to be curious and to honor that curiosity with discoveries that reward the trust. Get this right, and your players will explore your world with the conviction that every step was their idea. They will not realize you were guiding them. They will only realize they could not stop walking forward, and they did not want to.