Default FiveM gives players nothing when a ped dies. You can bolt on a simple loot prompt — or you can build a system that treats every NPC death as a contextual event with loot outcomes specific to who that ped was. This script takes the second approach.

Loot Tables That Know What They’re Dropping

The configuration separates loot by NPC category and individual ped model. Gang members drop burner phones and dirty cash. Animals drop pelts and meat. Business NPCs carry wallets with cards. Zombie servers can assign survival loot to infected ped models. Each category gets its own item and money table with configurable rarity — and if you need to override the loot for a specific entity at runtime (say, a heist script that spawns a security guard with a specific keycard), the export function lets you assign custom drops to any entity ID.

• Per-NPC-category loot tables (gangs, animals, businessmen, custom groups)
• Per-model loot overrides for individual ped types
• Runtime export: assign custom loot to any entity from another script
• Money and item drops — both configurable per table
• Optional ragdoll looting: search peds before they die, not just after
• Smooth pickup animations synced between players
• Loot state synchronised across all players on the server
• Optional target system support for interaction prompts
• 0.00ms at idle, 0.01ms near active loot — verified lightweight
• ESX and QBCore — standalone capable

Framework Compatibility and Performance

The script runs on ESX and QBCore, with standalone operation also possible. Performance sits at 0.00ms idle and 0.01ms when a player is near active loot drops — 3D text rendering may add marginal cost on high-density servers, but this is a well-optimised script with roughly 1,600 lines of server code, the majority of which is readable. The 7-day money-back guarantee from the original creator reflects confidence in the product’s stability.

The Export Is What Makes It Flexible

Most looting scripts are closed loops — configure a table, done. The entity export here opens a different use case: any other script on your server can call it to set loot on a specific ped it just spawned. Your drug lab security guard script spawns an armed ped and immediately registers a keycard as its specific loot. That kind of cross-script integration is rare in this category and makes the system genuinely reusable across multiple scenarios without duplicating config.