liverlande

Your plugins have filed a lot of the void left in the core LSPDFR modification, and I am very glad that you are choosing to open source so these plugins can be improved upon further. Thank you.

As far as I understand, police vehicle recognition is based on vehicle flags. Vehicle flags are stored in the vehicles.meta file, this post won't explain the specifics and assumes you can do this on your own. The following flags should enable police functions for LSPDFR (and by extension, the IsPoliceVehicle method in RAGEPluginHook):
 
FLAG_LAW_ENFORCEMENT FLAG_EMERGENCY_SERVICE  

Your plugins have filed a lot of the void left in the core LSPDFR modification, and I am very glad that you are choosing to open source so these plugins can be improved upon further. Thank you.

Your plugins have filed a lot of the void left in the core LSPDFR modification, and I am very glad that you are choosing to open source so these plugins can be improved upon further. Thank you.

Your plugins have filed a lot of the void left in the core LSPDFR modification, and I am very glad that you are choosing to open source so these plugins can be improved upon further. Thank you.

CalloutPacker is a work in progress plugin for LSPDFR 0.4 that allows you to choose which callouts can be called naturally through “callout packs”. This means that you can have a pack allowing all callouts, a pack allowing traffic related callouts, and so on. These packs are their own .xml files, which means they can be distributed by plugin developers for their own mods.
 
How It Works
The native callout dispatching system is disabled and replaced with one controlled by this plugin. Only callouts that are enabled are triggered. A chance modifier is planned for the future. 
 
The native available for calls functionality will be accounted for.
 
A menu is available in game to manage callout packs or enable/disable callouts for just the current session.
 
Estimated Release
This type of plugin involves a lot of different code to tie things together. I won’t be setting a release date in stone, but hope to have an initial stable release out before April. No promises.

OnCalloutNotAccepted is triggered. It's an override in the Callout class.

Being arrested and being cuffed are two different things in LSPDFR. BeingArrested is the stage where:
 
1) The takedown is initiated
2) The player starts holding down the E key
 
In the first case, the player could literally just stand there and aim their pistol at a grounded suspect - they'll still be counted as being arrested. Not sure if this is something you want. In this event, you could potentially be "arresting" multiple peds. The same is technically true for AI, but I don't think they're allowed to arrest multiple at once.
 
Assuming that is something you intend, there are no practical reasons the methods you gave wouldn't work. You could optimize further by maintaining a cache of Peds so you're not calling World.GetAllPeds every time. Mockup code with no such caching benefits:
 
https://gist.github.com/RiverGrande/6361b57bb5231762c75d127df5a4cb02
 
No one is forcing you to play or develop a modification developed for free by a group of individuals who reverse engineer a game with no real support from Rockstar Games. If you have issues with LSPDFR (and specifically the API, as this is the topic for the API), you should provide information so a patch can be introduced in a future update.

This thread can be used to post "snippets" - a small amount of code that is either almost or fully independent of the script it's used in. Unless otherwise specified, snippets hold the following terms:
 
Credit must be given to the author of the snippet if used in another project
Posting a snippet gives the above license for use
 
Snippets:
 
Name: RandomCallouts
Author: LiverLande
Description: Caches all callouts and adds a function for calling a random callout.
Requirements: LSPDFR 0.3.1
Link: https://gist.github.com/RiverGrande/d27b7506d5eb1372e53f1840a8a647c8
 
Name: WaitForDismissal
Author: LiverLande
Description: Monitors all stopped Peds and waits until they're dismissed.
Requirements: LSPDFR 0.4.0
Link: https://gist.github.com/RiverGrande/712b8678baf6b6365ffa8e9c56b63134
 
Name: OnScreenKeyboard
Author: NoNameSet
Description: Draws a keyboard on the users screen (used in such things as the cheat menu)
Link: https://gist.github.com/NoNameSet/33dbed309e48428e8b5d498fa15165fa
 
Name: SynchronizedScene
Author: NoNameSet
Description: Plays synchronized animations (animations that are meant to be used to play together, like the cuffing animation)
Link: https://gist.Github.com/NoNameSet/048d8d7bac259236c25f6280a9918ce0
 
Name: Trains
Author: NoNameSet
Description: A class to easily create trains 
Link: https://gist.github.com/NoNameSet/0a90a9652643c795abe30fb23c187640
 
Name: PursuitExtensions
Author: NoNameSet
Description: Pursuit extension methods
Link: https://gist.github.com/NoNameSet/046464b917b3bc8f181fe5c9e6fa1a85
 
