thatmaxplayle

I would highly suggest you do this. Loading ScriptHookVDotNet into the RPH AppDomain isn't a very good idea. Somebody has kindly sorted out converting your code for you. It's a relatively simple change, but will go a long way. A little while back, I teamed up with a couple of other developers to create a "base LSPDFR plugin repository" for you to reference from. Feel free to use this code as an example, in expansion to what has been posted above: https://github.com/thatmaxplayle/LSPDFRBasePlugin/blob/master/LspdfrBasePlugin/Settings.cs If you do implement any of this code, please however credit myself and Rich.

No - they aren't. You can use the Rage.InitializationFile in RPH to do this.

Completely out of interest, why are you depending on SHVDN and SHV? There's very little (if anything) that SHV/SHVDN can achieve that LSPDFR cannot. I've had multiple support requests from people using this pack having issues due to the lack of SHVDN. Of course, that is their doing because it is listed as a dependency, but I just wanted to ask why you're referencing these libraries which shouldn't be required in an LSPDFR plugin.

Take a look at this showcase video for an early version of one of the new features coming in the next update: https://www.youtube.com/watch?v=uLA84d8mzeE%2F

i'm not dead. there is content coming. don't worry.

I'm gonna go ahead and go with the blind option, especially considering this question has been answered 200 times on this thread already... Plugins\LSPDFR\Section136Callouts\mainconfig.xml

100,000 DOWNLOADS. To think that I was here exactly a month plus one day ago, thanking everybody on this site for 90,000 downloads on my little lockdown project - it simply astonishes me to think that I am here once again, so soon after my last post, thanking the community for 100,000 downloads. The download count is just a number - but when I visualise it as 100,000 individuals - all having clicked that big blue download button in the top right corner, at some point over the last nearly two years. That's quite a crazy thought, isn't it? To fit 100,000 people into a room - would sure be a stretch. To think that my plugin has had more people downloads than seats in Wembley Stadium (90,000) is quite insane. It's for sure an achievement, and I'm extremely thankful. I would like to apologise for my recent lack of updates around here, I've been extremely busy - but the support that I am shown day after day with people sending nice messages about the work I've done to the pack, is making me want to jump back into development more and more. I have confirmed before, and would like to reiterate, Section136Callouts is still under development and there is another update coming, but whilst juggling full time work with other commitments, such as my paid Discord Bots, I've been left with very little time to devote to the pack. But to confirm, I'm going nowhere. So I would like to thank all 100,000 of you legends for hitting that download button. This is one hell of an achievement, and without you - it couldn't have happened. Speak soon, Max Remember - Early Access Club members get updates first! They already have new features for the next update! For more information, visit https://maxplayledev.org/section136callouts/eac

I've said this probably 30 times in this thread. Section136Callouts is not designed (deliberately) to work with Callout Manager. Section136Callouts is designed to cancel callouts if you are too far from the situation loaded by the callout. The next update will introduce measures to prevent issues involving this, but for the moment - use the Section136Callouts Menu to launch callouts, as the menu will disable some location bounds in callouts within the pack. 10/10 for the reply, here. 😂 As Cyan said, you can find out what it does simply by googling the name of it. It's included in the Section136Callouts download package, and handles (de)serialization of the XML files created by the plugin. Serialization/deserialization is just a more automated way of loading/saving the XML files - to help cut down on the amount of code required for loading/changing/saving settings files. Feel free to ask if you have any further questions, but remember - Google is your friend. Never delete DLL files that come with the download of callout packs - otherwise you will find that nothing works. 🙂

A) Please don't post an entire log in my comments section, use a tool such as Pastebin or GitHub Gist to provide a link to your log. B) If you could edit this and remove the log, that'd be most appreciated. It's a pain to scroll through an entire log whenever I open the comments. This issue was caused by an outage on the Section136Callouts API server, which is used to request the most recent version of Section136Callouts. It has since been fixed, and you should face no additional errors. Please remove the log content in this comment. It is extremely inconvenient when people post entire logs in the comments. Include only a snippet, or use a tool such as GitHub Gist or Pastebin to provide a link to your log, or mark it as a spoiler. This issue was caused by an outage in the Section136Callouts API server. It has since been fixed, and you should no longer encounter this issue.

Interesting. The ped may have gone invalid, but I'll be sure to look into it. Thank you for reporting this. Section136Callouts is not designed to work with Callout Manager. I've been quite open about this on the thread so far, so maybe take a look? Callout manager saying it "failed to start" is not true. Section136Callouts is designed to cancel callouts if they would make you drive for 20 minutes to arrive at a scene. If you want to start callouts within 136 more effectively, use the Section136Callouts -> Callouts menu. You can see this by pressing X (by default) and selecting Callouts.

Section136Callouts doesn't spawn this partner, and doesn't attempt to control it. This is a bug with STP or whichever mod you are using to spawn this partner. General LSPDFR AI logic makes the partner arrest the suspect, not Section136Callouts.

Nothing here suggests that Section136Callouts has anything to do with this. I've not had any reports of this - which leads me to suggest you've got something setup wrong. Perhaps try reinstalling RageNativeUI to see if that solves the problem?

Firstly - thank you for the kind words. I would appreciate it if you could submit those as part of a review for this plugin, using the Reviews tab that the top of the comments section. This crash appears to have been caused by LSPDFR itself, rather than Section136Callouts. It appears as if LSPDFR crashed when processing the Backup request sent to it by Section136Callouts. If it happens often, I would suggest submitting a bug report to the LSPDFR team on the appropriate page.

Callouts in this pack are not designed to work with Callout Manager. They are implemented so you do not have to drive across the map to a call, so will not run if you’re far away. Calls do not “fail to start” as callout manager says.

THANK YOU FOR 90,000 DOWNLOADS. For something I started as a lockdown project to help my own mental health, this thing has sure taken off - hasn't it? I'm constantly amazed by how many people have downloaded this simple little project of mine. I want to personally thank each and every one of you for downloading the callout plugin. But then again, 90,000 personal thank you's would take me bloody forever, and I'm an impatient Brit so - this post will have to do. Thank you so much everybody, this means a lot to me. Enjoy your day/week/month/year. ❤💙

Progress is certainly being made in preparation to release Version 1.0.9.0. The new content actually turned out quite nicely, and it's a relatively large callout as well - being completely dynamically located, with plenty of personality. Trust me. 🏏 There is a lot of new features and bug fixes, and I cannot wait to share them with you! I've even shared a little screenshot of my notion project. For those who can work their magic and unblur the below image, go for it. But personally - I think you should wait until the update drops. Not quite sure on the release date just yet, but it's sooner rather than later - I can assure you. Just waiting for some feedback from my beta testers to ensure its' all stable and ready to go, then will most likely work on bug fixes until release. I am excited to share the new content with you! Keep patrollin! - Max https://maxplayledev.org/section136callouts/earlyaccess https://maxplayledev.org/discord

Thank you, Mr Null!

If you get confused by the XML configuration file, don't worry! There's a nice little convenient GUI-based configurator on the way.

That is nothing to do with the plugin. 1. Do not load LSPDFR on startup. You'll encounter issues, for example - infinite loading screens. 2. Use the LoadPlugin command once you've launched into Singleplayer.