ToastinYou

Hey there! Looking to create a callouts plugin of your own? Well, I'm here to help you.
So, let's get started. The requirements are as follows:
1) Have some general knowledge of C#, to learn the basics of C# I recommend reading Sections 1-17 here: http://rbwhitaker.wikidot.com/c-sharp-tutorials
2) Have Visual Studio Community Free, or any other version other than a trial, found here: https://www.visualstudio.com/en-us/visual-studio-homepage-vs.aspx
3) Have the files "RagePluginHookSDK.dll" and "LSPD First Response.dll", found in the downloads of RPH and LSPDFR.
 
Alright, once you have met those requirements, we can move onto the steps of starting your first callouts plugin!
1) Create a folder called "References" anywhere easily accessible to you.
     - In this folder, place your files "RagePluginHookSDK.dll" and "LSPD First Response.dll".

2) Open Visual Studio.
     - Once VS has fully loaded, at the top right click "File", "New", "Project".
     - At the left click the arrows next to "Installed", "Templates", and click on "Visual C#".
     - Then, in the middle box click "Class Library".
     - Under "Name" at the bottom, in the box type whatever you want your project/callouts plugin to be called.
     - Under "Location" choose where you want to save the project, this is recommended to be an easily accessible area.
     - Click "OK".

3) When all loads in, you should get a screen of code like this:
 
4) First, click "Project" at the top of the screen, then "Add Reference..".
     - A window will pop with a bunch of gibber jabber on it. Click the arrow next to "Browse".
     - At the bottom left, click "Browse.."
     - Once in Windows Explorer, navigate to your folder "References".
    - Hold the left control key and select both the files in the folder References (Rage SDK and LSPD DLL).
    - Make sure both boxes for the two files are ticked. Then, click "OK".

5) At the top of your code where everything says "using blahblah;". Replace all of those with the following lines below:
These basically state what references you're using, simple as that.
6) Over to the right, rename Class1.cs to Main.cs.
7) Then, you need to replace the code below the using statements with the following (explanations in the code, after "//"):
So this basically concludes our Main.cs file, all we have to do later on, as stated near the end of Main.cs above our method RegisterCallouts(), is register the callouts that we make, which we are about to do.
8) Next, we need to double click on "Properties" to the right. Under the dropdown box "Target framework:" select .NET Framework 4.6.
     - Then click Control+S and exit the Properties tab.

9) Over to the right, right click on ExamplePlugin and click "Add" then "New Folder", naming it "Callouts".
     - Then, right click on the "Callouts" folder, click "Add" then "Class..".
     - Name it whatever your callout name is, for this example we're going to be creating a simple "Pursuit in Progress" callout, so name it "PursuitinProgress.cs".

10) In it, use this code below:
Everything is explained in the code to help you out. I recommend you experiment with it to change things to your liking.
11) Now, go to Main.cs and under the RegisterCallouts() method you need to add the following:
12) Lastly, double click "Properties" to the right. Then, click "Build" to the left. Under "Platform Target:" select x64.
     - Thank you @Stealth22 for informing me of this!

Save and you're good to go! You got your first callout. You can ultimately expand upon this information I have provided with you to make your own unique callouts plugin!
     - To actually use the plugin, you have to click "Build" at the top of VS, click "Build Solution", make sure there are no errors, then go to wherever your project "ExamplePlugin" is located, go into bin > Debug. There you will find your references that were used and your "ExamplePlugin.dll". Drag and drop this file into GTA V > Plugins > LSPDFR and boot up GTA V! Also, if you want to quickly debug and make solving crashes easier, install "ExamplePlugin.pdb" to the same spot you installed ExamplePlugin.dll.

 
If you have any questions, please ask me!
If I forgot something or messed up something (as expected), please let me know.

Hey there! Looking to create a callouts plugin of your own? Well, I'm here to help you.
So, let's get started. The requirements are as follows:
1) Have some general knowledge of C#, to learn the basics of C# I recommend reading Sections 1-17 here: http://rbwhitaker.wikidot.com/c-sharp-tutorials
2) Have Visual Studio Community Free, or any other version other than a trial, found here: https://www.visualstudio.com/en-us/visual-studio-homepage-vs.aspx
3) Have the files "RagePluginHookSDK.dll" and "LSPD First Response.dll", found in the downloads of RPH and LSPDFR.
 
Alright, once you have met those requirements, we can move onto the steps of starting your first callouts plugin!
1) Create a folder called "References" anywhere easily accessible to you.
     - In this folder, place your files "RagePluginHookSDK.dll" and "LSPD First Response.dll".

2) Open Visual Studio.
     - Once VS has fully loaded, at the top right click "File", "New", "Project".
     - At the left click the arrows next to "Installed", "Templates", and click on "Visual C#".
     - Then, in the middle box click "Class Library".
     - Under "Name" at the bottom, in the box type whatever you want your project/callouts plugin to be called.
     - Under "Location" choose where you want to save the project, this is recommended to be an easily accessible area.
     - Click "OK".

3) When all loads in, you should get a screen of code like this:
 
4) First, click "Project" at the top of the screen, then "Add Reference..".
     - A window will pop with a bunch of gibber jabber on it. Click the arrow next to "Browse".
     - At the bottom left, click "Browse.."
     - Once in Windows Explorer, navigate to your folder "References".
    - Hold the left control key and select both the files in the folder References (Rage SDK and LSPD DLL).
    - Make sure both boxes for the two files are ticked. Then, click "OK".