Post with the following format to have a snippet added to the main post:
Name:
Author:
Description:
Link:
 
Using GitHub gists is recommended for ease of use and access - discussion regarding snippets is also allowed in this thread. The goal is to produce a valuable resource for developers to share code.

This thread can be used to post "snippets" - a small amount of code that is either almost or fully independent of the script it's used in. Unless otherwise specified, snippets hold the following terms:
 
Credit must be given to the author of the snippet if used in another project
Posting a snippet gives the above license for use
 
Snippets:
 
Name: RandomCallouts
Author: LiverLande
Description: Caches all callouts and adds a function for calling a random callout.
Requirements: LSPDFR 0.3.1
Link: https://gist.github.com/RiverGrande/d27b7506d5eb1372e53f1840a8a647c8
 
Name: WaitForDismissal
Author: LiverLande
Description: Monitors all stopped Peds and waits until they're dismissed.
Requirements: LSPDFR 0.4.0
Link: https://gist.github.com/RiverGrande/712b8678baf6b6365ffa8e9c56b63134
 
Name: OnScreenKeyboard
Author: NoNameSet
Description: Draws a keyboard on the users screen (used in such things as the cheat menu)
Link: https://gist.github.com/NoNameSet/33dbed309e48428e8b5d498fa15165fa
 
Name: SynchronizedScene
Author: NoNameSet
Description: Plays synchronized animations (animations that are meant to be used to play together, like the cuffing animation)
Link: https://gist.Github.com/NoNameSet/048d8d7bac259236c25f6280a9918ce0
 
Name: Trains
Author: NoNameSet
Description: A class to easily create trains 
Link: https://gist.github.com/NoNameSet/0a90a9652643c795abe30fb23c187640
 
Name: PursuitExtensions
Author: NoNameSet
Description: Pursuit extension methods
Link: https://gist.github.com/NoNameSet/046464b917b3bc8f181fe5c9e6fa1a85
 
Post with the following format to have a snippet added to the main post:
Name:
Author:
Description:
Link:
 
Using GitHub gists is recommended for ease of use and access - discussion regarding snippets is also allowed in this thread. The goal is to produce a valuable resource for developers to share code.

This thread can be used to post "snippets" - a small amount of code that is either almost or fully independent of the script it's used in. Unless otherwise specified, snippets hold the following terms:
 
Credit must be given to the author of the snippet if used in another project
Posting a snippet gives the above license for use
 
Snippets:
 
Name: RandomCallouts
Author: LiverLande
Description: Caches all callouts and adds a function for calling a random callout.
Requirements: LSPDFR 0.3.1
Link: https://gist.github.com/RiverGrande/d27b7506d5eb1372e53f1840a8a647c8
 
Name: WaitForDismissal
Author: LiverLande
Description: Monitors all stopped Peds and waits until they're dismissed.
Requirements: LSPDFR 0.4.0
Link: https://gist.github.com/RiverGrande/712b8678baf6b6365ffa8e9c56b63134
 
Name: OnScreenKeyboard
Author: NoNameSet
Description: Draws a keyboard on the users screen (used in such things as the cheat menu)
Link: https://gist.github.com/NoNameSet/33dbed309e48428e8b5d498fa15165fa
 
Name: SynchronizedScene
Author: NoNameSet
Description: Plays synchronized animations (animations that are meant to be used to play together, like the cuffing animation)
Link: https://gist.Github.com/NoNameSet/048d8d7bac259236c25f6280a9918ce0
 
Name: Trains
Author: NoNameSet
Description: A class to easily create trains 
Link: https://gist.github.com/NoNameSet/0a90a9652643c795abe30fb23c187640
 
Name: PursuitExtensions
Author: NoNameSet
Description: Pursuit extension methods
Link: https://gist.github.com/NoNameSet/046464b917b3bc8f181fe5c9e6fa1a85
 
Post with the following format to have a snippet added to the main post:
Name:
Author:
Description:
Link:
 
Using GitHub gists is recommended for ease of use and access - discussion regarding snippets is also allowed in this thread. The goal is to produce a valuable resource for developers to share code.

You should be able to detect this by waiting until Functions.IsPedStoppedByPlayer returns false (run this check in a separate thread). This won't work correctly with StopThePed since it uses its own functions and not the LSPDFR API. StopThePed might offer other functions through its own API for you to integrate.
 
