Skip to main content
Ambient NPCs reuse population peds created by GTA instead of spawning every AI character from the server. This preserves normal population behavior and scales better across the map.

​
Lifecycle

  1. Each client scans nearby population peds in small batches.
  2. The server validates reported candidates.
  3. An eligible character receives a temporary lease on a networked ped.
  4. HumaLike tracks the character while that ped exists and releases stale bindings when the game removes or replaces it.
  5. The character can later bind to another compatible ped.
The character identity and memory are stable; a GTA entity handle is not. Your integration should refer to the HumaLike NPC id whenever it stores character state.

​
Configure ambient population

Open a server in the dashboard and use its Ambient NPCs settings to enable the system and select the desired map limit and tuning. Dashboard policy is authoritative for the number of active ambient characters. The FiveM reporting defaults are designed for normal OneSync servers:
  • reports cover nearby NPCs rather than the whole map;
  • candidates are scanned and sent in bounded batches;
  • stable rejections are cached;
  • active leases are scoped to players near them.

​
Models

An ambient character only ever binds to a pedestrian of exactly its ped model, so the model decides where — and whether — the character is met. GTA’s population system spawns a fixed set of models, each in particular map zones: Beverly Hills types in Rockford Hills, beachgoers in Vespucci, Lost MC bikers around Stab City. A model the population never streets (story characters, cutscene variants, mp_ player models) leaves the character in the pool forever. Characters generated from a world get their model picked for them: the group’s home zone and the member’s sex and age band select a model the game streets there. For a hand-made ambient character, give it a model that GTA naturally creates in the intended part of the map. Which models that are comes from the stock GTA population files: which ped groups each map zone runs at each hour, and how common each model is in them. Only bodies about as common as the commonest one in the zone are used, so a generated character is on a ped players actually meet; the outfit, not the body, is what makes two characters on one model look different. A server’s own population overrides and addon peds are not read.

​
Performance tuning

Do not increase scan or report frequency only to make an NPC bind a fraction of a second sooner. Lower intervals increase client scanning, server validation, and network traffic. If you have measured a problem, the relevant advanced settings are documented under Configuration. Change one value at a time and compare humalike_status and server performance before and after.

​
Common behavior

  • An ambient NPC disappearing outside player scope is expected.
  • Its next compatible ped may have a different network id.
  • Different clients still observe the same networked entity while it exists.
  • HumaLike does not server-spawn the entire GTA population.
Use a static NPC when the physical character must always return to one exact place.

​
Next