← All mechanic references

Mechanics and variants

1Systemic interactions and immersive simsOverview and example ↗Shared object properties produce several solutions, allowing players to transfer known rules into unanticipated combinations.4

Mechanic variants

  • Materials determine responses to effects.
  • Environments carry effects between objects.
  • Tools work beyond a scripted target.
  • Consequences persist after the player leaves.

Design example. A metal crate becomes a conductor, pressure-plate weight or movable cover under shared rules. Prototype check: Test one property across object classes so visually identical rules do not hide inconsistent exceptions.

Context and sources: Robert Nystrom: State
2Physical materials, deformation and destructionOverview and example ↗Materials determine responses to force and damage; deformation and destruction create a new interaction structure.4

Mechanic variants

  • Elasticity restores shape after a load.
  • Plasticity preserves a dent after contact.
  • Brittleness splits objects above a threshold.
  • Fragments inherit selected original properties.

Design example. A thin panel bends open while a glass divider breaks into separate obstacles. Prototype check: Test traversal and fragment interactions after saving and loading a destroyed scene.

Context and sources: Robert Nystrom: State
3Ecology, food chains and environmental recoveryOverview and example ↗An ecosystem connects food availability, population sizes and environmental conditions, allowing interventions to propagate.4

Mechanic variants

  • Predators limit prey populations.
  • Plants recover under suitable conditions.
  • Pollution changes a site's suitability for a species.
  • Recovery starts by removing the damage source.

Design example. Cleaning a stream brings back insects, then fish and finally birds that feed on them. Prototype check: Test long unattended simulation and explain simplifications rather than claiming real ecological accuracy.

Context and sources: Robert Nystrom: State
4Character routines, needs and memoryOverview and example ↗Routines connect needs, available places and event memory to produce understandable daily character routes.4

Mechanic variants

  • Schedules set expected places at specified times.
  • Needs interrupt plans for recovery.
  • Memory changes attitudes toward familiar places.
  • Unavailable destinations trigger fallback behavior.

Design example. A craftsperson goes for lunch but chooses a cheaper canteen after a wallet theft. Prototype check: Test closed workplaces and missed appointments so NPCs do not endlessly attempt unavailable actions.

Context and sources: Robert Nystrom: State
5Creature training and tamingOverview and example ↗Creature training connects signals, actions and consequences to establish a clear, limited command vocabulary over time.4

Mechanic variants

  • Reinforcement increases a selected response's likelihood.
  • Context limits transfer of learned commands.
  • Trust unlocks more complex joint actions.
  • Rest prevents endless uninterrupted practice.

Design example. A creature learns to retrieve a marked object and later attempts it among distractors in another room. Prototype check: Test reward attribution to an action and distinguish refusal, misunderstood commands and fatigue.

Context and sources: Robert Nystrom: State
6Simulated societies, populations and autonomous communitiesOverview and example ↗An autonomous community distributes roles and resources without direct commands to each member, producing observable collective outcomes.4

Mechanic variants

  • Job-choice rules change employment structure.
  • Migration responds to differences in living conditions.
  • Social links transmit information among members.
  • Collective decisions aggregate different preferences.

Design example. A mine attracts workers, raises housing demand and changes the availability of craftspeople. Prototype check: Trace aggregate statistics to agent actions and avoid presenting a simplified simulation as a social forecast.

Context and sources: Robert Nystrom: State

Sources and examples

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

  • Robert Nystrom: State

    The author’s original discussion of states and transitions; rule implementation context, not evidence for every editorial variant.

CC BY 4.0 · gamemechanics.pro contributors