MrFr33

On a serious note. Anything going on or possible of alleyway chases? All the suspects seem to stick on the main roads. Not as much fun when they're on a linear path.

That's nice screenshot you got there! 

As the modifications for Grand Theft Auto V keep rolling in, we've been hard at work developing a brand new downloads section to better host, categorize and display the masses of new content on offer.
Featuring two entirely homepages, the new Downloads Portal creates the perfect distinction between GTA IV and GTA V content - this makes finding all of the latest files for your chosen game that much easier.  
Among the other changes are the reintroduction our advanced filtering system, allowing for downloads throughout all categories to be filtered by attributes specific to that category, and a much friendlier interface which emphasises content over clutter.
We're excited to be continuing the development of the new Downloads Portal and will be making further updates to it throughout the week.

http://www.lcpdfr.com/downloads/

I think I messed my post up but I didn't mean to include the album. But whatever go check out the album if you'd like.

Its about time I break my silence on this mod. If you enjoyed the vdH Bait Car mod, you'll enjoy this too. Development of this has been ongoing for about a week now, and some versions have been sent out for testing. Select a bait car from a list of models(changeable), wait for it to be driven to you, park it where you like, then sit back and wait. 
 
Current Features
Fully editable list of vehicle models Neat, clean interface for selecting the vehicle Simple to use, only one keybind(open the selection menu) Fleeing suspects are recognized by LSPDFR, so backup will assist you. Kill switch to toggle the bait car's engine. Planned Features
None Issues to overcome
A few minor conflicts with MoreControlV Video Preview: https://youtu.be/1pbZU-p3Kdc
I will post more updates in this thread when the time comes. I'm currently having a few people play with the mod to ensure that there are as few bugs as possible in the initial public release.
 

Since we have the new LSPDFR media thread, I figured i'd kick it off with a thread of some of your best screenshots taken in LSPDFR. I'll start off with a few.
Also, make sure to add a spoiler tag if you're posting more than one screenshot at a time.

Police Beats - Everyday Policework
very work in progress
 
Little bit of a change in direction after learning the basics of making these plugins and such and so we are now 'Police Beats - Everyday Policework' and will focus on handcrafting callouts for the districts of Los Santos, starting with Vespucci.
I've spent a few days doing the rounds and getting spawn points around Vespucci, Rockford Hills, Morningwood and all the suburbs in between. So far, I have the front door of almost every business or commercial property and their respective car parks or dining areas mapped out so that callouts will be quite specific - it could be a dispute about food quality at a restaurant or cafe that's gotten a bit out of hand, a hold up alarm, a car parking issue that's become violent or perhaps not even violent - someone could just be pissed off that someone else parked across two disabled bays and you've been called to give the dropkick a ticket. It could be anything!
Some areas such as the pier and the beach have a whole lot more and more specific callouts - lifeguards and security have apprehended someone and need you to come and lay down the law or perhaps one of the street vendors have been mugged, or had some items stolen. Every one of those little street vendor stalls now has a spawn point mapped to it and you could get called there - of course, when you do, there'll actually be a vendor there to speak to and there's probably a guy running away or hiding out nearby that stole something or punched him or took a leak on his cart. 
Back in the districts, almost every house is going to have a spawn point mapped for a house alarm, domestic, fight, burglary, noise complaint - whatever you can think of, I'll manage to squeeze it in there. The motels scattered throughout Vespucci all have locations mapped there for issues in the car park or perhaps unauthorised people using the pool - the owner might want them all charged with trespassing or maybe just moved on - those everyday calls are all gonna be there.
As you roll through the streets and see the bus stops and the train stations, think that they're also potential hotspots - public transport isn't necessarily the safest mode of transport and with all those hubs having spawn points, you could find yourself at any of them dealing with a fight on a bus or someone trying to ride the train for free.
Vespucci isn't your thing? Give it time, eventually I'll roll this model out over the entire city and county.
Calls will include:.
Welfare Check - 911 call was disconnected early or hung up immediately and the dispatcher can't get back on the line to the caller. These could be at an exact location such as a house or business or could be from a mobile phone and give you an area to check out.  You could find anything there - medical issues, fights, fires or absolutely nothing.  Traffic Complaint - This could be ongoing or historic. Maybe the complainant witnessed someone that lives in the street do a burnout so you just need to attend and speak to the complainant then head on down to get the other guys version of events to decide whether you'll cite him, warn him or leave it at that. Perhaps the complainant is following a vehicle doing something stupid... better catch up before the complainant loses sight.  Routine Assistance - Another agency needs help with something. It could be a bus driver with someone refusing to pay a fare or get off the bus or a security guard with trespassers in custody... maybe Ambulance officers need help with a cranky pateint. The dispatcher will tell you what it is and how urgently you're needed.  Stealing/Mugging - Someone has been mugged or had something stolen from them. Depending on circumstances, you or you and another car may be dispatched. If you arrive first, speak to the victim/complainant and get a description out to the other car or take the victim back to the station for a statement. If you're a bit slow no doubt the other unit will  give you a description and direction of travel for the offender so you can go have a look for him.  Hold Up Alarm/Robbery - Much the same as the above, two or more cars will be dispatched. Arrive first and you'll be getting the details from the victim/complainant. Arrive after and you'll be looking for the bad guys. Off course, if it's just an alarm it could be a false alarm or maybe the clerk panicked she a customer got angry and hit it.  Noise Complaint - The name speaks for itself. Attend and ask for the noise to be lowered or if you're particulary narks, issue a citation or take the offender in. Be mindful that every action has a reaction and if it's a party, there may well be more of them than you... Loitering/Trespassing - One or more people are hanging around somewhere and staff or residents aren't willing to move them on or haven't been successful - attend and move them on.  Alarm - Maybe a house a alarm or a car alarm - attend and check the area. May be something happening or someone suspiciously hanging around. Check bona fides and move them on. Suspicious Person - Maybe they were seen looking into cars or houses or they're just being a bit weird... attend and scope it out.  Disturbance/Domestic - Violent or verbal only. Attend, speak with all parties and move them on, arrest them, cite them - deal with the incident as you see fit. Indecent Act/Indecent Exposure - Someone's showing a bit too much skin off and may need a bit of a hand finding their pants - or perhaps they've found someone else's pants and that other person didn't really appreciate it... guess you'll find out when the call comes in! That's both a conservative and an ambitious list of calls that I'm hoping to get into the mod at some point and it's going to take a lot of time and work to get to a polished and compete state but I do intend to release the works in progress as there's something to release... for now though, I'm working with a tutor, learning to write scripts and working towards having at least one call to show off in the near future!
 
 

