Bodybag Script

Most death interactions in FiveM stop at the downed state — a body lying in the road with nothing to close the scene. This bodybag script gives EMS and law enforcement the ability to physically wrap and transport deceased players, turning a flat mechanic into something that actually completes a crime scene narrative.

The design philosophy here is minimal dependency. The only hard requirement is a targeting system (ox_target or qb-target); beyond that you configure whether job restrictions or item requirements are needed, or skip both entirely for open-access servers. That flexibility means it fits into a barebones QBCore setup and an ESX server running a full medical framework without rewiring either.

Key Features

• Bodybag placement and removal on dead players via target interaction

• Removable bodybags with toggleable disable — lock removal to specific roles if needed

• Job and item requirements independently configurable (use one, both, or neither)

• Statebag-based synchronisation keeps all clients consistent with zero desyncs on restart

• Safe to restart the resource mid-scene — placed bags persist correctly through the cycle

• Exports and server events exposed for other scripts to add or remove bags programmatically

• Bridge functions available for framework-level customisation without patching core files

• 0.00ms resource monitor reading — confirmed at idle and during active use

Framework Compatibility

Framework-agnostic with built-in support for ESX, QBCore, and Qbox. Requires a target system; ox_target and qb-target both work.

The restart-safe statebag implementation is the detail most competing scripts get wrong — a half-wrapped body that vanishes on resource restart breaks immersion and creates unnecessary support tickets. This script handles that correctly out of the box. Rated 4.5/5 across ten community reviews.

Installation

1. Make sure ox_target or qb-target is running; one of the two is the single hard requirement.
2. Drop the resource into resources and add its ensure line to server.cfg.
3. Decide in the config whether job restrictions, item requirements, both or neither apply, and whether placed bags can be removed again.
4. Restart the server, bag a downed test player, then restart the resource mid-scene to confirm the bag survives the cycle.
5. Point any other resource that needs to place or clear bags at the exports and server events provided, rather than patching core files.