Stealth22

No worries, whenever you get to it.

Did you set the relationship to hate in both directions? (On both peds)

I've started on the API namespace, and I took a copy of the ped database form, just to use it as a dummy callout form. I committed what I've got to the Git repo. I'm not done with the API classes yet, though. @AlconH, keep me posted on the server stuff. I can help with the database design. I've created a channel on Discord to discuss anything related to this project which we want to keep within developers. PM me for access if you're a developer who is either working on this project, or involved in any planning or discussion. (Albo, I sent you a friend request on Discord)

Yeah, I'll be adding a bit of that sort of stuff to the Git project.

Sweet, so its even easier than I thought. Ball is in your court, @PieRGud! Let me know if you get stuck. Once your classes are done, I can give them a test with Code 3 Callouts.

GitHub for open source, or VSO (Visual Studio Online, which runs Microsoft TFS, or Team Foundation Server) for closed source.

Like I said, that would be way long term, lol. Much to do before we can get to that stage. Start with the API classes, and we'll go from there.

Either way works, really. It comes down to personal preference. But yeah, start on your classes and functions first. Once you've got them built, we'll have a starting point to work from. At a minimum, I would have at least one class (CalloutDetails), one function for passing in details from a callout, and perhaps functions to add entities to the current active callout. For example, as a callout progresses, the developer can pass in more peds, vehicles, or add details to the notes. The notes property could even be a List of Note objects, which would be a class/struct containing a string for the note text, and maybe a Date for when it was added. EDIT: If you really want to get fancy (this would be like Phase 10, though), you can re-produce fiskey's report functionality, and each time a player writes a report for a callout, the details of the call, who was involved, who was arrested, etc can all get logged into a SQLite database. SQLite is file-based, and the db would be stored in the LSPDFR directory. So say you arrest "Bob Smith" for assault, and then pull him over 3 days later, your computer pulls up the details and tells you that Bob Smith has a prior arrest for Assault. Cool, huh?

Its really just a matter of exposing the classes and functions (i.e. make them public) that you want to offer. However, after that, I think that you need to ensure the plugins are running in the same AppDomain, but I am not sure. That is where my knowledge starts to get cloudy on the subject. But since @Albo1125 has done it, he can definitely answer that. (Have I tagged you enough times in this thread, Albo? lol) You could start by creating an API namespace, and create, say a public CalloutDetails class with various properties. For example, it would have a string for the callout name, another for the briefing/synopsis, a Date field for when the call was dispatched, etc. It could also have List properties for Peds, Vehicles, or even allow the officer to add notes to the call. Then you'd have a static instance of your CalloutDetails, and set it to null. Create a function in your API namespace which accepts a CalloutDetails parameter, and set your static instance to that parameter. (EDIT - Or actually, the function would accept several parameters, one for each of the properties of CalloutDetails. Then you populate your shared instance with the properties that were passed in. That would be cleaner.) The computer checks to see if the static CalloutDetails is null, and if it isn't, you can click the button to display the callout details. I would start on that, and then let Albo help you on actually exposing it properly.

Like I said, that part is up to you guys. But for the purposes of this discussion, callout integration would probably be limited to your computer project. It would be great to have the reporting aspect too, but I don't want you to re-invent the wheel if he already has something built, that's all I am saying. The more I think about this, the more I am thinking it's doable. The easiest way would be for you to build an API into LSPDFR Computer+. I haven't done such a thing yet, so I'm not 100% sure on how. I may be able to figure it out eventually, but @Albo1125 has already done it more than once. Albo, if you're willing to help out, I can see this getting off the ground (at a basic level) pretty quickly. For instance, just to get started, we could re-create the functionality I've built into Code 3 Callouts, where you get a synopsis of the call, and that's it. We can build it further from there. It would be fairly simple...you'd have a button called 'Call Brief' or something similar. If a callout isn't active (there is already a function in the LSPDFR API called "IsCalloutRunning" that tells you if a callout is active), the button is disabled. If there is, then the computer checks to see if the active callout has passed it any details. If so, the button enables, and you can open the callout details form. If not, the button is still disabled. When the callout is over (i.e. when IsCalloutRunning returns false), then the details object gets cleared or set to null, and the button disables itself again. In theory, this is actually fairly easy to get started on. The most difficult part is probably building the API, which Albo can help you out with anyway. This is something that is not that difficult to build, but has a huge impact, and opens a whole new level of immersion.