Honestly, don't bother with Script Hook V. If you want to do anything LSPDFR or police related, stick to Rage Plugin Hook.
There is a bit of a learning curve, but once you get the hang of it, things get easier.
As FtDLulz said, download Visual Studio Community 2013. Its free, and it is "straight from the horse's mouth", so to speak. Its a Microsoft tool, and Microsoft makes the .NET Framework, which is what all these plugins are developed on. The Community edition does not have all the tools that the professionals use in the Premium and Ultimate versions, but honestly, it doesn't matter. Community has more than enough built into it...take it from someone who is a .NET Developer for a living. I make money and pay my bills doing this stuff, and I use Visual Studio Premium at work. I find that Community is more than enough for stuff I want to do with LSPDFR scripts.
Now, all that said...DON'T LOOK AT ANY RAGE/LSPDFR CODE YET!!
Don't do it! I know you're looking at LukeD's Example API project in the other thread...its tempting, isn't it?
Well, don't download it! I'm watching you...
Okay, seriously...I would strongly suggest looking up some tutorials online on how to code in C#. Learn about the basic concepts...learn what a function is, what a variable is, what a loop is, etc. Start by making a program in C# that opens a Command Prompt (DOS) window and writes "Hello World!". You can do that one in about 5 minutes...literally.
Hint:
Console.WriteLine("Hello World!"); Once you're done that, and you're comfortable using Visual Studio, then follow the Rage Plugin Hook Getting Started guide in the Rage Documentation. And you'll be off and running! 
At that point, download LukeD's example API project from this subforum. If you take even just one or two days to learn some basic C# concepts, then you'll be far better off, and you'll be able to read and actually understand the example code that Luke has written. (Keep in mind that Luke's example is for developing an LSPDFR callout plugin...the guide in the Rage Documentation is for developing a script mod for GTA V...two different things!)
Feel free to post in this forum if you need help.
Good luck!

Hello.
someone could develop a mod
giving more intensity police lights?
Like in real life, you can see the red and blue lights bounce off the walls a few blocks away.