5) At the top of your code where everything says "using blahblah;". Replace all of those with the following lines below:
These basically state what references you're using, simple as that.
6) Over to the right, rename Class1.cs to Main.cs.
7) Then, you need to replace the code below the using statements with the following (explanations in the code, after "//"):
So this basically concludes our Main.cs file, all we have to do later on, as stated near the end of Main.cs above our method RegisterCallouts(), is register the callouts that we make, which we are about to do.
8) Next, we need to double click on "Properties" to the right. Under the dropdown box "Target framework:" select .NET Framework 4.6.
     - Then click Control+S and exit the Properties tab.

9) Over to the right, right click on ExamplePlugin and click "Add" then "New Folder", naming it "Callouts".
     - Then, right click on the "Callouts" folder, click "Add" then "Class..".
     - Name it whatever your callout name is, for this example we're going to be creating a simple "Pursuit in Progress" callout, so name it "PursuitinProgress.cs".

10) In it, use this code below:
Everything is explained in the code to help you out. I recommend you experiment with it to change things to your liking.
11) Now, go to Main.cs and under the RegisterCallouts() method you need to add the following:
12) Lastly, double click "Properties" to the right. Then, click "Build" to the left. Under "Platform Target:" select x64.
     - Thank you @Stealth22 for informing me of this!

Save and you're good to go! You got your first callout. You can ultimately expand upon this information I have provided with you to make your own unique callouts plugin!
     - To actually use the plugin, you have to click "Build" at the top of VS, click "Build Solution", make sure there are no errors, then go to wherever your project "ExamplePlugin" is located, go into bin > Debug. There you will find your references that were used and your "ExamplePlugin.dll". Drag and drop this file into GTA V > Plugins > LSPDFR and boot up GTA V! Also, if you want to quickly debug and make solving crashes easier, install "ExamplePlugin.pdb" to the same spot you installed ExamplePlugin.dll.

 
If you have any questions, please ask me!
If I forgot something or messed up something (as expected), please let me know.

I'd like to add in a few things here just so you can look back on this when you are further into coding and want to know this and that about spawning Ped's/Vehicle's so you don't have to start a new topic later on, as the answer will be right here :)
First, you have your simple spawning of your Ped.
//myCopPed1 is the name of the ped you will use throughout your code, I used myCopPed1 as 1) it's a cop, 2) I have another cop Ped which is named myCopPed2. //= new Ped creates the Ped, and then you can sift through the arrow keys up and down to find (Model model, SpawnPoint spawnpoint, float heading); // under Model model you can put whatever model ID you want, so in my case I want a police officer, so I did "s_m_y_cop_01". // I have set my SpawnPoint as SpawnPointmyCopPed1.Position, yours could be called just plain SpawnPoint, but mine is from a more complex callout. // and then, I believe (never used it), float heading is ho high or low the ped is. Generally you would want your Ped at 0.0f unless you have some weird callout that spawns the guy in the air lol (Suicidal Guy Jumped off Building? CALLOUT IDEA! :) ) myCopPed1 = new Ped("s_m_y_cop_01", SpawnPointmyCopPed1.Position, 0.0f); Now, you may be wondering later on.. can I list off a few different models and just get it to randomly pick from that list/string of models? Yes, you can! It's pretty simple too..
// Okay, in this example I'm using a Vehicle style, same thing as Ped but spawning a Vehicle. // We use Model[] VehicleModels = new Model[] to start off and initialise it, and then we do { }; and inside those brackets we list off in strings what models we want spawned. So since I want a cop car, I could put any cop car models in there, which I have done. Model[] VehicleModels = new Model[]             {                 "POLICE", "POLICE2", "POLICE3", "POLICE4", "FBI"             }; // Here, we're just doing the same thing we did for our CopPed. we do myCopCar1 to start it off, = new Vehicle to tell the code we're creating a new Vehicle, then (VehicleModels[new Random().Next(VehicleModels.Length)] okay that might sound confusing, but it's just taking the VehicleModels we created, creating a new Random generator type of sorts, and creating the next vehicle to spawn, except randomly. Then we have SpawnPointmyCopCar1.Position to tell it where to spawn the car, again, yours could be as simple as "SpawnPoint". myCopCar1 = new Vehicle(VehicleModels[new Random().Next(VehicleModels.Length)], SpawnPointmyCopCar1.Position); Hope this helped or helps you in the future, if you need any further explaining or have some questions let me know! I'm always here :)

Hey there! Looking to create a callouts plugin of your own? Well, I'm here to help you.
So, let's get started. The requirements are as follows:
1) Have some general knowledge of C#, to learn the basics of C# I recommend reading Sections 1-17 here: http://rbwhitaker.wikidot.com/c-sharp-tutorials
2) Have Visual Studio Community Free, or any other version other than a trial, found here: https://www.visualstudio.com/en-us/visual-studio-homepage-vs.aspx
3) Have the files "RagePluginHookSDK.dll" and "LSPD First Response.dll", found in the downloads of RPH and LSPDFR.
 
Alright, once you have met those requirements, we can move onto the steps of starting your first callouts plugin!
1) Create a folder called "References" anywhere easily accessible to you.
     - In this folder, place your files "RagePluginHookSDK.dll" and "LSPD First Response.dll".

2) Open Visual Studio.
     - Once VS has fully loaded, at the top right click "File", "New", "Project".
     - At the left click the arrows next to "Installed", "Templates", and click on "Visual C#".
     - Then, in the middle box click "Class Library".
     - Under "Name" at the bottom, in the box type whatever you want your project/callouts plugin to be called.
     - Under "Location" choose where you want to save the project, this is recommended to be an easily accessible area.
     - Click "OK".

