dbor

This is a good point. It's a small thing but bothersome enough to make me want to take care of it by writing everything myself. Might do that soon since I seem to be having no luck with downloads. I agree, crashes are part of the experience at this point. By compatibility issues, I'm mainly referring to the inability for STP to properly interact and behave well with newer plugins. I understand that part of the responsibility of developers is to account for widely used plugins made by others, but STP is years behind on doing their part. 100% percent relatable. I've got one always disabled but still in the files, switching back and forth every now and then. I'd also add that the new Computer+ is pretty good.

I see your point. A good chunk of playing LSPDFR can involve your imagination at times, especially since (as you already said) not every single possible course of action for a player has been scripted. Amen. I would say that, although lacking features, LSPDFR is by far the most polished mod I've ever seen released for GTAV. It's clear that a lot of care went into planning out the development of it. I looked more into purchasing the new versions of STP & UB and yeah.. it's not worth my time. Your warning about this is appreciated.

Sadly, you're right, there is not. I completely agree that STP has a pretty nice system, but I also believe that more of this kind of stuff should be standardized and polished to the same or a similar level as LSPDFR. My point here is just that, as good as STP is, I think that there is a lot more room for improvement.

Although maybe not necessarily broken, you have features like pat-downs that will have STP using their own method to return pedestrian possessions while LSPDFR now has their own. Although this in itself is something you can deal with, you also have callout packs like "Lore Callouts" that take advantage of the LSPDFR searches as a mechanic. This causes confusion. This is just an example, but I can name a number of similar occurrences that could be fixed. Absolutely agreed with you. It's the only reason I'm trying my best to correct these issues without having to consider removing it (which I doubt I'd do anyways.)

So, to clarify, the scripts are still being updated to work better with LSPDFR 4.9, but those updates are just unavailable without paying the creator? I've been on the creator's Discord & there has been no sign of interaction with the community from the author in about a year or more. Although I'd love to help, I'm afraid that my poor compatibility experiences occurred in the past and that none of my logs from that time would be accessible. I completely agree with you. I've had some of my best times playing LSPDFR with these two. Despite this, they seem to have begun to fall behind in terms of their purpose, especially considering the changes to LSPDFR for which this version of the plugins did not account for. I'm sure you'll agree when I say that I find the LSPDFR animations, UI, and mechanics among other things much more polished than what STP & UB offer. As a disclaimer, just know that my understanding on this topic is limited. Although I have extensive experience with development, my knowledge of this community and the history of popular plugins/authors is very broad.

As the title suggests, I'd like to discuss the compatibility of these two scripts with LSPDFR 0.4.9. In my opinion, it seems that due to the lack of updates for these scripts, they may not be fully optimized for use with LSPDFR 0.4.9. While both of them offer impressive features that I'd hate to part with, I often encounter situations where they duplicate some of the functions recently integrated into LSPDFR, causing a bit of confusion in the overall experience. One prominent example of this is the frisking features present in both LSPDFR and StopThePed. They operate independently of each other, resulting in perplexing outcomes when searching pedestrians. Furthermore, although I appreciate the alternative surrender animation offered by StopThePed, I sometimes revert to the original system due to compatibility issues with callout packs. These are only two examples and, although I can offer more, I believe my point is clear. I'm primarily interested in hearing your opinions on this matter and any alternative solutions to common issues that people encounter with these two scripts. If there's something significant that I might be overlooking, I would greatly appreciate it if someone could fill me in.