Skip to content
View in the app

A better way to browse. Learn more.

LCPDFR.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

4 Screenshots

No Routine Stops

“There’s no such thing as a routine traffic stop.”

Most stops are still paperwork. Some aren’t. This decides which, based on who you actually pulled over – and then gives you a second or two to notice before it goes bad.

The driver tells you first

Nothing here comes out of nowhere. Before it happens, you get a beat of body language:

  • “The engine is still running. They keep checking the mirror.”

  • “They are reaching across to the passenger seat.”

  • “Reverse lights.”

  • “The two of them are talking fast. Neither is looking at you.”

And what you do about it changes the ending

That beat is a real window, not a warning label. The driver is reading you back – whether you drew, whether you’re pointing it at them, whether you closed in or backed off, whether you ran their plate first, whether there’s another unit standing there, and which side of the car you walked up.

The same tell ends differently depending on what you did:

  • A man reaching for something under the seat comes out shooting – or puts his hands up, if there’s already a gun on him when he comes back up.

  • A driver about to reverse into your cruiser just leaves instead if you stepped out of the way.

  • Someone planning to shoot their way out decides against it and simply floors it, if you already ran their plate and there are two officers watching.

  • A driver who was going to abandon his passenger in the road can’t – if you came up the kerb side, you’re standing exactly where that passenger would have stepped out, so nobody gets out and the whole car goes.

None of that is scripted per scenario. Outcomes decide for themselves what to become, from what you did.

What can happen

Twelve outcomes, from the small to the serious: they mouth off, rev at you, spit, sit there and refuse to move, run on foot, run in the car, reverse into you, come out shooting, fire through the window, give up – or the passenger runs while the driver stays put, and the other way round: the driver goes and leaves the passenger standing there with their hands up, and you have to choose which one you want.

Which one you get depends on the driver. Wanted, suspended licence, a record, a stolen car, how long they took to pull over, how many people are in it, whether it’s dark, whether you walked up with a gun in your hand, whether another unit is with you – and whether this exact person has run from you before, which the plugin remembers between shifts.

Requirements – and what it does NOT need

  • RAGE Plugin Hook

  • LSPDFR 0.4.9 or newer

That is the whole list. No Common Data Framework. No RAGENativeUI. No ScriptHookV. Nothing that another plugin can ship a different version of, and nothing that can take your game down when it updates.

The driver’s record – wanted status, licence, prior stops, citations, whether the car is stolen – all comes from LSPDFR itself, which already knows it. If you happen to have CDF installed for something else, registration, insurance, VIN and BOLO data get used as well. But it is never required, never loaded by us, and never version-bound.

Coming from Riskier Traffic Stops?

Riskier Traffic Stops by AstroBurgers is why this exists. It is the mod that made everyone expect something to happen at a traffic stop, and it earned every one of its 373,000 downloads. It hasn’t been updated since June 2023.

You don’t need to do anything special to switch. Uninstall it, drop this in, carry on. Your old settings map across one to one – Chance stays Chance, EStaticChance / ESuspectBased / ECompoundingChance become ChanceMode = Fixed / Reactive / Compounding, and each outcome switch has a matching one here. The full table is in the read me.

And if nothing else on your setup uses Common Data Framework, you can uninstall that too.

Install – 2 steps

  1. Drag the plugins folder into your GTA V folder, so you end up with
    Grand Theft Auto V\plugins\LSPDFR\NoRoutineStops.dll

  2. Load in and go on duty.

Settings live in plugins\LSPDFR\No Routine Stops\No Routine Stops.ini – every outcome can be switched off individually, and every risk factor is a number you can change. Edit it, save, then go off duty and back on. No restart needed.

If something goes wrong

Set ExplainInLog = true and every stop writes down what it decided and why:

stop: risk 41, 85% chance (+25 wanted, +12 licence suspended)
stop: Hostile, going with GetOutAndShoot
stop: officer aimed at them
stop: GetOutAndShoot becomes Surrender

Post that with any bug report and it usually answers the question on its own. Every step is wrapped in its own guard, so the worst case is a stop that quietly does nothing rather than a game that stops.

This was played, not just written

Every outcome in here was triggered on purpose, over and over, and watched – across hours of stops, on a game running sixteen other LSPDFR plugins alongside it, plus NaturalVision, ELS and a stack of callout packs. If it was going to argue with anything, it had plenty of chances.

A lot of what it does now exists because it went wrong first:

  • A driver who climbed out of his own car mid-stop and wandered off, because a standing animation on a seated ped makes the game empty the seat.

  • A suspect who floored it and then froze in the road – the pursuit was starting before the stop had let go of him.

  • An unarmed man getting out to throw punches at an armed officer, because “has a weapon equipped” is true of nearly every ped in the game.

All three were found by playing it, not by reading it. Behind that there are 197 automated checks that run before every build – they catch things like an outcome nobody registered, a setting in the ini that silently stopped doing anything, or an animation that would empty the driver’s seat again.

And it is built so that the worst case is a stop that quietly does nothing. Every step is wrapped in its own guard, because a plugin that takes your game down with it is the problem this was written to get away from.

Credits

  • AstroBurgers – Riskier Traffic Stops, which this replaces, and the reason anybody expects a traffic stop to be interesting at all

  • MulleDK19 and LMS – RAGE Plugin Hook

  • G17 Media – LSPDFR

Built by Rely.

Edited by Rely


Short Description

Traffic stops that can go bad - with a beat of warning first. Draw, back off or stay put: the driver is reading you too.

AI disclosure

The author has disclosed that AI tools were used in creating the following aspects of this file:

  • Description
  • Images
  • Mod and Mod Content (Substantial)

The plugin's C# was written with an AI assistant (Claude), working from my design. I decided what the mod should do and how it should feel, set the rules for every outcome and every risk factor, and did all of the in-game testing myself across several sessions - a number of the behaviours only exist because I found them going wrong while playing and had them fixed. The page description and this text were written with AI as well. The screenshots are genuine in-game captures, not AI-generated images. The titles and captions laid over them were composed by a small C# tool that was itself written with AI, which is why the Images box is ticked - no image generator was involved. The download contains no AI-generated art, audio or models.

User Feedback

Recommended Comments

BJ USA

Members

Interesting upgrade!

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.