Example untested module that you can expand on:
https://gist.githubusercontent.com/RiverGrande/712b8678baf6b6365ffa8e9c56b63134/raw/dae92b3542fdb43a0b77b006bd84a489840767ec/WaitForDismissal

Great idea. I was actually experimenting with something related to callouts and have a pretty good base I can use for something like this. I'll see what I can come up with 🙂
 
Edit
 
 

CalloutPacker is a work in progress plugin for LSPDFR 0.4 that allows you to choose which callouts can be called naturally through “callout packs”. This means that you can have a pack allowing all callouts, a pack allowing traffic related callouts, and so on. These packs are their own .xml files, which means they can be distributed by plugin developers for their own mods.
 
How It Works
The native callout dispatching system is disabled and replaced with one controlled by this plugin. Only callouts that are enabled are triggered. A chance modifier is planned for the future. 
 
The native available for calls functionality will be accounted for.
 
A menu is available in game to manage callout packs or enable/disable callouts for just the current session.
 
Estimated Release
This type of plugin involves a lot of different code to tie things together. I won’t be setting a release date in stone, but hope to have an initial stable release out before April. No promises.

Great idea. I was actually experimenting with something related to callouts and have a pretty good base I can use for something like this. I'll see what I can come up with 🙂
 
Edit
 
 

Great idea. I was actually experimenting with something related to callouts and have a pretty good base I can use for something like this. I'll see what I can come up with 🙂
 
Edit
 
 

Functions.StartCallout takes a string parameter, this is the name specified in CalloutInfo. To achieve this, we have to get this name from all available callouts. We can do this by searching through all assemblies with a base type of Callout, retrieving the name specified in CalloutInfo, and caching it into a list of strings. When we want to trigger a random callout, we access this list and randomly choose a string with no conditions. Credit goes to Stealth22, he (as far as I know) wrote the base code for going through all callouts that I've made use of here. Gist is below with untested mock up code that should theoretically work:
 
https://gist.githubusercontent.com/RiverGrande/d27b7506d5eb1372e53f1840a8a647c8/raw/a71c93eb007f9b35e3b1e376026624507779f40e/RandomCallouts.cs

Functions.StartCallout takes a string parameter, this is the name specified in CalloutInfo. To achieve this, we have to get this name from all available callouts. We can do this by searching through all assemblies with a base type of Callout, retrieving the name specified in CalloutInfo, and caching it into a list of strings. When we want to trigger a random callout, we access this list and randomly choose a string with no conditions. Credit goes to Stealth22, he (as far as I know) wrote the base code for going through all callouts that I've made use of here. Gist is below with untested mock up code that should theoretically work:
 
https://gist.githubusercontent.com/RiverGrande/d27b7506d5eb1372e53f1840a8a647c8/raw/a71c93eb007f9b35e3b1e376026624507779f40e/RandomCallouts.cs

Your plugins have filed a lot of the void left in the core LSPDFR modification, and I am very glad that you are choosing to open source so these plugins can be improved upon further. Thank you.

Your plugins have filed a lot of the void left in the core LSPDFR modification, and I am very glad that you are choosing to open source so these plugins can be improved upon further. Thank you.

You are not going to be forced to upgrade your game installation to LSPDFR 0.4. In fact, I personally recommend people with free hard drive space back up their LSPDFR 0.3 game in full and maintain a LSPDFR 0.4 installation in a new, clean folder. This way you can go back to LSPDFR 0.3/0.4 with a folder rename.
 
Some mods most likely will become obsolete, which isn't necessarily a bad thing. Some mods (specifically, LSPDFR plugins) may break when used with LSPDFR 0.4. It'd be on the specific developer to address the compatibility issues with the new API. Hopefully a majority of callout type plugins will at least stay compatible with basic functionality, especially the old ones with inactive developers. No way to know yet.
 
All in all, this is a great chance to redo your game and get things how you want them again. The update most likely won't be plug and play for the aforementioned reasons, but this isn't necessarily a bad thing.

Going on a cursing rampage and demanding that you be assisted because you're oh so special is not how lcpdfr.com works. Everyone who helps out on these forums is volunteering their time and effort to help you with problems that have more than likely been resolved elsewhere and are accessible on Google. There is no secret agenda to set you back in doing things that are straight forward and naively supported by the game, and there most certainly is no obligation for anyone to help you at all.
 
