420Chuur

I use a extension class specifically for markers. I can't remember where I found it , Was on google somewhere. I did look again but couldn't find the author. I take no credit for this class & if anyone knows who created it please let me know so I can credit them.
 
 

First of all you would create a new class named say Marker.cs.
Put the code in that spoiler in there and rename to your namespace (where it says YourProjectName).
Then from that point in a callout you can use Marker1 = new Marker(); With your parameters.
Marker1.Visible = true;
 

A issue I have found is when concluding a pursuit , The number of suspects apprehended is never correct. E.G I Pursued a baller with 4 occupants, They stopped 2 of them got out , started shooting ,one was killed the other surrendered. The other 2 were ripped out of the vehicle and apprehended. Never the less, In the notification , Suspects Apprehended = 6. 😕 Suspects killed = 1.

It is certainly something we are thinking about, however, we will need to figure out a few things first, such as limiting abuse (which will require some backend engineering), before we will make a decision on how (or whether) we make the sync services available via API.

Will LSPDFR sync related features be added to the API at some point in the future? It would be cool for callouts/plugins to be able to add their own stats and activities to the activity feed. E.g. "Bob Vance just freed 5 hostages at the Pacific Standard Bank", "EMS just saved 2 people on Vespucci Boulevard... sadly, 3 people did not make it", etc. 

A issue I have found is when concluding a pursuit , The number of suspects apprehended is never correct. E.G I Pursued a baller with 4 occupants, They stopped 2 of them got out , started shooting ,one was killed the other surrendered. The other 2 were ripped out of the vehicle and apprehended. Never the less, In the notification , Suspects Apprehended = 6. 😕 Suspects killed = 1.

Not sure what this has to do with LSPDFR 0.4, but I will say that considering how much @Albo1125 has given the whole community with his work, I think this comment is in poor taste.

Don't be so rude and quick to judge! Some people have difficulties with language, such as dyslexia. Not everything can be taken at face value.

Np, Although all the info I gave you can be found from google 😄 . You may want to take a look at this post here:  https://gtaforums.com/topic/808513-changing-ped-clothes-and-attaching-props-to-ped-via-scripts/, Down where it says props.

Instead of asking for handouts and complaining when you don't get them, why don't you try looking yourself? I don't code at all and it took me 5 minutes to find a native you can try for props. Most people who develop for GTA learn based on experimentation. Try something, if it doesn't work, try something else. Google is your friend. You won't learn anything new by asking for people to do the work for you.
 
 

You could use one of the natives,  ADD_AMMO_TO_PED(Ped ped, Hash weaponHash, int ammo), 
SET_PED_AMMO(Ped ped, Hash weaponHash, int ammo)

Ok for a start 1: These are the natives for ptfx, this will make the purple clown appears smoke.
NativeFunction.Natives.REQUEST_NAMED_PTFX_ASSET("scr_rcbarry2");
NativeFunction.Natives.x6C38AF3693A69A91("scr_rcbarry2"); // _SET_PTFX_ASSET_NEXT_CALL
NativeFunction.Natives.START_PARTICLE_FX_NON_LOOPED_AT_COORD<uint>("scr_clown_appears", Game.LocalPlayer.Character.Position, 0, 0, 0, 5.5f, 0, 0, 0);

2: Why not just give a new weapon and set the amount of ammo there?IGame.LocalPlayer.Character.Inventory.GiveNewWeapon(WeaponHash.Pistol, 9999, true);
 
3: Why not use EUP Menu, That way you can choose,save & load your custom outfits with or without sunglasses , police hat ect...
 
Do you expect people to go through every post on these forums hourly? 😄 
Maybe joining the RPH Discord channel would be more appropriate.
ALSO, People care if you curse because your just wasting space in a post. 
Everyone has an opinion, People just need to learn there's a time and a place to voice it :). & Here is not it 😜 

Looks absolutely stunning.
 
Can't wait to reload the lcpdfr page 5 times a day in February ^^

As LSPDFR 0.4 nears completion, we hope this topic will help in providing some clarification for developers who make use of our API about what the changes in 0.4 mean for them and their work.
 
Firstly, the significance of the changes to LSPDFR that 0.4 brings can't be overstated.  LSPDFR 0.4 introduces changes to almost every aspect of the mod and will take a little getting used to.  We think that the overall experience is much improved from 0.3, and a lot of the features that we introduced in 0.3, or earlier versions, have been dramatically changed, expanded upon or entirely re-worked.  It's important to keep this in mind as such drastic changes will unavoidably have the potential to cause issues across the board.
 
In regards to our current approach, our main priority at this time is to release a public version of LSPDFR 0.4 as soon as is possible.  In short, this means that our focus is and has been very much on the core experience of the mod.  As a result, while we will still ship the first public release of LSPDFR 0.4 with a functioning API, it will not be substantially different from the current LSPDFR 0.3 API.  Additionally, we are committed to ensuring that custom callout plugins remain compatible with LSPDFR 0.4.
 
We understand that this approach might cause some initial disappointment, but we think it is the most sustainable way of doing things both in terms of people being able to play 0.4 as soon as possible (which obviously is very important), but also from an API and development perspective.  As said above, a lot has changed in 0.4 and we want developers to have the opportunity to properly familiarise themselves with the new version and get a feel for what sort of content they'd like to create and what sort of things they'd like to change.  
 
Just like with previous versions of LSPDFR, we are committed to pushing post-release updates and hotfixes for 0.4, with a view to following up with a minor 0.4.1 version, which will focus primarily on extended API functionality.  During this process, we will work with developers to incorporate their suggestions and requests for the 0.4.1 API, and will also provide development builds of 0.4.1 to developers for testing.

Im just wondering if this is still being worked on as I haven't seen anything relating to it in the past 6 months? 

Im just wondering if this is still being worked on as I haven't seen anything relating to it in the past 6 months? 

Im just wondering if this is still being worked on as I haven't seen anything relating to it in the past 6 months?