3) When all loads in, you should get a screen of code like this:
 
4) First, click "Project" at the top of the screen, then "Add Reference..".
     - A window will pop with a bunch of gibber jabber on it. Click the arrow next to "Browse".
     - At the bottom left, click "Browse.."
     - Once in Windows Explorer, navigate to your folder "References".
    - Hold the left control key and select both the files in the folder References (Rage SDK and LSPD DLL).
    - Make sure both boxes for the two files are ticked. Then, click "OK".

5) At the top of your code where everything says "using blahblah;". Replace all of those with the following lines below:
These basically state what references you're using, simple as that.
6) Over to the right, rename Class1.cs to Main.cs.
7) Then, you need to replace the code below the using statements with the following (explanations in the code, after "//"):
So this basically concludes our Main.cs file, all we have to do later on, as stated near the end of Main.cs above our method RegisterCallouts(), is register the callouts that we make, which we are about to do.
8) Next, we need to double click on "Properties" to the right. Under the dropdown box "Target framework:" select .NET Framework 4.6.
     - Then click Control+S and exit the Properties tab.

9) Over to the right, right click on ExamplePlugin and click "Add" then "New Folder", naming it "Callouts".
     - Then, right click on the "Callouts" folder, click "Add" then "Class..".
     - Name it whatever your callout name is, for this example we're going to be creating a simple "Pursuit in Progress" callout, so name it "PursuitinProgress.cs".

10) In it, use this code below:
Everything is explained in the code to help you out. I recommend you experiment with it to change things to your liking.
11) Now, go to Main.cs and under the RegisterCallouts() method you need to add the following:
12) Lastly, double click "Properties" to the right. Then, click "Build" to the left. Under "Platform Target:" select x64.
     - Thank you @Stealth22 for informing me of this!

Save and you're good to go! You got your first callout. You can ultimately expand upon this information I have provided with you to make your own unique callouts plugin!
     - To actually use the plugin, you have to click "Build" at the top of VS, click "Build Solution", make sure there are no errors, then go to wherever your project "ExamplePlugin" is located, go into bin > Debug. There you will find your references that were used and your "ExamplePlugin.dll". Drag and drop this file into GTA V > Plugins > LSPDFR and boot up GTA V! Also, if you want to quickly debug and make solving crashes easier, install "ExamplePlugin.pdb" to the same spot you installed ExamplePlugin.dll.

 
If you have any questions, please ask me!
If I forgot something or messed up something (as expected), please let me know.

If you were to replace "ALL" the vehicles then you will notice extreme performance decrease and in some cases, common cases, your game will crash after adding so many extra mb/gb of cars.

Hey there! Looking to create a callouts plugin of your own? Well, I'm here to help you.
So, let's get started. The requirements are as follows:
1) Have some general knowledge of C#, to learn the basics of C# I recommend reading Sections 1-17 here: http://rbwhitaker.wikidot.com/c-sharp-tutorials
2) Have Visual Studio Community Free, or any other version other than a trial, found here: https://www.visualstudio.com/en-us/visual-studio-homepage-vs.aspx
3) Have the files "RagePluginHookSDK.dll" and "LSPD First Response.dll", found in the downloads of RPH and LSPDFR.
 
Alright, once you have met those requirements, we can move onto the steps of starting your first callouts plugin!
1) Create a folder called "References" anywhere easily accessible to you.
     - In this folder, place your files "RagePluginHookSDK.dll" and "LSPD First Response.dll".

2) Open Visual Studio.
     - Once VS has fully loaded, at the top right click "File", "New", "Project".
     - At the left click the arrows next to "Installed", "Templates", and click on "Visual C#".
     - Then, in the middle box click "Class Library".
     - Under "Name" at the bottom, in the box type whatever you want your project/callouts plugin to be called.
     - Under "Location" choose where you want to save the project, this is recommended to be an easily accessible area.
     - Click "OK".

3) When all loads in, you should get a screen of code like this:
 
4) First, click "Project" at the top of the screen, then "Add Reference..".
     - A window will pop with a bunch of gibber jabber on it. Click the arrow next to "Browse".
     - At the bottom left, click "Browse.."
     - Once in Windows Explorer, navigate to your folder "References".
    - Hold the left control key and select both the files in the folder References (Rage SDK and LSPD DLL).
    - Make sure both boxes for the two files are ticked. Then, click "OK".

5) At the top of your code where everything says "using blahblah;". Replace all of those with the following lines below:
These basically state what references you're using, simple as that.
6) Over to the right, rename Class1.cs to Main.cs.
7) Then, you need to replace the code below the using statements with the following (explanations in the code, after "//"):
So this basically concludes our Main.cs file, all we have to do later on, as stated near the end of Main.cs above our method RegisterCallouts(), is register the callouts that we make, which we are about to do.
8) Next, we need to double click on "Properties" to the right. Under the dropdown box "Target framework:" select .NET Framework 4.6.
     - Then click Control+S and exit the Properties tab.

9) Over to the right, right click on ExamplePlugin and click "Add" then "New Folder", naming it "Callouts".
     - Then, right click on the "Callouts" folder, click "Add" then "Class..".
     - Name it whatever your callout name is, for this example we're going to be creating a simple "Pursuit in Progress" callout, so name it "PursuitinProgress.cs".

10) In it, use this code below:
Everything is explained in the code to help you out. I recommend you experiment with it to change things to your liking.
11) Now, go to Main.cs and under the RegisterCallouts() method you need to add the following:
12) Lastly, double click "Properties" to the right. Then, click "Build" to the left. Under "Platform Target:" select x64.
     - Thank you @Stealth22 for informing me of this!