Morning folks,
Wondering if it's at all possible to add an option to the LSPDFR Radio menu while on a callout.
What I'm hoping to do is - rather than having a button to end callouts - have an option in the radio menu (where person/vehicle checking etc. is) saying something to the effect of 'clear callout'. Basically to radio in saying you're clear of the scene and it would end the callout. I know I can have a button to do this but just thought it would be a little neater and more polished with an option like that. 
I'd also like to add an option in there to radio for assistance from your supervisor. Basically press it and you'll get a message to guide you through the callout. Again, I know I can do this with a hotkey but it'd just be nicer to throw an option in there.
Wouldn't mind putting a request Ambulance/Fire button in there, too...
Cheers,
Kyben

Code 3 Callouts
"Attention all units, officer needs assistance. Shots fired. All available units, respond Code 3."
This is a plugin that I have been planning for ever since I started writing scripts for LSPDFR. Now that the LSPDFR API has come out, this idea can now become a reality!
The focus of this plugin will be to create a realistic experience where the player needs to do some actual police work. Police work is not always about flicking on the lights and sirens and flying down the road at 100 MPH. Nor is it always about pulling out an AR-15 and emptying a clip on a suspect.
In fact, most of the time, police work is all about dealing with people. Hearing both sides of the story. Figure out who is lying, and who isn't. Sometimes you have a helping hand when you have an eyewitness, and sometimes not. Or sometimes you will get eyewitnesses who contradict one another. Bob says the bank robber's car was blue. Jane says the car was red. Turns out, Jane was on her cell phone, and wasn't paying attention. Oh, and Bob was in the bathroom, so he didn't actually see anything. You later find out that the car was actually green.
It is YOUR job to determine what actually happened based on the evidence. Its time for your shift, Officer. Gear up, and move out.
Callouts
Assault Intoxicated Person Person with a Gun Unknown Trouble Hit and Run Impaired Driver Police Impersonator Road Rage in Progress Backup Required (Domestic Disturbance) Callouts Coming Soon
Burglary in progress (Next update!!) Future Callouts
Citizen reporting officer in danger Suspicious vehicle, with occupant(s) inside Domestic disturbance (May remove this, depending on how the above domestic backup call plays out) Bank robbery Officer requesting backup (potentially with one of the above calls!) Kidnapping in progress Shots fired ...and more!! (Not all of these callouts may be implemented. Plans are subject to change.)
Features
Framework & logic for managing each callout type Dispatch audio Altering suspect behavior based on the response of the officer Ambient events! ...more to come!! Screenshots
The following screenshots are from the Assault callout. You need to get stories from the victim and the suspect! Figure out who is lying by speaking to the witness!
Check everyone's ID's, just so you know who you are talking to, and so you can run their names in your computer!
Videos
FinKone has done a video demonstrating an early version of Code 3 Callouts, and watch for a video (coming soon!) by Jeff Favignano as well!
 
Developer Information
This plugin will be designed to work alongside callout plugins created by other developers. I am already in conversation with LukeD (Callouts V), FinKone, and Straysify, and best efforts will be made by all of us not to step on each other's toes.
Any other developers that will be producing callout plugins are encouraged to keep in touch with all other callout developers to ensure that we don't unnecessarily duplicate any work.

Using the steam version?  Lets back it up to prepare for next time (because this is not the last time it will happen.)
 

Help GTA V updated and now LSPDFR doesn't work!
With the ever increasing number of threads being made and the number of repeats we all have to make about Rockstar I figured it would be beneficial for you all to have a pinned thread on avoiding updates along with some useful information for you all.
Important Notices:
This is verified to work with the STEAM edition of GTA V, I cannot verify that it will also work with the RGSC edition, however if users report that it works I will update this thread to suit the requirements.
Do not upload or copy links to downloads containing the backup files, as we do not condone sharing the original game files.
Modding will always be broken by official updates. this is not just a Rockstar thing, this applies to any game that gets a new update. Cities: Skylines for example has native mod support through Steam workshop, but those mods get broken and require updating whenever Colossal Order (the developers) release an update.
Here is what they have to say on the matter:

And here is what Rockstar says on the matter:

