Description
A coroner workflow: bag a corpse, store it in numbered morgue cold-storage, then perform an autopsy that reveals the recorded cause of death. It bridges police, EMS and legal roleplay into a single flow, which is why servers buy it — the cause of death is hidden until the autopsy, creating real investigative roleplay across multiple jobs.
Prompt Template
You are writing a FiveM resource for a roleplay server. Detect the framework via…
The full prompt template and its reference Lua are part of a one-time pack. Pick your depth — both are lifetime access, no subscription, ever.
- 60 prompts + syntax-validated reference Lua
- Lifetime access — pay once
- All 510 prompts — the full library
- Per-prompt profit/trend intelligence (CSV + playbook)
- Lifetime free updates — new niches as the market moves
$49 for 60 · $199 for all 510 + intelligence — one-time, no subscription.
Expected Output
See content/expected-outputs/medical/09-coroner-morgue-autopsy.lua. It stores…
The full prompt template and its reference Lua are part of a one-time pack. Pick your depth — both are lifetime access, no subscription, ever.
- 60 prompts + syntax-validated reference Lua
- Lifetime access — pay once
- All 510 prompts — the full library
- Per-prompt profit/trend intelligence (CSV + playbook)
- Lifetime free updates — new niches as the market moves
$49 for 60 · $199 for all 510 + intelligence — one-time, no subscription.
Known Failure Modes & Corrective Prompt
- Cause of death leaked at bagging — sending
codto the client immediately defeats the investigation. It must only be revealed inside the autopsy server handler. - Client-generated body IDs — two coroners collide on the same slot. The id must be a server-incremented counter.
- Round-trip via TriggerEvent — the autopsy reveal never returns without
RegisterNetEvent+AddEventHandler.
Corrective re-prompt: "Never send the cause of death to a client until the autopsy completes. Store it only in the server's bodies table, generate bodyId from a server-side counter, and reveal cod exclusively inside the medical:morgue:autopsy handler via TriggerClientEvent to the coroner."
Framework Integration
- ESX: gate the coroner actions behind
xPlayer.job.name == 'ambulance'(or a dedicated coroner job) resolved throughexports["es_extended"]:getSharedObject(). - QBCore: persist bodies in a
morgue_bodiestable viaoxmysqland check the player's job withQBCore.Functions.GetPlayer(src).PlayerData.job.name. - QBox: use
exports.qbx_core:GetPlayer(src)for the job gate and pair the autopsy result withox_libcontext menus for the morgue UI.
Profit Potential
$250–$3500/mo on Tebex (expected ~$900). [INFERRED] priced inside the $50-389 script band against the signal-scraper tebex corpus (median seller $11.85K/mo, n=100); a rising cross-job module with defensible synergy.
Trend Signal
↗ rising — strategy: Coroner/morgue bridges PD+EMS+legal jobs; cross-job synergy is defensible per matrix and absent from basic jobs.
Sales Angle
Position as the module that connects three jobs — PD investigates, EMS bags, legal uses the autopsy. Recommended Tebex price $229.
Difficulty & Ship Time
intermediate · ships in 2-4h.