Save and you're good to go! You got your first callout. You can ultimately expand upon this information I have provided with you to make your own unique callouts plugin!
     - To actually use the plugin, you have to click "Build" at the top of VS, click "Build Solution", make sure there are no errors, then go to wherever your project "ExamplePlugin" is located, go into bin > Debug. There you will find your references that were used and your "ExamplePlugin.dll". Drag and drop this file into GTA V > Plugins > LSPDFR and boot up GTA V! Also, if you want to quickly debug and make solving crashes easier, install "ExamplePlugin.pdb" to the same spot you installed ExamplePlugin.dll.

 
If you have any questions, please ask me!
If I forgot something or messed up something (as expected), please let me know.

Hey there! Looking to create a callouts plugin of your own? Well, I'm here to help you.
So, let's get started. The requirements are as follows:
1) Have some general knowledge of C#, to learn the basics of C# I recommend reading Sections 1-17 here: http://rbwhitaker.wikidot.com/c-sharp-tutorials
2) Have Visual Studio Community Free, or any other version other than a trial, found here: https://www.visualstudio.com/en-us/visual-studio-homepage-vs.aspx
3) Have the files "RagePluginHookSDK.dll" and "LSPD First Response.dll", found in the downloads of RPH and LSPDFR.
 
Alright, once you have met those requirements, we can move onto the steps of starting your first callouts plugin!
1) Create a folder called "References" anywhere easily accessible to you.
     - In this folder, place your files "RagePluginHookSDK.dll" and "LSPD First Response.dll".

2) Open Visual Studio.
     - Once VS has fully loaded, at the top right click "File", "New", "Project".
     - At the left click the arrows next to "Installed", "Templates", and click on "Visual C#".
     - Then, in the middle box click "Class Library".
     - Under "Name" at the bottom, in the box type whatever you want your project/callouts plugin to be called.
     - Under "Location" choose where you want to save the project, this is recommended to be an easily accessible area.
     - Click "OK".

3) When all loads in, you should get a screen of code like this:
 
4) First, click "Project" at the top of the screen, then "Add Reference..".
     - A window will pop with a bunch of gibber jabber on it. Click the arrow next to "Browse".
     - At the bottom left, click "Browse.."
     - Once in Windows Explorer, navigate to your folder "References".
    - Hold the left control key and select both the files in the folder References (Rage SDK and LSPD DLL).
    - Make sure both boxes for the two files are ticked. Then, click "OK".

5) At the top of your code where everything says "using blahblah;". Replace all of those with the following lines below:
These basically state what references you're using, simple as that.
6) Over to the right, rename Class1.cs to Main.cs.
7) Then, you need to replace the code below the using statements with the following (explanations in the code, after "//"):
So this basically concludes our Main.cs file, all we have to do later on, as stated near the end of Main.cs above our method RegisterCallouts(), is register the callouts that we make, which we are about to do.
8) Next, we need to double click on "Properties" to the right. Under the dropdown box "Target framework:" select .NET Framework 4.6.
     - Then click Control+S and exit the Properties tab.

9) Over to the right, right click on ExamplePlugin and click "Add" then "New Folder", naming it "Callouts".
     - Then, right click on the "Callouts" folder, click "Add" then "Class..".
     - Name it whatever your callout name is, for this example we're going to be creating a simple "Pursuit in Progress" callout, so name it "PursuitinProgress.cs".

10) In it, use this code below:
Everything is explained in the code to help you out. I recommend you experiment with it to change things to your liking.
11) Now, go to Main.cs and under the RegisterCallouts() method you need to add the following:
12) Lastly, double click "Properties" to the right. Then, click "Build" to the left. Under "Platform Target:" select x64.
     - Thank you @Stealth22 for informing me of this!

Save and you're good to go! You got your first callout. You can ultimately expand upon this information I have provided with you to make your own unique callouts plugin!
     - To actually use the plugin, you have to click "Build" at the top of VS, click "Build Solution", make sure there are no errors, then go to wherever your project "ExamplePlugin" is located, go into bin > Debug. There you will find your references that were used and your "ExamplePlugin.dll". Drag and drop this file into GTA V > Plugins > LSPDFR and boot up GTA V! Also, if you want to quickly debug and make solving crashes easier, install "ExamplePlugin.pdb" to the same spot you installed ExamplePlugin.dll.

 
If you have any questions, please ask me!
If I forgot something or messed up something (as expected), please let me know.

Hey there! Looking to create a callouts plugin of your own? Well, I'm here to help you.
So, let's get started. The requirements are as follows:
1) Have some general knowledge of C#, to learn the basics of C# I recommend reading Sections 1-17 here: http://rbwhitaker.wikidot.com/c-sharp-tutorials
2) Have Visual Studio Community Free, or any other version other than a trial, found here: https://www.visualstudio.com/en-us/visual-studio-homepage-vs.aspx
3) Have the files "RagePluginHookSDK.dll" and "LSPD First Response.dll", found in the downloads of RPH and LSPDFR.
 
Alright, once you have met those requirements, we can move onto the steps of starting your first callouts plugin!
1) Create a folder called "References" anywhere easily accessible to you.
     - In this folder, place your files "RagePluginHookSDK.dll" and "LSPD First Response.dll".

2) Open Visual Studio.
     - Once VS has fully loaded, at the top right click "File", "New", "Project".
     - At the left click the arrows next to "Installed", "Templates", and click on "Visual C#".
     - Then, in the middle box click "Class Library".
     - Under "Name" at the bottom, in the box type whatever you want your project/callouts plugin to be called.
     - Under "Location" choose where you want to save the project, this is recommended to be an easily accessible area.
     - Click "OK".

