Whenever I play LSPDFR, I always receive a certain type of callout more than others due to the callout probability being set to high or very high. I am usually itching to get another callout which I have not seen in a long time.

In real life, certain callouts do occur more than others, however I feel like it can get boring for the typical player as they experience the same thing being repeated over and over again. I am suggesting that we limit the probability to low, medium, and maybe high? It will create a more diverse playing experience.

What are the opinions of players and devs on this topic?

Edited July 2, 20169 yr by tanu1215

I like the concept, but its the kind of thing that'll get broken too easy to be worth it IMO. It'll end up with most devs rating their callouts appropriately, then one guy comes along, copy-pastes the API example and sets it to very high/always and the rest of us never see our callouts again :P

i agree with Darkmyre Some dude makes a new callout for us and like he says changes the API and boom more of those callouts than Agency and CalloutsV i hardly ever get a Pursuit of Armed Suspects call anymore due to the many other callouts i downloaded but i would like to one day see some progress on that concept someday 

17 minutes ago, Darkmyre said:

I like the concept, but its the kind of thing that'll get broken too easy to be worth it IMO. It'll end up with most devs rating their callouts appropriately, then one guy comes along, copy-pastes the API example and sets it to very high/always and the rest of us never see our callouts again :P

 

 

2 minutes ago, LapdCode3 said:

i agree with Darkmyre Some dude makes a new callout for us and like he says changes the API and boom more of those callouts than Agency and CalloutsV i hardly ever get a Pursuit of Armed Suspects call anymore due to the many other callouts i downloaded but i would like to one day see some progress on that concept someday 

Yes these are good points. Maybe options other than low, medium, high can be removed from the API entirely? That way, there won't be a way for it to get broken, as developers will have to select from only three options.

wont that affect the callouts during updates and such?

I agree with OP. 

An idea came to my mind (dunno if that's doable as of now, but will look into it myself): each callout should have a probability configuration (ini).
Therefore each player could decide the probability of each individual callout.

Maybe we could also find a way to centralize everything, to avoid having 1 ini file for each callout.
Like, each callout could hook onto it, and if the probability isn't defined in that centralized ini, it sets a default value (Low/Medium for instance)

EDIT: seems like @Albo1125 already did this with TrafficPolicer (just checked all the ini files from the plugins I have :p)

EDIT 2: user linking is broken, or I don't know how to do it ^^

Edited July 2, 20169 yr by liberto

Realistically, as mentioned above.. There's no way to have a centralized consistency because anyone can mark their callouts as high. We should create a shared library (similar to the update manager plugin) which plugins can participate in.. Then we can manually trigger each callouts based on randomness without a weight on priority.

 

Edit: tagging @Darkmyre

Edited July 2, 20169 yr by ainesophaur

I think it's worth educating developers more than making yet another shared library everyone has to update every week. Perhaps this is something that can be fixed at the LSPDFR level.

Most of mine are set to medium...I've got a couple at Low and one or two at High.

All of mine are set to High. When I'm playing I do feel like quite a few of mine don't come up very often and I do get the same ones over but that's the luck of the draw.

I agree with Cyan on this one, we already have too many extra files people need in the form of common libraries and such, honestly if you install everyone's plugins your GTA V directory might as well replace the System32 folder.

I also don't think everyone filling their config files with custom probabilities is a good idea. There's no consistency there. The LSPDFR system exists for a reason, so I would recommend working with it rather than trying to overrule it.

All of my callouts are set to medium, they have been since day 1. I see no reason for anybodies callouts to go higher than medium probability personally. They definitely shouldn't be set to always under any circumstance.

If you set your callouts to medium everyone gets a reasonably fair chance at them showing up. Use low for callouts which you wouldn't expect to happen every few minutes (unless you're planning on directing a GTA V film with michael bay.....Khorio...)

 

Something critical for the developers out there. Remember that LSPDFR is primarily aimed at normal policing. It isn't a new SWAT game, it isn't Call of Duty, it's routine policing. It's putting on your uniform, jumping in your car and responding to things which would be your every day 911 calls or having a good eye for someone who can't keep their car within the road markings.

I think this point is vital for those of you making callouts aimed at different things, agency callouts, swat callouts, wildlife callouts. (Just to name a few that stand out)
It's important for players too, if you're running 3 different plugins for normal callouts and then also a swat callout pack then you should probably be expecting an unbalanced set of callouts.

 

I think perhaps a good discussion on what we all consider the probabilities mean would be helpful, that could then be used to produce some form of document/guide that shows what kind of callout belongs to which category