So lets take a minute out of our time to not whine, complain, shout at and otherwise slander Rockstar for updating their game just because it slightly inconveniences you. If you had made backups you wouldn't be in any position to need to slander them. We're all getting tired of reading and responding to the same select posts "Rockstar sucks, they released a stupid update I don't care about". Let's just stop. Please?
With that over with, let's get onto....
The Guide Part 1 - Making a Backup:
It's no surprise that the title updates appear to be unavoidable in some regards. On Steam the launcher often forces you to update before you can play, I suspect this is similar for the RGSC edition. But fortunately it's possible to trick Steam (and possibly RGSC) into thinking it has updated, and as such that is the big secret about this guide.
1) Create a folder in your GTA V directory or in a preferred location (to avoid any possible chance of accidentally removing the files, I recommend making the backup outside of the directory)
2) Name this folder "GTAVBackup" or something similar so you know EXACTLY what this folder contains.
3) Take careful note of what patch you are currently on, this is best found via the RagePluginHook.log file, I'll show you what you're looking for:
Scroll down to the bottom of the log (most recent logged activity usually) and then slowly scroll up until you find the beginning of your last modded game session, it will look like this:
Product Version: 1.0.393.2"
4) Copy the GTA5.exe, GTAVLauncher.exe into the folder you created before (these are both located in the root of your GTA V directory)
5) Now go into Grand Theft Auto V / update / and copy the update.rpf file into the backup folder.
6) Congratulations you've just made a backup of the latest patch.
 
Now how do we stop GTA V updating?...
The Guide Part 2 - Avoiding the Update
Now as I mentioned earlier it is not actually possible to 100% avoid the update. But you can trick Steam and possibly RGSC into thinking it has updated.
1) Open your GTA V commandline file (called commandline.txt) and add the following to it "-scOfflineOnly" (without the quotes), this will force GTA V to load social club in offline mode (and therefore boot straight into singleplayer) NOTE: You must have loaded GTA V at least once to let it authorise your account before using offline mode.
2) Let GTA V update. CRAZY!? RIGHT? I know but there is method in the madness. Let it update to the latest patch version.
3) Here comes the magic, once the game has updated....guess what you do with those files we backed up in part 1? Yes, you replace the new files in your GTA V directory with the ones from your backup folder.
4) Launch the game and voila you've just gone backwards by a patch version. Your mods should now continue to work fine.
 
Keeping Track of Updates
Now that you know how to go backwards by a patch you also know how to manage your game versions. Or do you? You see while mods will all continue to work on the previous patch we will always strive to bring our mods up to date and in line with the latest patches so that you can keep enjoying them. Meaning they soon become outdated.
Keep an eye on all information possible, the main places to go to are:
• This forum (see the top of the website for important information).
• GTAForums thread for ScriptHookV (and Alexander Blade's development website)
• RagePluginHook website
• Rockstar Games website
Make your backup at the start of a patch when mods are all working again, as this is probably the point you want to go back to when an update occurs. Do not replace your backup files immediately. Only replace them when you KNOW mods work on that patch. And if you have the disk space, feel free to keep multiple backups.
 
Updated Information! - Reverting Game Version 757 to 678
Special thanks to all users who discovered this, and to MulleDK for the tutorial video that can be found at the top of the home page, or here.
In order to revert this game version you are required to backdate your Social Club Launcher application as well, failure to do so results in "error 16".
Follow the steps of the full guide as per usual, replacing the updated game files with the backed up old version (678). When you try to launch the game now you will received an error 16 launch failure.
1) Uninstall all traces of the Social Club application
2) Install the corresponding patch release for the Social Club launcher. This can be found direct from Rockstar's website here http://patches.rockstargames.com/prod/socialclub/Social-Club-v1.1.7.8-Setup.exe
3) Launch the game and enjoy your mods

I was just about to go to bed.
Sam, I hate you in the best possible way.

We've released a small update to LSPD First Response 0.2, including a number of fixes to reported issues.  Ever since the release of LSPDFR 0.2, we've been working to identify the most serious problems and glitches, and hope to have fixed all of these with this new update, LSPDFR 0.2a.  Among the fixes and changes included in this update are the debut of non-lethal stun guns, easier arresting and better first person view compatibility.
Also included are a couple of new LSPDFR API functions for developers, including the ability to play audio over the new police radio that we introduced in 0.2, and better access to pedestrian persona data.
You can find LSPDFR 0.2a, along with a full list of changes, on the LSPDFR download page.