3) When all loads in, you should get a screen of code like this:
 
4) First, click "Project" at the top of the screen, then "Add Reference..".
     - A window will pop with a bunch of gibber jabber on it. Click the arrow next to "Browse".
     - At the bottom left, click "Browse.."
     - Once in Windows Explorer, navigate to your folder "References".
    - Hold the left control key and select both the files in the folder References (Rage SDK and LSPD DLL).
    - Make sure both boxes for the two files are ticked. Then, click "OK".

5) At the top of your code where everything says "using blahblah;". Replace all of those with the following lines below:
These basically state what references you're using, simple as that.
6) Over to the right, rename Class1.cs to Main.cs.
7) Then, you need to replace the code below the using statements with the following (explanations in the code, after "//"):
So this basically concludes our Main.cs file, all we have to do later on, as stated near the end of Main.cs above our method RegisterCallouts(), is register the callouts that we make, which we are about to do.
8) Next, we need to double click on "Properties" to the right. Under the dropdown box "Target framework:" select .NET Framework 4.6.
     - Then click Control+S and exit the Properties tab.

9) Over to the right, right click on ExamplePlugin and click "Add" then "New Folder", naming it "Callouts".
     - Then, right click on the "Callouts" folder, click "Add" then "Class..".
     - Name it whatever your callout name is, for this example we're going to be creating a simple "Pursuit in Progress" callout, so name it "PursuitinProgress.cs".

10) In it, use this code below:
Everything is explained in the code to help you out. I recommend you experiment with it to change things to your liking.
11) Now, go to Main.cs and under the RegisterCallouts() method you need to add the following:
12) Lastly, double click "Properties" to the right. Then, click "Build" to the left. Under "Platform Target:" select x64.
     - Thank you @Stealth22 for informing me of this!

Save and you're good to go! You got your first callout. You can ultimately expand upon this information I have provided with you to make your own unique callouts plugin!
     - To actually use the plugin, you have to click "Build" at the top of VS, click "Build Solution", make sure there are no errors, then go to wherever your project "ExamplePlugin" is located, go into bin > Debug. There you will find your references that were used and your "ExamplePlugin.dll". Drag and drop this file into GTA V > Plugins > LSPDFR and boot up GTA V! Also, if you want to quickly debug and make solving crashes easier, install "ExamplePlugin.pdb" to the same spot you installed ExamplePlugin.dll.

 
If you have any questions, please ask me!
If I forgot something or messed up something (as expected), please let me know.

With LSPDFR 0.4 the API received a few minor changes in terms of the Persona class, which might require recompilation on your end. While there are not many new additions to the API just yet, we hope to change that soon with our next minor update. We ask you to bear with us for a little bit longer before we expand our API functionalities.
 
As for additions for newly introduced 0.4 features, we ask you to provide some feedback here in the thread on what you would like to see. We have showcased scenarios in one of our announcements and still plan to make the available shortly. In short, a scenario takes over control during a chase or a traffic stop to provide unique behavior. During a scenario, it has full control over all entities. Another useful addition will probably be frisking and the ability to place items on peds, that can then be found, much like we had it in LCPDFR.
 
Thanks for your patience and all the work you have done.

Hi All,
 
I know the LSPDFR community is aflush with Work in Progress callout plugins, However I've decided to have a crack at my own, using both experience out of game, and a list of callouts I've wanted to see based on my play style. My goal is not to create extravagant scenarios, but to bolster your existing list of calls with a few of my own. Each call will encompass a variety of circumstances or locations. I'll keep a list of planned features here and welcome any and all suggestions. 
 
Planned Calls
 
Tresspass on the railway [In Progress]: Inspired by a lack of British Transport Police calls, This scenario will have you respond to various rail network locations across the city and outlying areas to remove an individual from the track. They will attempt to flee from you. There is also a chance that the call is dealt with prior to your arrival and as such you will be stood down.

Antisocial Behaviour[In Progress]: You're asked to respond to an individual acting anti-socially in a public space. They're likely going to be drunk, violent, boisterous or a combination of all three.

Fail to stop [Complete]: Whilst this has been address across multiple plugins, I've left this in as it was the first callout I've created and it's sentimental! You're asked to respond to a fail to stop, in which a pursuit is already in progress.
 
Suspicious Circumstances [Planned]: This call will encompass a variety of circumstances, including an individual taking photographs of sensitive properties such as police stations or government offices, An individual acting suspiciously at a rail terminal or airport, Reports from neighbours regarding suspicious sightings on another property, and more.
 
Abandoned vehicle/vehicle alight [Planned]: A vehicle has been found in a public area either abandoned, or alight. Investigate the scene and handle the aftermath appropriately.
 
I will update this list when more callouts are planned, or when their status changes. I welcome any suggestions.
 
A big thanks to @ToastinYou for their wonderful guide, which helped massively in working out the format for the plugin. Whilst i've developed in c# before, I've never looked into a plugin until I read that guide.
 
 
 

Due to a lack of time and inclination on my part, I have decided to make all of my LSPDFR projects open source under the GPL, effective immediately. Most of them probably don't work that well anymore, and I simply don't have the time to develop or maintain them any longer.
 
This will also serve as my defacto "retirement" from LSPDFR development. I may decide to pick things up again in the future, who knows. But for now, this is my way of giving back to the community, and possibly inspiring or helping other people who are trying to learn software development.
 