@PieRGud and @fiskey111, you guys will want to read this. Same goes for all the developers, callouts or otherwise... @Albo1125, @Darkmyre, @alexguirre, @goigle, @LukeD, @FinKone, and the rest of you. (There are too many to name! @LMS and @Sam, I wouldn't mind having your input as well.) I stumbled upon a video by FirstThirtyMinutes where he was testing out PieRGud's Computer+ plugin. I only got a few seconds into the video before I let out a 'Wow'. I then found fiskey's MDT in the downloads section, and was equally impressed. First off, before I go any further, you guys are doing some good work. A police computer has been on my list of things to do for a while...but the timeline on that list is 'sometime between now and later', which for all intents and purposes, means practically never. So I am glad that both of you were able to get something going. Now, the reason I'm writing this...@PieRGud, I just had a brain wave when I saw that video. What if there was a way to integrate callouts into your police computer? I mean like, when you get a call, all of the details are transmitted to the computer, just like in real life. You can enter names of subjects, and attach them to the call. Dispatch would enter a synopsis of the situation, which (and this is up to the developer of the callout) may or may not be correct. Because as you all know, police officers rarely get much information (or correct information!) when going to a call. This functionality would flow with the rest of the functions you've already built...looking up names and such. Personally, I think that you and @fiskey111 should combine your efforts into LSPDFR Computer+. Whether you guys decide to or not, is up to you. But if you combine fiskey's reporting stuff into your computer project, you could have players write reports about the calls they attended. If you go on a ridealong with a police officer, you'll notice that he or she will sit at a scene (or parked nearby) long after the situation is over. They're sitting in the cruiser, writing a report on their laptop. Now before we get too excited, I am not sure if any of this is possible. I vaguely recall there was some discussion about LSPDFR plugins talking to one another, and @Albo1125 has successfully built an API into Traffic Policer. What if we do the same thing with LSPDFR Computer+? LMS and Sam haven't got the time (correct me if I am wrong, guys!) to build in API functions for us to get callout entities, and its likely a waste of effort. But if we could create an API for the police computer, callout devs could hook into it, and pass in all the details of the call, ped objects, etc into the police computer. The computer then displays that information, but of course, the player has to be in their vehicle in order to do any of this!! (Some departments may use portable tablets, but personally, I think it should all be restricted to the car, but that's a discussion for another time) We would essentially be creating a real, bonafide, CAD (computer aided dispatch) system. And not the fake one that I've got in Code 3 Callouts now, which is just a popup. What do you guys think? Any thoughts?

I put this as a request in the GitHub repo, but I thought I'd post it here too. I'm not sure if there's already a way to do this programmatically, but it would be nice if there was a function we could call that would put a ped into that 'stopped' state where you can interact with them. Like when you hold 'E' to stop a ped, or when you ask a driver to step out of their vehicle. You can either interact (ask for ID/cite/warn) with them by pressing 'E', or place them under arrest by holding 'E'. Can we have a function that would do this? I found SetPedAsArrested(Rage.Ped) in the API namespace, but I don't think that does the same thing, based on the name of the function. (I haven't tried it yet, though.) @LMS?

Not much in the way of new features...just improvements to the existing callouts more than anything. For example, @Polecat324 made a pretty good point in one of his recent videos. He responded to a Person with a Firearm call, and he got next to no information when he arrived. He was searching the area on foot, and the suspect escaped before he could really do anything. So my apologies for that, Polecat! I promise I'll improve that callout, just for you! As for the ideas you mentioned... Gang related callouts - These are covered (to an extent, at least) by other callout packs. I could perhaps look at doing something for this...but its difficult to come up with a gang callout that wouldn't just result in a shootout. Same goes (to an extent) for the drug related stuff as well. Nuisance crimes - I know the urination one is covered already by someone else. I could MAYBE do disturbing the peace...but all of this being said, these callout ideas would be something long term, added down the roads Vehicular assault - Covered (mostly, anyway) by the hit and run and road rage callouts.

You could write your own extension method that would do this.

I just thought this up in my head, but I doubt it's an efficient method of accomplishing this. You could get a list of nearby vehicles (sort the list by distance with a LINQ query), and then calculate the heading to each vehicle, and compare each value to the player's current heading. You could accomplish this with a LINQ query or two, but it may not be very efficient.

VERSION 1.0.0 HAS BEEN RELEASED! Updated pre-requisite DLL's (Plugin will refuse to run without these!) RAGEPluginHook v0.38+ LSPDFR v0.3.1+ RAGENativeUI v1.3.1+ (Included) Stealth.Common DLL v1.6.0.1+ (Included) Fixed bugs in the Road Rage and Impaired Driver calls that would cause an LSPDFR crash Added more variety to the 'Person With a Firearm' call NEW CALLOUT!! Burglary in Progress - You have to enter a house, and search each room for the suspect!! This call can spawn almost anywhere on the map, at around 120 unique houses and apartments! NEW FEATURE - Interaction menu, which allows you to interact with peds. You can ask them for ID, and even question them! (See documentation) Many thanks to @Century and @forsakenbacon17 for helping me gather residential locations for the Burglary call!! Many thanks to @Bayareabuggs and @JFavignano for testing the Burglary call, and helping me fix things that were broken!