So being that I am a software developer for a living, I thought I would create this thread to share some tips with fellow developers...especially those who are new.
Anyone can contribute to this topic...I myself am a newbie when it comes to RAGE Plugin Hook and LSPDFR. So anything useful that you come across, feel free to post it!
Some of what I have written below may not make sense to a new programmer, so if you have questions, or it seems like I am speaking Martian, feel free to ask questions!!
I'll start off by saying...
ORGANIZE YOUR CODE!! This means folders and namespaces for just about everything. Don't keep all your classes at the root level, and do not, for god's sake, do every part of your code in the Main class. Feel free to ask questions about this if you are confused, but LukeD's example API is a great way to start with namespaces.
  Take advantage of inheritance and polymorphism! Use base classes and interfaces for everything! (Callouts, pedestrians, vehicles, etc) For example, I have started on the framework for my callout plugin. I have a CalloutBase class, which inherits the LSPDFR Callout class, and it has all of my method overrides. The overridden methods in CalloutBase perform any actions which are common to all of my callouts. Each callout type will have its own class, which would, you guessed it: inherit the CalloutBase class. My CalloutBase class implements my "ICalloutBase" interface. The interface is for declaring methods or properties that CalloutBase may not be able to do anything with, but if you use the abstract keyword in C# (or MustOverride in VB.NET), then each callout class/type you create would have it's own set of actions for that function. For example, my ICalloutBase interface declares a method called "OnArrivalAtScene()". The CalloutBase class implements this as an abstract method, meaning, any class that inherits CalloutBase (say, ShotsFiredCall, for example) has to have a method called "OnArrivalAtScene", which would be a set of actions for the program to take when the officer arrives on scene OF THE SHOTS FIRED CALL ONLY. The abstract method I just created would be called in the Process() method of the CalloutBase class. Remember, Process() is an LSPDFR method that is called continuously. CalloutBase performs actions which are common to ALL callouts, including calling the OnArrivalAtScene() method. In CalloutBase.Process(), I check to see if the player's location is getting close to my callout location. If so, and if the callout state is still "Unit Responding", then OnArrivalAtScene() is called, and the state is changed to "At Scene". Now, when you create a ShotsFiredCall class, there is no need to call OnArrivalAtScene() from ShotsFiredCall.Process(), because CalloutBase.Process() has already done it for you! The example I stated above requires you to track the state of the callout (i.e. Dispatched, Unit Responding, At Scene, Call Completed, Call Cancelled, etc), but it just gives you an idea on how efficient you can make your code. Its a bit of legwork in the beginning, but it pays off BIG TIME as your plugin grows and matures. Using base classes and interfaces is not only useful for Callout classes. You can use them to track which Peds are suspects, and which are civilians, or what role a certain vehicle plays in your callout. You can add properties to Peds that don't exist in the Rage Plugin, like "MyPlugin.MySuspect.IsBankRobber", for a simple example.
  ERROR HANDLING!! Always, always, ALWAYS use proper error handling. One bad block of code can crash a user's entire game. Use Try...Catch blocks, and use the Catch block to log exceptions, so that when a user says "Your plugin is shit!!", then their log file will tell you what is wrong. Always use Ped.Exists or Vehicle.Exists (I think its called Exists for cars) to make sure that GTA V has not disposed of your object. GTA V does not mess around in terms of garbage collection and memory management. Always check if an object is null, and then if it has an Exists property, check that as well.
  ANYONE CAN CODE!! VB.NET and C# are both very easy to learn. It does take years to master programming, and a university education in Computer Science or Software Engineering definitely helps. But if you're a newbie, and want to learn, jump in with both feet! Search Google for tutorials, or buy a book at your local book store. I guarantee that you can write a Hello World! program in less than 5 minutes!
  VISUAL STUDIO IS FREE!! That's right! Visual Studio Community Edition 2013 is completely free. It doesn't have all the features that the pros use, but who cares? You aren't a software company!
  USE A CODE REPO AND SOURCE CONTROL!! When you download Visual Studio Community, you get the option of creating a Visual Studio Online account. DO IT! Visual Studio Online gives you free and unlimited access to code repositories where you can store and back up your code. If any programmers are reading this, they provide both TFS and Git based repos. Source Control allows you to keep track of each change you make to your code. Last update crashed everyone's GTA? No problem, just roll back your changes! Computer hard drive crash? Laptop stolen? No problem! Once you're up and running, install Visual Studio again, connect to your code repo, and all your code is back! For those that use TFS, you can create work items for yourself to track all changes that you need to make to your plugin. Each time you check in code, you can tie a set of changes (called a changeset) to a specific work item.
  BRANCH YOUR CODE!! This, at an elementary level, means to maintain two copies of your code. Your main branch (also referred to as your 'master' or 'trunk' branch) contains the most stable version of your code. Your second branch is called your 'dev', or development branch. All of your code changes and testing should be made on the dev branch. When you're ready to release, you merge all of the relevant changes from your dev branch to the trunk. This allows you to make different code changes to your project, all in parallel. This allowed me to recently release a LSPDFR 0.3 compatibility patch for Code 3 Callouts (I made those code changes in my trunk branch), while still working on the next update in my dev branch. See this MSDN link for more details: https://msdn.microsoft.com/en-us/library/ee782536.aspx 
  CHECK ALL DEPENDENCIES ON STARTUP!! Check file versions on EVERY DLL or assembly referenced by your project. You don't need to check the Microsoft .NET ones, but you should be checking file versions on RagePluginHook.exe, the LSPDFR DLL, and any other DLL (including RageNative UI, a Common DLL you've written yourself, etc) that is used by your project and needs to be installed in the GTA V folder. And NO, do NOT, I repeat, NOT use the Assembly class to load the DLL's into memory. That is just a waste of resources. Use the GetVersionInfo function of the System.Diagnostics.FileVersionInfo class instead.
  More to come...