The code is old, and was written when I was still new to LSPDFR/GTA programming. It could probably use some refactoring, but again, I have no time to do any of that. Feel free to submit a pull request with any suggested improvements, and I will look at the PR's as time allows.
 
If there is enough activity on trying to move the project forward, I can explore doing releases in the future, and crediting any contributors. Feel free to use this repo as a resource to learn from and improve your programming skills.
 
This goes without saying, but this code is provided with no warranty, and I accept no liability for anything. 😛
 
Lastly, I would just like to say...there are a lot of people to thank for my time in the LSPDFR community, and I apologize if I miss any names, but you all know who you are.
- @Sam @LMS @Cyan @MulleDK19 You guys laid the foundation for all GTA and RPH development, and for that, the community owes you a debt of gratitude!
- @Jeff Favignano @FinKone You two are the ones who got me interested in GTA development to begin with! (Yes Jeff, I blame you for the countless hours I've spent debugging my code! 😛)
- @Jeff Favignano @Polecat324 @Bayareabuggs @Zachary Houseknecht Thanks for all the inspiration, and for all the times you guys graciously tested my plugins for me!
- @Albo1125 What can I say about Albo? NOTHING! Just kidding, Albo...you came to me when you first started learning the ropes, and you grew into a fantastic dev (*sniff* They grow up so fast...)
- @PNWParksFan You know why...keeps giving me work to do on my code... *grumble*  #InsideJoke
- @LukeD @alexguirre @Fiskey111 @PNWParksFan For the countless times you bailed me out of difficult coding situations (and Luke, for showing me that C# is better than VB!)
- @khorio All of the explosions and other shenanigans you pulled for our countless entertainment
- @PeterU For all the work you did in trying to help me maintain my plugins!
- @ToastinYou Eh, you didn't do anything. I just wanted to find a reason to give you a shout-out. *snicker*
 
Thanks all, and enjoy the code! Or what's left of the working parts of it...?
 
https://github.com/Stealth22PD/code-3-callouts 
https://github.com/Stealth22PD/alpr-plus 
https://github.com/Stealth22PD/keep-calm 
https://github.com/Stealth22PD/traffic-control 
https://github.com/Stealth22PD/stealth-common 

Dear all, 
 
As many of you will have noticed, my activity in the LSPDFR scene has decreased significantly over the past few months. There are many reasons for this, the details of which I won't bore you with. It mostly comes down to being busy with other things in my life, as well as LSPDFR becoming less interesting for me having played it for so long and the introduction of frameworks allowing modded GTA5 multiplayer environments.
 
How times have changed since when I joined the community in 2015, from me taking an interest in learning to code in C# to having multiple plugins released on the site. It's been one heck of a journey here. I recall well the first 'mod' I uploaded for the LSPDFR community, which was called 'More Jail Points' at the time. This was first published for RAGEPluginHook 0.20. This later evolved into 'More Jail Points & Prisoner Transporter' and is now known as the all-so-familiar Arrest Manager. When I was contacted by @dbock1989, who was so enthusiastic about my More Jail Points & Prisoner Transporter plugin at the time, I couldn't quite believe it. He had been so kind as to create a variety of images related to the plugin (see below)! It frankly couldn't have been a more exciting moment at the time and, alongside other overwhelmingly positive and welcoming feedback, served as a major motivation factor for me to continue learning to code and create plugins.

 
Following this, I was looking to give more purpose to the LSPDFR traffic stop system. And so, Traffic Policer was born - a plugin originally intended to add a few ambient events related to traffic offences. This has now grown into one of my most feature-packed plugins to date. By this time, some YouTubers started using my plugins in their videos. Not only was this a great way for me to obtain feedback on my mods' user experience, I also watched @Zachary Houseknecht with great pleasure while my ANPR Hit AI lit many of his police vehicles on fire... An absolute howler: https://youtu.be/4D8HshZzWMQ?t=606
 
Some weeks on and Assorted Callouts was next in line. This was originally created out of a callout idea by  @CaptainSugarFree  and turned into what is now known as the Pacific Bank Heist. This took about 4 weeks of intensive development to fully complete (and am I shocked at the code quality looking back at it now... works though). As the first of its kind, the callout featured voice-overs and an intense, detailed SWAT based LSPDFR callout. I was incredibly proud for this to be featured on @Jeff Favignano's channel and I see now that the video in question has amassed over 1.9 million views... breathtaking. https://www.youtube.com/watch?v=eIXKvUyzylA
 
Moving on again. At this point, @FinKone had managed to get me into YouTube. After having released British Policing Script, longing for an LSPDFR experience closer to home for me, many longed a version of the plugin for international and American users to incorporate the traffic stop improvements and a court system. With that, I released LSPDFR+ by doing my first ever YouTube live stream, which was quite the experience. After this, I released Siren Mastery, PoliceSmartRadio and a variety of other tools and smaller plugins. Many hours of coding, effort, stress, giving support and obtaining feedback had been put in by this point. I was absolutely chuffed to then achieve one million downloads on my published files...
This figure has since risen to over five million.
 
Following some negative coverage of LSPDFR in some of the Australian media, I'm also very happy that Wired UK decided to publish an overwhelmingly positive article on the whole GTA5 police modding scene: https://www.wired.co.uk/article/gta-5-mods-lsdpfr-british-police?utm_content=buffer9ca53
 
After PoliceSmartRadio's release - with the infamous April FoolsRadio download giving four thousand people a perhaps frustratingly good laugh - I placed the whole modding scene lower in my priority list. As mentioned previously, this has since been pushed far further down.
 
Some thoughts on the community's development over time
I would describe the LSPDFR community as healthy. @Sam @LMS and all the other contributors have created something very special for all the right reasons and this is largely reflected in the attitudes of the staff & moderation team and community members. With publishing mods on a popular website like this, unfortunately, comes some drama and negativity - and while I have not always agreed with the way and speed the moderation team dealt with my reports relating to me and my work, they have done a good job overall. The few issues that I experienced were all resolved. From my experience in the plugin side of the modding scene, this continues to be the case now.
 
One thing I noted during the months that passed is that both experienced but particularly newer modders are now frequently treated with disdain in the scene. The modding scene has grown massively since when I first started and unfortunately, in this area, it shows. Everyone starts somewhere and the fact someone is spending their free time creating something for all of you to download, for free, has become massively underappreciated and taken for granted. Sure, a new modders' release may be full of bugs and be nowhere near as feature-rich as more developed plugins, but this takes time to solve. Had I received the negative feedback I've seen on many a new modder's release page back in 2015, you can rest assured I wouldn't have continued my development here. When providing feedback, by all means, point out the issues, but do so in a friendly, constructive manner, not in an entitled, toxic one. Have a look at the first few comments on my Arrest Manager download page to see what that is like - this was a major factor for me to consider continuing development! It is essential for the development of the LSPDFR modding community that this attitude is changed back to what it was in the 'good old days'.
 
With all that said, I also hope the release of LSPDFR 0.4 kicks a breath of fresh air into the now somewhat stale core LSPDFR modification. With over 2 years having passed since the latest update of the core modification, I'm sure we all agree that an update would be a very welcome step. From the various preview posts released by the development team, it looks that we all have something great to look forward to there.
 
'Retirement'? So does that mean you're permanently done with the LSPDFR modding scene?
No, but I won't be actively developing plugins for LSPDFR any more. To be fair, nothing's really changing much now compared to the past few months. I intend to remain as a member of the LSPDFR Testing Team and I'm sure I'll be drawn back in at some point to explore some of the new development options in the 0.4 API. I'll also stay around on my discord and occasionally the forums and I intend to continue publishing occasional videos on my Youtube channel. If my time and motivation levels allow, I may publish some minor updates to my current mods before 0.4 is released. The fact remains, however, that I would currently classify myself as 'inactive' in the scene. With so much other stuff going on, I simply don't have the time to commit that I used to. It would be a pity to say the least to let all my work slowly deteriorate and waste away. Therefore, I've decided to publish the source code to some of my plugins to https://github.com/Albo1125/. At the very least, I would like it to be a learning resource for other ambitious plugin developers in the scene. At best, I hope other developers will take it upon themselves to improve the code where necessary (yes it is very necessary!) and create pull requests to share those improvements. These can then be merged and released, with credits obviously included for contributors.
 
Back when I started developing for LSPDFR, very few learning resources were available bar the great example project by @LukeD . This hasn't really changed since, despite the creation of the LSPDFR API repository by LMS (https://github.com/LMSDev/LSPDFR-API) and some posts aiming to document the LSPDFR functions by myself in the API development subforum. A noteable step was the creation of the LSPDFR Developers Discord server thanks to  @Stealth22 A full post with current development resources can be found here: 
I'm planning to publish the source code to a number of my plugins one-by-one to improve this and give something to the community:
Arrest Manager: https://github.com/Albo1125/Arrest-Manager  Assorted Callouts: https://github.com/Albo1125/Assorted-Callouts Albo1125.Common: https://github.com/Albo1125/Albo1125-Common Traffic Policer: https://github.com/Albo1125/Traffic-Policer LSPDFR+: https://github.com/Albo1125/LSPDFRPlus British Policing Script: https://github.com/Albo1125/British-Policing-Script  
By no means do I claim that any of the code I post is perfect or amazing - on the contrary, far from it. With the experience I have now gained, reading through some of my old code makes me want to tear my hair out. This is only to be expected, though - most of my plugins were created as part of my learning experience of C#. Prior to this, I had no coding experience or knowledge. It's fascinating to see how the quality of my code has evolved over time by looking at my various different plugins in order of initial release date.
 
Wrapping up. I hope this post provides some clarification and closure for those of you wondering where on earth I've been over the past few months. It's been an absolute blast and a pleasure. To all of you who were a part of my journey here, thank you.
 

This was something I was working on for S.W.A.T.: Revamped, but since it will take a while before that goes public I might just release this sooner on its own, if there is enough interest.
 
Ever get sick of hospital restarts? Video is self explanatory:
 
More info coming soon

Not really unless it's open sourced.

Woops, didnt even realise that i had wrote this, definitely came out wrong lol. Edited it, thanks :)

WOOP! Thank you so much <3

WOOP! Thank you so much <3

YAYYYYYYYYYYYYYYYYY

Been a while, huh?
 
You know, when we first started making LSPDFR, the whole process was pretty much one big roller-coaster that didn't have any brakes:  there were the obvious highs when we'd finally add in something cool, but the low points were pretty hard as well - the amount of work that went into simply researching how things worked really took its toll as well.  And, of course, while this was all going on there just simply wasn't any stopping, we were a couple of (somewhat) real people who essentially lived in Los Santos for just about all of 2015, spending month after month pushing forward and trying to come up with things that everyone here would like to see.
 
So, of course, the grind and the pace of everything simply just wasn't sustainable and after 0.3, it's no secret that while the numbers and everything for our site are still on the up, month after month, things did slow down quite substantially for the actual mod itself.  But, we can tell you, this wasn't all bad news - it's afforded us the opportunity to take a step back and really look at the mod and figure out where we want to go next with it.  While our approach before was all about cramming as much new stuff as we could into a couple of months of development, we've now been able to look back at many of the original ideas and concepts that we had for LSPDFR and build on them.  Of course, with that being said, there's still a lot of new stuff crammed into 0.4!
 

 
With 0.4, we've taken the time to fix a couple of those "how the hell didn't they add this yet" moments :)
 
Aside from the cool little additions like this, though, the major theme of 0.4 is Character.  Ever since seeing the character system for GTA Online, it was always our goal to implement something similar in LSPDFR.  There's just something that much more personal and immersive about playing a game with your own character, and the possibilities that it offers are staggering too.  And yes, while mods like EUP are fantastic (and awesomely compatible with 0.4!), they still feel somewhat separate or distant.  With 0.4, this separation is gone.
 

 

 
No, these shots aren't taken from GTA Online.  This is our own, fully-featured, LSPDFR Character Creator.
 
Of course, we'll talk more about the new Character features in LSPDFR 0.4 later.  The Character Creator menu shown above is obviously only one part of what's new in this regard, although hopefully it emphasizes the effort that we've gone to.  Thanks to some of the new additions like this, much of 0.4 actually looks and feels like an entirely new mod altogether.
 

 
Officer Ronson and his clones obviously couldn't make it to the flashlight party. 
 
Stay tuned!  We'll be sharing more about 0.4 soon.

Going to be back in development, Soon?™

Going to be back in development, Soon?™

I really like you crafted an algorithm and managed to solve this by yourself, great job!

try..catch? Not string.Split(...)?
https://msdn.microsoft.com/pl-pl/library/tabh47cf(v=vs.110).aspx

Hey there! Looking to create a callouts plugin of your own? Well, I'm here to help you.
So, let's get started. The requirements are as follows:
1) Have some general knowledge of C#, to learn the basics of C# I recommend reading Sections 1-17 here: http://rbwhitaker.wikidot.com/c-sharp-tutorials
2) Have Visual Studio Community Free, or any other version other than a trial, found here: https://www.visualstudio.com/en-us/visual-studio-homepage-vs.aspx
3) Have the files "RagePluginHookSDK.dll" and "LSPD First Response.dll", found in the downloads of RPH and LSPDFR.
 