e.g. Bomb threat at airport: low. (because it's not a regular everyday police activity)

14 hours ago, Stealth22 said:

Most of mine are set to medium...I've got a couple at Low and one or two at High.

Same here.

On 7/2/2016 at 5:59 PM, Cyan said:

I think it's worth educating developers more than making yet another shared library everyone has to update every week. Perhaps this is something that can be fixed at the LSPDFR level.

I agree.

13 hours ago, Albo1125 said:

Same here.

I'm not sure you can claim all your callouts are set to Medium, when you allow users to change probability in your INI that affects the number of times you register your callouts. Kinda defeats the point of even bothering to use the probability IMO, and definitely isnt the same as registering all your callouts once at Medium.

16 hours ago, LukeD said:

Something critical for the developers out there. Remember that LSPDFR is primarily aimed at normal policing. It isn't a new SWAT game, it isn't Call of Duty, it's routine policing. It's putting on your uniform, jumping in your car and responding to things which would be your every day 911 calls or having a good eye for someone who can't keep their car within the road markings.

I think this point is vital for those of you making callouts aimed at different things, agency callouts,

Since you decided to target my callout pack for no reason, can you explain to me how exactly having different callouts being the responsibility of different police departments, like is the case in real life, is "abnormal policing"? If this is abnormal, why doesn't America just have one singular department that handles everything?

23 minutes ago, Darkmyre said:

Since you decided to target my callout pack for no reason, can you explain to me how exactly having different callouts being the responsibility of different police departments, like is the case in real life, is "abnormal policing"? If this is abnormal, why doesn't America just have one singular department that handles everything?

I wasn't targeting your callout pack. Let's get this clear right now my previous post has nothing to do with calling anyone out for making the wrong thing.

My point is that LSPDFR follows on from LCPDFR, which means it likely has the same design theme that LCPDFR did. That was beat patrol policing, that's why you can do traffic stops rather than arrange your police partners for a tactical sweep on a factory. It wasn't designed to run as a basis for all things policing, it's not filling out paperwork simulator in the same way that it isn't designed for the aforementioned plugins. That being said, LSPDFR is still young so who knows, maybe we will see changes to better suit the multiple police roles allowing you to choose police work based on the model you pick in the locker room.

I'm not saying anything about people's plugins not being policing. This has nothing to do with the content of your plugins. I am literally saying the underlying principle behind LSPDFR is for ordinary every day street police work, so take that into consideration as well when you're playing with multiple different plugins.

And the fact you guys make these different plugins is great, we know from LCPDFR that people wanted different aspects of policing. You are giving that to them. So again, maybe LSPDFR will grow to better suit that in the long run.

Is this more clear now? I will never attack you guys for your callouts, it was just a name of one that sprung to mind to help get my point across. I hope this make it more clear I really do, but if you're still not happy about it you can reach me privately on the Discord. I am more than happy to chat with you about it. Just know that I am not targeting or attacking anyone.

3 hours ago, Darkmyre said:

I'm not sure you can claim all your callouts are set to Medium, when you allow users to change probability in your INI that affects the number of times you register your callouts. Kinda defeats the point of even bothering to use the probability IMO, and definitely isnt the same as registering all your callouts once at Medium.

By default, the settings all accommodate the default Medium probability.

The INI setting is there to allow users to 'force' a specific callout (e.g. Bank Heist, which is set to very low by default). Back when I created all of those, LSPDFR didn't have any kind of API function to force callouts. Because I set my callouts to such a low probability by default to maintain realism and lots of other callouts are being set to higher probabilities, mine occur very rarely if a user has multiple callouts installed.

I consider it a good thing to have for user customisation - which is something entirely different than using the default settings and using the default probability.

Edited July 4, 20169 yr by Albo1125

On 7/3/2016 at 0:39 PM, LukeD said:

I agree with Cyan on this one, we already have too many extra files people need in the form of common libraries and such, honestly if you install everyone's plugins your GTA V directory might as well replace the System32 folder.

I also don't think everyone filling their config files with custom probabilities is a good idea. There's no consistency there. The LSPDFR system exists for a reason, so I would recommend working with it rather than trying to overrule it.

All of my callouts are set to medium, they have been since day 1. I see no reason for anybodies callouts to go higher than medium probability personally. They definitely shouldn't be set to always under any circumstance.

If you set your callouts to medium everyone gets a reasonably fair chance at them showing up. Use low for callouts which you wouldn't expect to happen every few minutes (unless you're planning on directing a GTA V film with michael bay.....Khorio...)

 

Something critical for the developers out there. Remember that LSPDFR is primarily aimed at normal policing. It isn't a new SWAT game, it isn't Call of Duty, it's routine policing. It's putting on your uniform, jumping in your car and responding to things which would be your every day 911 calls or having a good eye for someone who can't keep their car within the road markings.

I think this point is vital for those of you making callouts aimed at different things, agency callouts, swat callouts, wildlife callouts. (Just to name a few that stand out)
It's important for players too, if you're running 3 different plugins for normal callouts and then also a swat callout pack then you should probably be expecting an unbalanced set of callouts.

 

I think perhaps a good discussion on what we all consider the probabilities mean would be helpful, that could then be used to produce some form of document/guide that shows what kind of callout belongs to which category

e.g. Bomb threat at airport: low. (because it's not a regular everyday police activity)

Personally I did the same thing as well.  Secondary Callouts has a lot of callouts at low, and a couple at very low (or whatever it is).  I would rather someone play and be excited when they see my callout pop up than someone play and see mine pop up all the time (like knife attack is medium, but officer shot is very low).

I personally think that high and always should be removed -- you should never get a callout that often.

On 7/5/2016 at 2:34 AM, Fiskey111 said:

Personally I did the same thing as well.  Secondary Callouts has a lot of callouts at low, and a couple at very low (or whatever it is).  I would rather someone play and be excited when they see my callout pop up than someone play and see mine pop up all the time (like knife attack is medium, but officer shot is very low).

I personally think that high and always should be removed -- you should never get a callout that often.

Always shouldn't be removed, its too useful for development, maybe restrict it to debug.
I also used medium/low at the start, until people started complaining all the time about never getting the callouts (which is the whole reason i added a force callout option in the end)
A different police dep setting in lspdfr would be very useful, maybe if 0.4 ever comes out :)