Thanks for that, I'm sure it will help people.
A few things I'd like to add...
 
Don't sleep in your main thread!If you do, I will pay you a visit and it won't be nice! No, but seriously, the Process function is called every tick from LSPDFR's CalloutManager and if you decide to sleep there, you will block other callouts from working correctly. If you need to await something, do it in a separate GameFiber (if it requires game logic) or System.Threading.Thread if not. Use logging!Not only as a beginner, you should use logging extensively. You can create overloads of your logging function so that it only happens in debug build (like most LSPDFR logging) or under certain circumstances (such as logging levels), but use it. It will help you to better understand what went wrong on a user's end. Especially since as a beginner you probably have no real experience with debugging or checking crashes via crash offsets. Note that debugging V is unfortunately not really possible right now, as the DRM doesn't really like it. I didn't test on 393 yet, but earlier versions didn't work well. Keep an eye on performanceEvery now and then it might be a good idea to measure the time the main loop (your Process function) takes to run. 1-2 ms? Good! 20ms? Not so good... Don't be afraid to add a lot of general logic, your CPU can handle it. Game calls and poor code (such as unnecessary loops) will most likely be the cause of performance issues. Use commentsI'm not an idiot, I know what I'm doing here. Sure, now you do. But will you remember why you passed that 0x2 value to the native call in 2 weeks? Chances are you will not. And why did you apply the Wait task to the passenger again? Use comments to describe why you are doing such actions. It will help you later on, trust me.

Wow... Just wow...
I'm playing LSPDFR 0.2 with those mods :
MoreControlV Breathalyzer Police Radio Spotlight Traffic Control Vehicle Search Waiting for an update on the mod Keep Calm, because right now there is a little performance issue with the new update.
Was about to get Entity Persistent, happy to know there is a little problem with this mod too, I will wait for a fix!
But right now with all those mods, I HAVE TOO MUCH FUN! Never had this kind of fun since a loooooong time!
All those awesome mods should be merge all together in a Official DLC... I would pay a lot for that kind of stuff... 
Thank all the modders, it's just amazing!
And it's only the beginning! :D 
Gonna put a donation soon for sure! :)

Hey hey hey hey, what the hell man! GTA IV was a buggy piece of shit. LCPDFR was marvelous :)

Once I get to sit down and play with the API - I'll know soon.  I know they've had stuff listed in there but I just didn't get to test it out yet, if that makes sense.  I should know something tomorrow once I get some free time.

Just got done checking out the new LSPDFR 0.2 - exciting to get out there and patrol now!
 

We're proud to present the second major public release of LSPDFR, and by far the most epic version yet, LSPDFR 0.2.
LSPDFR Version 0.2 follows on from the groundbreaking success of our first release for GTA V, implementing a large number of features specifically asked for by our community.
You can find LSPDFR 0.2 on the brand new LSPDFR page, including a whole set of online resources and documentation, at http://www.lspdfr.com

The nerve of some people. Think they are so entitled.

Keep it up guys! :)