Alright, once you have met those requirements, we can move onto the steps of starting your first callouts plugin!
1) Create a folder called "References" anywhere easily accessible to you.
     - In this folder, place your files "RagePluginHookSDK.dll" and "LSPD First Response.dll".

2) Open Visual Studio.
     - Once VS has fully loaded, at the top right click "File", "New", "Project".
     - At the left click the arrows next to "Installed", "Templates", and click on "Visual C#".
     - Then, in the middle box click "Class Library".
     - Under "Name" at the bottom, in the box type whatever you want your project/callouts plugin to be called.
     - Under "Location" choose where you want to save the project, this is recommended to be an easily accessible area.
     - Click "OK".

3) When all loads in, you should get a screen of code like this:
 
4) First, click "Project" at the top of the screen, then "Add Reference..".
     - A window will pop with a bunch of gibber jabber on it. Click the arrow next to "Browse".
     - At the bottom left, click "Browse.."
     - Once in Windows Explorer, navigate to your folder "References".
    - Hold the left control key and select both the files in the folder References (Rage SDK and LSPD DLL).
    - Make sure both boxes for the two files are ticked. Then, click "OK".

5) At the top of your code where everything says "using blahblah;". Replace all of those with the following lines below:
These basically state what references you're using, simple as that.
6) Over to the right, rename Class1.cs to Main.cs.
7) Then, you need to replace the code below the using statements with the following (explanations in the code, after "//"):
So this basically concludes our Main.cs file, all we have to do later on, as stated near the end of Main.cs above our method RegisterCallouts(), is register the callouts that we make, which we are about to do.
8) Next, we need to double click on "Properties" to the right. Under the dropdown box "Target framework:" select .NET Framework 4.6.
     - Then click Control+S and exit the Properties tab.

