On most UK servers the story ends when the cuffs go on. FiveM detective RP starts from the opposite idea: the arrest is the middle of the story, and the best part — the scene work, the case file, the interview across the table — hasn’t happened yet. A working CID unit turns forty-minute crime-and-chase loops into cases that run for weeks, and it gives both your police mains and your criminal players a reason to log back in tomorrow.
Why detective RP is the missing layer on UK servers
Watch a typical evening on a British RP server and you’ll see the same shape repeat: a job goes off, response officers turn up, there’s a chase or a scuffle, someone gets nicked, and the whole event evaporates. Nothing carries over. The shop that got done over tonight has no bearing on anything that happens Thursday.
That’s the gap CID fills. An investigation is continuity — a thread that connects sessions, characters and crews over real weeks. It also solves a quieter problem: experienced police players who are bored of response work but don’t want to leave the job. Detective work is where they go to stay invested.
Building CID the British way
Get the basics right, because your players will notice if you don’t. A Detective Constable isn’t a rank above PC — it’s the same grade with a different specialism, and the same goes for DS and DI mirroring Sergeant and Inspector. Plainclothes, warrant card shown on contact, unmarked cars that look like something a force would actually lease. No tactical gear, no self-dispatching to every shout on the radio.
The handover is where CID roleplay actually begins. Response officers secure the scene, take first accounts and start a scene log; CID arrives, gets briefed, and takes ownership of the case. Write that handover into your police SOPs, because it creates a natural RP moment between two groups of players — and it stops detectives hoovering up jobs that a uniformed officer should keep.
The investigation arc: one crime, several sessions
The biggest mindset shift for new detectives is pacing. A case is not meant to be solved tonight. A decent arc looks like this: session one is the initial report and the scene — photographs, exhibits, first accounts. Session two is enquiries: CCTV canvassing, witness interviews, checking who was seen where. Session three, maybe a week later, is the knock on the door.
The tool that holds this together is a written list of lines of enquiry — every open question the case still has, kept in the case file. It means a different DC can pick the case up on a night the lead detective isn’t on, and it stops investigations dying because one player went on holiday. Cases that stall for a fortnight and then break open are a feature, not a failure.
Forensics roleplay that holds up
Forensics is where props and scripts earn their keep. Scene photographs first — a camera or photo script, or even screenshots pinned to the case channel, taken before anything is touched. Then collection: fingerprint dusting on points of entry, swabs on anything a suspect bled or drank from, casings picked up with markers placed where they fell. Evidence scripts that drop collectable items with metadata make this mechanical rather than imaginary, and the better ones degrade outdoor evidence in rain — which forces detectives to treat a scene as perishable.
Bag and label everything with exhibit references — real UK exhibits use the finder’s initials plus a number, so DC Bailey’s first exhibit is AB/1 — and log them in the case file. Then enforce the one rule that keeps forensics honest: if it wasn’t photographed or bagged in roleplay, it doesn’t exist for the case. No retroactive evidence, ever.
Case files, MDT work and warrants
Your MDT is either CID’s best tool or its biggest obstacle. What detectives need is case management: one file per investigation, with linked incident reports, suspect profiles, witness statements, the exhibit log and the lines of enquiry all hanging off it. Several modern MDT resources support linked reports and case tabs; if yours only does standalone incident reports, that’s a genuine reason to shop for a replacement.
Warrant applications deserve to be roleplay rather than a button. Make the detective write the grounds — what they believe, why they believe it, what they expect to find — and have a DI or a magistrate character approve or refuse it. It takes ten minutes and it makes a search feel earned. The case file also quietly protects your staff team: when a criminal player claims metagaming, the paper trail shows exactly what CID knew and when they knew it.
The interview room
Interviews are the set-piece of detective RP, and they’re worth doing properly. Distinguish a voluntary interview — the suspect attends by arrangement and can leave — from an interview after arrest, and open both with the caution. Two detectives in the room: one leads, one takes notes and watches for the detail the lead misses.
Teach your detectives that a no-comment interview is not a failure. It’s realistic, it’s the suspect’s right, and it forces CID to build cases that don’t depend on a confession. Disclosure is the counterweight: brief the suspect’s solicitor on an outline of the evidence beforehand, but hold your strongest card back for a second interview. Watching a suspect go from confident “no comment” to silence when the fingerprint match lands on the table is the best scene this whole discipline produces.
Keeping it fun for the criminals
Here’s the part most servers get wrong: detection is not the point. The contest is. If every crime ends in a solved case, your criminal players will stop committing interesting crimes — and without them, CID has nothing to investigate.
Good criminal players will leave evidence deliberately — a glove off for one job, a distinctive car, a face half-caught on CCTV — because being hunted is content for them too, and smart crews treat a case closing in as an escalating storyline rather than a loss. Encourage escalation agreements between crews and CID leads: a light OOC understanding that a case will run over weeks with give and take on both sides. And ban rubber-banding outright — not every crime gets solved, forensics is not a magic wand, and a lifted fingerprint means nothing unless that character’s prints are already on record from a previous arrest.
Once trust exists between the two sides, long-running operations become possible: surveillance logs on a target address, an informant registered to a handler DC, a small taskforce sitting on an organised crew for a month. One well-run operation like that generates more roleplay than fifty street chases.
Scripts, assets and staffing your first CID unit
The shopping list is short. An evidence system with fingerprint, DNA and casing collection plus a proper evidence locker; an MDT with case management as described above; a camera or photo tool for scene work; an interview suite — most decent UK police station MLOs include one, and the good ones have the recording light and observation glass that make the room feel real; and a small pack of plausible unmarked vehicles. Watch resmon on evidence resources specifically — anything spawning dozens of persistent scene props can creep on busy nights.
Staff it small and deliberately: one DS and two or three DCs is plenty to start. Recruit from response officers who already write decent reports, because paperwork discipline matters more here than arrest counts. Before going live, run a training case — stage a burglary with planted evidence and a briefed “suspect”, and let the new unit work it end to end. You’ll find the holes in your SOPs in one evening instead of one month.
Detective roleplay rewards servers that invest in it: deeper stories, longer character arcs and a police division people queue to join. For evidence systems, MDT resources and the rest of your UK police stack, browse the FiveM script ranges at vortexscripts.co.uk, xdopestore.com and cfxtebex.store.
