← All mechanic references

Mechanics and variants

1Action-adventureOverview and example ↗The player alternates combat, traversal and finding tools that open further stages of an adventure.4

Mechanic variants

  • A tool opens routes and changes combat.
  • A dungeon teaches one new action.
  • A companion grants access to another area.
  • Returning reveals changes to a familiar place.

Design example. A shield reflects an enemy beam and directs light toward a locked door. Prototype check: Check that the new tool remains useful beyond its tutorial room instead of becoming a disposable key.

Context and sources: Godot: Ray-casting
2Open worlds and free explorationOverview and example ↗Free exploration lets players choose destinations and visiting order from recognizable world features.4

Mechanic variants

  • A landmark attracts without a quest marker.
  • A rumor identifies an approximate search area.
  • A road offers a safer but longer route.
  • A systemic event changes the current route.

Design example. Smoke beyond a mountain draws the player off the road toward an unmapped camp. Prototype check: Hide objective markers and test whether the environment itself suggests a meaningful next destination.

Context and sources: Godot: Ray-casting
3Expeditions and returning to baseOverview and example ↗An expedition limits exploration by supplies and asks when to return with discoveries.4

Mechanic variants

  • Supplies determine the available travel radius.
  • A forward camp extends the expedition range.
  • An unknown region increases reconnaissance value.
  • Damaged equipment changes the return route.

Design example. A geologist collects a final sample before a storm, choosing a pass or a longer valley route. Prototype check: Check whether return costs are understandable before the player spends the final essential supply.

Context and sources: Godot: Ray-casting
4Archaeology and interpreting environmentsOverview and example ↗The player reconstructs the past from object placement, environmental layers and differences between traces.4

Mechanic variants

  • Layers reveal the order of site rebuilding.
  • Comparison links findings from separate rooms.
  • A tool exposes a hidden material trace.
  • A hypothesis meets independent corroboration.

Design example. A sealed doorway and a later mural suggest two different groups occupied the same temple. Prototype check: Check that the conclusion follows observable evidence rather than guessing an author's intended answer.

Context and sources: Godot: Ray-casting
5Treasure hunting and secretsOverview and example ↗Secret hunting combines a clue, interpretation of a location and an action revealing a hidden reward.4

Mechanic variants

  • A map gives relationships instead of coordinates.
  • Sound suggests the presence of a hidden passage.
  • A return visit uses a newly acquired tool.
  • A cache chain provides the next meaningful clue.

Design example. A bell tower's shadow points at a slab only in the morning, as an old drawing suggests. Prototype check: Test whether an intentional clue can be distinguished from decoration before the reward is found.

Context and sources: Godot: Ray-casting
6Walking simulators and observational explorationOverview and example ↗Observation and movement reveal events through environmental detail without requiring continuous combat or reflex tests.4

Mechanic variants

  • Routes alter the order of narrative discovery.
  • An object triggers a brief recollection.
  • Looking again reveals a newly meaningful detail.
  • Skipping inspection preserves another reading pace.

Design example. An empty room gains new meaning after a letter is read in the neighboring house. Prototype check: Test whether object placement communicates meaning without a compulsory explanatory monologue.

Context and sources: Godot: Ray-casting

Sources and examples

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

  • Godot: Ray-casting

    Primary documentation of spatial queries; implementation context for interactions with an environment.

CC BY 4.0 · gamemechanics.pro contributors