9) Over to the right, right click on ExamplePlugin and click "Add" then "New Folder", naming it "Callouts".
     - Then, right click on the "Callouts" folder, click "Add" then "Class..".
     - Name it whatever your callout name is, for this example we're going to be creating a simple "Pursuit in Progress" callout, so name it "PursuitinProgress.cs".

10) In it, use this code below:
Everything is explained in the code to help you out. I recommend you experiment with it to change things to your liking.
11) Now, go to Main.cs and under the RegisterCallouts() method you need to add the following:
12) Lastly, double click "Properties" to the right. Then, click "Build" to the left. Under "Platform Target:" select x64.
     - Thank you @Stealth22 for informing me of this!

Save and you're good to go! You got your first callout. You can ultimately expand upon this information I have provided with you to make your own unique callouts plugin!
     - To actually use the plugin, you have to click "Build" at the top of VS, click "Build Solution", make sure there are no errors, then go to wherever your project "ExamplePlugin" is located, go into bin > Debug. There you will find your references that were used and your "ExamplePlugin.dll". Drag and drop this file into GTA V > Plugins > LSPDFR and boot up GTA V! Also, if you want to quickly debug and make solving crashes easier, install "ExamplePlugin.pdb" to the same spot you installed ExamplePlugin.dll.

 
If you have any questions, please ask me!
If I forgot something or messed up something (as expected), please let me know.

Rather than pathetically snipping shit out thinking we're going to steal your code; just show us the line that is causing the crash and any lines that may interfere with that.