---
id: stealth-infiltration
status: active
supersededBy: []
lang: en
title: 'Stealth, infiltration and escape'
description: >-
  Stealth manages what observers know through visibility, suspicion, traces,
  decoys and escape routes.
intro: >-
  Stealth manages what observers know through visibility, suspicion, traces,
  decoys and escape routes. Each overview separates player actions, state
  changes and alternative rules. Examples are hypothetical design scenarios, not
  claims about a named game. A prototype check states an observable question for
  the next iteration. Existing detailed references remain separately linked from
  the direction map.
updatedAt: '2026-10-21'
sources:
  - title: 'Robert Nystrom: State'
    url: >-
      https://github.com/munificent/game-programming-patterns/blob/master/book/state.markdown
    description: >-
      The author’s original discussion of states and transitions; rule
      implementation context, not evidence for every editorial variant.
counts:
  families: 8
  branches: 8
  variants: 32
url: 'https://gamemechanics.pro/en/mechanics/stealth-infiltration/'
markdownUrl: 'https://gamemechanics.pro/content/mechanics/en/stealth-infiltration.md'
license: CC-BY-4.0
codeLicense: MIT
attribution: gamemechanics.pro contributors
provenance: >-
  Original bilingual editorial overviews authored for gamemechanics.pro on
  2026-10-20 and reviewed on 2026-10-21. Scenarios are hypothetical design
  examples; prototype checks describe work to perform, not completed playtests.
  Primary sources support the stated techniques and implementation context, not
  every proposed variant.
---
# Stealth, infiltration and escape

Stealth manages what observers know through visibility, suspicion, traces, decoys and escape routes. Each overview separates player actions, state changes and alternative rules. Examples are hypothetical design scenarios, not claims about a named game. A prototype check states an observable question for the next iteration. Existing detailed references remain separately linked from the direction map.

## Mechanics and variants

<a id="mechanics"></a>

### 1. Visibility, noise and detection

<a id="t031"></a>
id: t031
canonicalId: stealth-infiltration--t031
url: https://gamemechanics.pro/en/mechanics/stealth-infiltration/#t031

Detection depends on observable signals, obstacles and observer attention, letting players manage the visibility of their actions.

#### Mechanic variants

<a id="t031-variants"></a>
- Light increases silhouette visibility. <a id="t031-v1"></a>
- Noise propagation accounts for obstacles. <a id="t031-v2"></a>
- Movement speed changes footstep loudness. <a id="t031-v3"></a>
- Brief contacts accumulate detection progress. <a id="t031-v4"></a>

Design example: The player runs while an industrial press masks the sound of footsteps.

Prototype check: Test detection near an obstacle edge and show which signal the observer actually noticed.

