thatmaxplayle

If it crashes - please send me a RagePluginHook.log so I can look into the bug. Urm, plugins don't tend to cause ERR_FIL_PACK - it's more of a mods folder thing... so that's very unlikely to be related.

The suicide callout isn't meant to work, it is hardcoded to provide a Code 4 Disregard because you aren't logged in with Early Access Club. Edit: Just realised that you were referring to the Suicide Callout, not the Concern for Welfare callout that I am currently working on. The only reasoning for the suicide callout failing to start (having checked the code) is that the memory pools for entities were full, and thus the game could not return a handle for the given entity (that's even if it were created in the first palce) - if you could complete the following troubleshooting steps, and let me know if any of them help: 1. Restart your game (allow a moment between closing it and opening it again, to allow Windows time to free the memory completely) 2. Restart your machine (if restarting your game wasn't enough alone) 3. Send your RagePluginHook.log file either in a reply to this message, or to my Discord Server (https://maxplayledev.org/discord) The callouts you mentioned have been entirely re-written, fixing a number of bugs found within the original callout, and given it's entirely rewritten logic - the code is also a lot cleaner, although the idea for them originated from Assorted Callouts. That said, I believe I may have used a UI helper for the "black-boxes" that display on-screen, however have been in the process of swapping those out for RNUI menus over the past couple of updates. I believe 136 makes use of the original locations, too. I did think Albo was credited within the credits to this file - however upon checking have discovered, as mentioned, that this is missing - this will be rectified shortly. "Partially modified" is a bold claim. Whilst the callouts have the same storyline/positioning data, the logic behind these callouts is unrecognisable. Furthermore, stuff like this is more tainted towards a Direct Message. If it were to be the case that this pack took no inspiration from a different one, this would be quite a bold accusation, would it not? Kind regards

Section136Callouts turns 3 years old! I just wanted to make it known that I am eternally greatful for all of the support you awesome people have shown the pack over the years! I know development has been rather slow recently, due to IRL commitments, however the prolonged support and usage of the pack does not go unnoticed. Even today, without an update recently, the pack averages just over 100 downloads per day. That's awesome to see! Development will continue shortly, once I've worked out why GTA hates the callout I'm trying to make... cheers once again for all the support. I honestly cannot believe the pack is now 3 years old. For something that was never intended for release, it ended up working out pretty well - did it not? Let's go!

This appears to be some sort of firewall on your end preventing a connection to my server. If you head into the configuration file (available at Plugins > LSPDFR > Section136Callouts > mainconfig.xml) and look for `ProhibitNetworkTransmission` - setting that to 'true' (without quotes) should fix this. Hope this helps, sorry to hear you've been having troubles

You're more than welcome, happy patrolling!

Sorry, but your log does not suggest any instance of an error caused by Section136Callouts. The only exception thrown by the plugin is related to the automatic error reporting system, although this would not affect gameplay in any way (as evidenced by the fact your game session continued for another 20 minutes following this error)

It seems to me like you’re probably making invalid changes to the configuration file, which are causing it to be reset when it’s loaded. Pay attention to the notification feed when loading plugins after modifying a configuration file. I’m not sure what effect the use of “uninstalled.” at the end of your message was meant to have, but rest assured it had none 😂

I use only the LSDPFR function to play scanner (I'm working on my own implementation) but I'm pretty sure it uses the audio in gameroot\lspdfr\audio.

Yes, you can. You can edit the configuration file at PLUGINS > LSPDFR > SECTION136CALLOUTS > mainconfig.xml (which is generated after the plugin loads for the first time) and Ctrl + F to search for "CheckOnStartup". Changing this value to "false" will remove the update checking.

Just thought I'd drop this in here... as a little hint to one of the many possible situations brought by the new callout.

⚠️ System Status I am aware that the automatic update checker inside of Section136Callouts will not work at the current moment. This is due to substantial data loss on the server the plugin retrieves update definition files from. Despite data recovery efforts, the original file structure (and contents) wasn't backed up, and was unretrievable. As such, the server has been restrucuted, improving on it's original layout. For that reason, public release builds of Section136Callouts will be unable to acertain whether they are up to date or not. The upcoming v1.12 update will introduce support for the new update checking format. Based on the client-side code alone, the new method of update checking is much more efficient than the former one. Given the low priority of something like an update checker, and the fact that failed update checks will not crash the plugin (or at least, they shouldn't) - a patch will not be released for the time being to fix this functionality. The next major update, which is coming in the next couple of weeks, will however address this issue. Apologies for any inconvenience or confusion which may have been brought by this issue. I'm aware that you may see some strange update checking related error messages in the bug, and have fixed the issue, but it is not of a sufficient priority to release a dedicated patch for it. The new update will be with you in the next couple of weeks. EDIT: This functionality has been fixed, and will be pushed very shortly.

Yes you absolutely can. Firstly, unload LSPDFR. Once you've done this, find the configuration file at the following location: GTA V > Plugins > LSPDFR > Section136Callouts > mainconfig.xml (This file is only generated once you've played with Section136Callouts at least once.) Open this file, navigate to the KEYS section, and change the MainMenu key to your desired key. Be sure it's a valid key (a full list is available here) Thanks for using the plugin!

So why didn't you just report said crash the first time you encountered it. Don't want to make you feel stupid here, but that probably would've lead it to be fixed. Furthermore: If it's only your game that is crashing with the pack (which it is, reports of regular crashing are indeed very rare), I'd lean to suggest it's your GTA/LSPDFR/RPH configuration that's messing things up. Not my pack.

I don't have a kidnapping callout, neither do I have a Gang Fight callout... so I think you've got the wrong pack! idk maybe you'd be able to do it if you submitted crash reports, like you're supposed to, including log files and the like? just a thought 🤷‍♂️

All of the scripting dependencies (e.g LSPDFR, RPH, SHV and RNUI) have been updated following the most recent update. Have you experienced any issues with Section136Callouts since the recent update? If so, I can look at issuing a patch before the new content would otherwise drop. This patch wouldn’t contain the new functionality but would at least fix any issues you’re encountering.

So, I thought I would update everybody on the progress of updating the pack. Pictured is the line count for the file of a new callout. Let's just say it's a big one. Already weighing nearly 1500 lines at approximately 40% completion. The pack will be updated soon, but given the influx of new functionaltiy, testing procedures may take some time. Not only is there a new callout in the upcoming update, but a whole army of new Quality of Life fixes to make your experience just that little bit better. Furthermore, the new update will make editing the plugin's configuration a lot easier. The new callout features a rich, multi-possibility story - and given it's ambitious nature, some time will pass before development of this callout is finished. It's 1,500 lines already (of compact, space-saving code) however I am nearing completion of the first major situation. This callout uses a randomised tree of possibilities to structure itself, and is anywhere from somewhat to completely dynamically positioned, depending on the result of the situation tree calculation that is performed at the start of the callout. I've been developing it LIVE on Twitch, on occasion. Of course, I've been utilising time off-camera to do more focused development on the pack, however if you're interested as to how these things work - giving me a follow on https://twitch.tv/thatmaxplayle may be of interest to you. This message is more of a confirmation. New stuff is coming. However, given the ambitious nature of this new content, it'll be a little while (perhaps a couple more weeks) before it is in a position where it can be released. Furthermore: Thank you for 150,000 downloads. That's an incredible amount of people who have come back to the pack, even after a duration of inactivity on my end. Thank you so much for being loyal to the pack, and I hope you enjoy the upcoming updates.

You can edit the mainconfig.xml file under Plugins > LSPDFR > Section136Callouts > mainconfig.xml In an upcoming update, you’ll be able to edit them from the Section136Callouts Menu.

If you’re experiencing issues, be sure to perform the following troubleshooting steps: • Delete your mainconfig.xml file (located in GTA > Plugins > LSPDFR > Section136Callouts) • Restart your game and see if this helps. • Delete the data folder (the same folder that contains the configuration folder) and reinstall Section136Callouts, which will reset the plugins data. • Restart your game folder and see if this helps. If you’re experiencing issues, send me a log folder either here or via my Discord Server.