Skip to main content

InteractV

InteractV is a GTA V NPC interaction engine.

The runtime scans nearby peds, matches them against XML routes, starts scenario graphs, and can hand actors to reactive behavior profiles. The shipped routes, scenarios, behavior profiles, groups, and spawn triggers are embedded in the mod's DLL. Files under scripts/InteractV/ are override points for advanced users, not the only source of runtime data.

What's active​

  • NPC routes: gang turf wars, gang cluster trigger, bum shakedown, shopkeeper robbery, street intimidation, bum encounters, and optional police routes.
  • Scenario graphs: scripted steps, decisions, linked modules, recruitment, vehicle handoffs, police control, ambulance response, robbery, arson, fake deals, and pursuit flows.
  • Reactive AI: AUTO_REACT behavior profiles loaded from behaviors/*.xml.
  • World events: spawn triggers for territory contests, revenge, drive-bys, dismount assaults, police/FBI/army response, air support, bum events, and phone reinforcements.
  • Player-facing menus: F5 InteractV menu, F5 Events toggles, optional F6 crew command menu.
  • Basic has no territory, player involvement, phone, conquest, or ride-alongs. The paid Gamer and Partner editions add player involvement, phone reinforcements, faction SMS, territory, and the world reactions (police, military, air support) (see Editions).

Architecture​

InteractV is a living-world mod built in layers:

  • Decision: evaluates world context, utility curves, and emotional states to determine high-level intent.
  • Execution: a state-machine runtime (StateBase, PedStateMachine) with explicit completion signals and per-actor ownership (PedClaimRegistry), so an action ends when it really finishes and no two systems fight over the same ped.
  • Gameplay: autonomous gang wars, interactive shop robberies, dynamic police traffic stops and foot chases, territorial control, and ambient world drama.

The reusable behavior technology underneath — the "Interact Engine" — is being turned into a starting point other developers can build on. It is in development and not open yet.

Documentation scope​

These docs avoid documenting dead code as a real feature. A state or setting is only documented here when it's actually reachable from shipped XML, behavior profiles, spawn triggers, ally reactions, or runtime flows.