When a scene ends with a body on the tarmac, most servers have two options: a respawn, or a ped left lying in the road until somebody clears it. This adds the step in between. An officer or medic walks over, bags the body where it fell, and the scene can be worked and handed over before anyone moves on.

How it plays

Aim your target system at a dead player and a "Put in bodybag" option appears. A short kneeling animation plays, a body bag is laid on the ground at that spot, and the player inside is hidden and held in place with no collision until the bag comes off. Removing it is the same interaction on the bag itself, after which the player is visible again.

Who can bag a body

Two checks sit in the config, and either can be switched off:

• Job. Only the job you name can bag a body. It defaults to police; point it at your ambulance or coroner job instead if that suits your server.
• Item. Bagging uses up a bodybag item, and removing the bag hands it back, so supply stays with whoever stocks them.

The server also checks the distance between the two players, so a desynced client cannot bag someone from across the street.

Fitting it in

• Frameworks: ESX, QBCore and Qbox. On Qbox it talks to the QBCore compatibility object, so qbx_core has to be started before it.
• Target: ox_target or qb-target must be running; the interaction is registered on whichever is present.
• Item: add bodybag to your inventory's item list if you keep the item check on.
• Death check: by default a player counts as dead when the game says so. If your ambulance resource keeps players alive while downed, change the check in the client bridge file to call its export.

Bags are tracked in state bags, so every client sees the same thing. Restart the resource during a scene and bags already on the ground get their interaction back; a player who disconnects while bagged has their bag cleared. Server exports add or remove a bag for a given player without the job and item checks, which is how a morgue or coroner script would hand bodies over.

Configuring it

config.lua holds the interaction distance, the bag prop, whether the bag is frozen, whether bags can be removed at all, both animations and the notification text. The framework calls live in the two bridge files, so a different inventory or notification system is a few lines to change.