- [Robert Nystrom: State](https://github.com/munificent/game-programming-patterns/blob/master/book/state.markdown)

### 2. Suspicion, alerts and searching

<a id="t032"></a>
id: t032
canonicalId: stealth-infiltration--t032
url: https://gamemechanics.pro/en/mechanics/stealth-infiltration/#t032

Suspicion moves observers from routine behavior through investigation, alerts and searching for a last known target.

#### Mechanic variants

<a id="t032-variants"></a>
- Investigation approaches an unusual signal source. <a id="t032-v1"></a>
- Alerts spread through available communication channels. <a id="t032-v2"></a>
- Search expands from the last known contact. <a id="t032-v3"></a>
- Returning to routine preserves memory of a threat. <a id="t032-v4"></a>

Design example: A guard investigates an open door, calls a partner and then searches nearby rooms.

Prototype check: Test that a searching guard cannot obtain the hidden player's exact position without observing a new signal.

- [Robert Nystrom: State](https://github.com/munificent/game-programming-patterns/blob/master/book/state.markdown)

### 3. Hiding bodies and traces

<a id="t033"></a>
id: t033
canonicalId: stealth-infiltration--t033
url: https://gamemechanics.pro/en/mechanics/stealth-infiltration/#t033

Hiding bodies and traces delays discovery of an action but costs time and can create new vulnerabilities.

#### Mechanic variants

<a id="t033-variants"></a>
- Carrying slows movement and occupies the hands. <a id="t033-v1"></a>
- Containers limit the number of hidden objects. <a id="t033-v2"></a>
- Cleaning removes a specific type of trace. <a id="t033-v3"></a>
- A missing character can itself trigger investigation. <a id="t033-v4"></a>

Design example: A guard is concealed, but a missed patrol check prompts a dispatcher to send a replacement.

Prototype check: Test trace persistence across room changes and distinguish hiding a body from removing evidence.

- [Robert Nystrom: State](https://github.com/munificent/game-programming-patterns/blob/master/book/state.markdown)

### 4. Disguises and social infiltration

<a id="t034"></a>
id: t034
canonicalId: stealth-infiltration--t034
url: https://gamemechanics.pro/en/mechanics/stealth-infiltration/#t034

Social infiltration uses an expected role instead of invisibility: access depends on clothing, behavior and recognition.

#### Mechanic variants

<a id="t034-variants"></a>
- A uniform opens areas for a specific profession. <a id="t034-v1"></a>
- An insider recognizes strangers within their group. <a id="t034-v2"></a>
- Forbidden actions undermine the assumed role. <a id="t034-v3"></a>
- Documents confirm access during an inspection. <a id="t034-v4"></a>

Design example: A technician's uniform permits entry, but touching a safe attracts the attendant's suspicion.

Prototype check: Test that access boundaries are visible before a violation and recognition has an identifiable observer.

- [Robert Nystrom: State](https://github.com/munificent/game-programming-patterns/blob/master/book/state.markdown)

### 5. Lures, distractions and sabotage

<a id="t035"></a>
id: t035
canonicalId: stealth-infiltration--t035
url: https://gamemechanics.pro/en/mechanics/stealth-infiltration/#t035

Distraction changes observer priorities while sabotage changes the environment to prepare a later covert action.

#### Mechanic variants

<a id="t035-variants"></a>
- Sound redirects the nearest available observer. <a id="t035-v1"></a>
- A lure requires a relevant target motivation. <a id="t035-v2"></a>
- A breakdown summons maintenance personnel. <a id="t035-v3"></a>
- A false alarm frees a different area. <a id="t035-v4"></a>

Design example: A disabled pump makes a technician leave their post and open a service corridor.

Prototype check: Test repeated distractions: reactions should account for a known trick or explicitly allow repetition.

- [Robert Nystrom: State](https://github.com/munificent/game-programming-patterns/blob/master/book/state.markdown)

### 6. Tailing, reconnaissance and counter-surveillance

<a id="t036"></a>
id: t036
canonicalId: stealth-infiltration--t036
url: https://gamemechanics.pro/en/mechanics/stealth-infiltration/#t036

Tailing maintains contact, reconnaissance learns routines and counter-surveillance checks whether the observer has been exposed.

#### Mechanic variants

<a id="t036-variants"></a>
- Distance balances losing a target against recognition. <a id="t036-v1"></a>
- Routes use several observation positions. <a id="t036-v2"></a>
- Photographs preserve a verifiable target action. <a id="t036-v3"></a>
- A checking turn reveals a follower copying the route. <a id="t036-v4"></a>

Design example: A courier changes streets and the player switches to a distant camera instead of closing dangerously.

Prototype check: Test regaining contact through a known route after a brief interruption of direct visibility.

- [Robert Nystrom: State](https://github.com/munificent/game-programming-patterns/blob/master/book/state.markdown)

### 7. Heists and coordinated infiltration

<a id="t037"></a>
id: t037
canonicalId: stealth-infiltration--t037
url: https://gamemechanics.pro/en/mechanics/stealth-infiltration/#t037

Coordinated infiltration assigns dependent actions to roles and synchronizes them within a limited access window.

#### Mechanic variants

<a id="t037-variants"></a>
- Reconnaissance unlocks operation preparations. <a id="t037-v1"></a>
- Synchronized orders combine several actions. <a id="t037-v2"></a>
- A fallback plan changes routes after an alert. <a id="t037-v3"></a>
- Loot slows the team's final escape. <a id="t037-v4"></a>

Design example: One participant cuts power, another opens a gate and a third moves cargo to a vehicle.

Prototype check: Test one failed action so the team can understand how to cancel synchronization and use its fallback plan.

- [Robert Nystrom: State](https://github.com/munificent/game-programming-patterns/blob/master/book/state.markdown)

### 8. Escape, chases and evading pursuit

<a id="t038"></a>
id: t038
canonicalId: stealth-infiltration--t038
url: https://gamemechanics.pro/en/mechanics/stealth-infiltration/#t038

Escape breaks pursuer contact through routes, obstacles and changed visibility rather than running speed alone.

#### Mechanic variants

<a id="t038-variants"></a>
- Branches make a pursuer infer the chosen route. <a id="t038-v1"></a>
- A barrier buys time at the cost of a consumable. <a id="t038-v2"></a>
- Crowds hide a player who changes behavior. <a id="t038-v3"></a>
- Vehicles change speed and usable passages. <a id="t038-v4"></a>

Design example: A player closes a grille, changes clothes in a workshop and leaves through another exit.

Prototype check: Test the end of pursuit: safety should follow lost information rather than an unexplained hidden timer.

- [Robert Nystrom: State](https://github.com/munificent/game-programming-patterns/blob/master/book/state.markdown)

## Sources and examples

Sources support particular techniques or methodology, not every family variant. Design examples and mechanic combinations are illustrative.

- [Robert Nystrom: State](https://github.com/munificent/game-programming-patterns/blob/master/book/state.markdown): The author’s original discussion of states and transitions; rule implementation context, not evidence for every editorial variant.