Skip to content

VNS Ped Spawner

An in-game ped placement tool for FiveM. Admins open a UI with the /pedspawner command, place NPCs anywhere on the map, give them idle scenarios and attach target interactions, with no restarts and no code. Peds are saved to a JSON file and respawn for every player, including after server restarts.

Target and permission handling comes from vns-core, a separate free download:

  • Frameworks: QBCore, QBox, ESX
  • Targeting: ox_target, qb-target, qtarget (or no target at all)
  • Requires vns-core and ox_lib. No database; the UI ships pre-built.

What admins can do

  • Place peds in-game - open the UI, click Add Ped, use Use My Position to grab your current coordinates (or paste a vector4), pick a model and save. The ped appears immediately for everyone online.
  • Idle scenarios - give each ped a scenario animation (standing impatiently, smoking, on the phone; the dropdown list is configurable).
  • Target actions - attach any number of target options to a ped. Each action has a label, a Font Awesome icon (with a built-in icon picker), an event name to trigger, a Client/Server toggle and an optional job filter. This makes the script a quick way to wire peds up to your other resources (shops, job menus, teleports): just point the action at the event.
  • Edit and delete - every saved ped can be reopened, changed and removed from the same list; deleting asks for confirmation.
  • Teleport - jump to any saved ped straight from the list.
  • Persistence - all peds are written to peds.json inside the resource and respawn on resource start and for every player who joins.

Spawned peds are (by default) frozen, invincible and ignore world events, so they behave like proper static NPCs.

Access

Permissions are on by default. Only players with vns-core's admin ace (command unless you changed Config.AdminAce) or an identifier listed in Config.Permission.allowedIdentifiers can open the UI. Saving and deleting peds are checked again on the server. See Installation.

Open vs Encrypted

config.lua, client/client_open.lua and server/server_open.lua stay editable in the encrypted version. The command, permissions, animation list and ped defaults are in config.lua; the open files contain the target registration and the permission check. See Open Source & Encrypted Versions.