The most ludicrous part of this response is that your tirade began a mere 4 hours after you posted this topic, not even a whole day passed. Since you're so adamant about having a proper SDK (which by the way, all three of your questions aren't even related to the LSPDFR API. RAGEPluginHook isn't a product of G17 Media), you surely can make your own extensions for RAGEPluginHook that do what you want how you want. Not good enough? Make your own hooking system that is everything you've ever dreamed of. If you are not up to such task, I strongly advise you to use resources such as Google and NativeDB and make do with the freely available systems that have been developed and made available for free. This topic will more than likely be locked due to your behavior.
 
P.S:  Being toxic is not going to magically make people help you (in case you haven't understood that part yet). Don't bother releasing anything on these forums if this is how you plan on acting. There are other places you can do that.

Going on a cursing rampage and demanding that you be assisted because you're oh so special is not how lcpdfr.com works. Everyone who helps out on these forums is volunteering their time and effort to help you with problems that have more than likely been resolved elsewhere and are accessible on Google. There is no secret agenda to set you back in doing things that are straight forward and naively supported by the game, and there most certainly is no obligation for anyone to help you at all.
 
The most ludicrous part of this response is that your tirade began a mere 4 hours after you posted this topic, not even a whole day passed. Since you're so adamant about having a proper SDK (which by the way, all three of your questions aren't even related to the LSPDFR API. RAGEPluginHook isn't a product of G17 Media), you surely can make your own extensions for RAGEPluginHook that do what you want how you want. Not good enough? Make your own hooking system that is everything you've ever dreamed of. If you are not up to such task, I strongly advise you to use resources such as Google and NativeDB and make do with the freely available systems that have been developed and made available for free. This topic will more than likely be locked due to your behavior.
 
P.S:  Being toxic is not going to magically make people help you (in case you haven't understood that part yet). Don't bother releasing anything on these forums if this is how you plan on acting. There are other places you can do that.

Grande Callouts is an LSPDFR plugin which aims to add a variety of different callouts of no distinct category. This plugin does not aim to add lengthy or otherwise complex callouts, the majority will be quick service calls that are resolved mostly through already existant game scripts and mechanisms.
 
Callouts:
Green - Stable, works in game
Yellow - May or not be stable, a prototype is in the script
Red - Not scripted, but is planned.
 
Law Agency Assist: Distress Call
Tow Truck Operator Assist
Medical Emergency Assist: Heart Attack
Medical Emergency Assist: Stabbing
 
Current Prerequisites:
LSPD First Response 0.3.1 - The base LSPD First Response modification is required for use.
RAGEPluginHook 0.51+ - This plugin will only work with RAGEPluginHook 0.51+ or above.
Legal version of Grand Theft Auto V - This plugin will only work with legal copies of Grand Theft Auto V.
 
Compatible Plugins:
I believe that good plugins should be compatible with any variety of additional scripts. All plugins listed here are optional, meaning this plugin will work without them. Some functionality may not be offered without these plugins, however.
ComputerPlus+: this plugin is used to store information relevant to the current (and past) callouts triggered by this lugin. "Status Updates" may be provided throughout the course of the call.
 
Additional Features and or Things To Brag About:
Smart Exception Handling: A majority of possible exceptions will be caught by the script in the event that they do occur. Where possible, exceptions will be recovered from. For all exceptions (even those not caught locally), a variety of exception information will be printed to the RAGEPluginHook log file. Some exceptions can not be recovered from.
Configurable Settings: Self explanatory and expected. There are some settings you can configure, such as what callouts to enable, minimum and maximum spawn distance for callouts, keybindings, and more.
Minimal Performance Impact: This plugin is designed with performance and CPU use in mind. Separate threads are used where applicable, continual processes are only run when necessary.
Hopeful Consistency: My goal is to keep this plugin consistent where possible. This means keeping the script organized and using uniform functions across callouts and other parts of the plugin. This brings the benefit of being able to introduce modifications to the plugin with relative ease, including adding new callouts.
 
What I Want From You:
What do you want to see from a plugin such as this? Do you have any ideas for callouts or other scripts that can be added in? Are there any released plugins that could add additional functionality (note: these plugins must provide sufficient APIs)? Would you rather variables such as amount of suspects, vehicle models, et cetera be hardcoded, or would you rather be able to configure such variables through an .xml file?
 
Release Date:
TBA
  

I don't imagine anything would prevent you from playing LSPDFR 0.3 once LSPDFR 0.4 is released. That said, it is equally likely that a majority of the plugins you have installed (along with LSPDFR and G17 Media, who probably won't ever update 0.3 again) and may not release updates compatible with 0.3 down the line. These developers may also not support these legacy versions.