Experiments

How repeatable are HITMAN's NPC routes? Observe before you interfere

Use a baseline and a second run to separate a character's normal route from the effect of your actions.

By GGX EditorialTest protocol

The Hitman Wiki documents default NPC walking cycles, including loops, stationary characters and routes affected by player actions. Exact timings for a selected World of Assassination mission are [CHECK IN GAME] until recorded.

Why a baseline matters

A character walking somewhere after you arrive does not necessarily mean you caused the movement. The community guide notes that some cycles need a nearby player or conversation trigger, and that reloading a save can affect a cycle. Starting conditions matter.

Two-run method

  1. Choose a story mission, starting location, loadout and difficulty. Record the version and pick one identifiable NPC.

  2. Restart the mission and observe for five real-world minutes without creating distractions. Log stops and movement.

  3. Restart again with the same settings. Introduce one controlled distraction at a recorded time and observe the same NPC.

  4. Repeat each run three times. Use a mission restart, not an assumed identical mid-mission save state.

Results

GGX has not recorded these runs: [CHECK IN GAME]. A change in one NPC's path would not establish how every guard behaves, nor would it justify a cross-game ranking of artificial intelligence. Keep the result specific to the mission, character and tested conditions.

Sources

Related game

Hitman: World of Assassination →

Related articles