LSPDFR - Tracking Down Various Issues

Vehicle Storage:

I have a vehicle that I spawned, modified, and saved to the apartment garage.

When you restart the game, it reappears as its default red configuration, but with the modifications already in place - except the livery. 

I noticed that - a modified Diletantte will save perfectly, including a unique plate that even returns my own ownership - this car does not. It has the default plate, as well. 

Is this a problem at the vehicle.rpf level? or an issue with LSPDFR?

Empty Console Arguments Crash:

Providing an empty argument to a console function should only give a friendly error message. This might be a ragepluginhook thing, but it's important to always code functions/subroutines/methods/hoohahs to handle empty arguments, especially in console.

Settings and Choice for Players:

Is it possible for us to choose/config which apartment we will use for our characters?

Can we include an configuration option that sets the default start timeofday?

Is it possible to fix the game so players can create a list of personal vehicles? (I'm aware GTA5 has problems storing vehicles in garages correctly...)

Can we get more teleportation commands with helpful autocompletes for various locations in the world?

Is it possible that we could passively identify our fellow police officers as they are on duty? It'd be nice to put names to faces.

Identification system, PED Tracking and storage - CALLOUT AND PLUGIN CREATORS BEWARE:

It seems to me that there's several mods that try to access data that should be stored first in LSPDFR, but there's a critical problem with identification and tracking where you can get/generate/delete the ID of a PED, which causes problems when callouts go over large areas or start involving PEDs having to be "re-detained." This duplicates or even unintentionally mutates them in some cases. 

As well, there's a lot of mods that could use the functionality of whether or not you actually HAVE identified a PED. I can PED-check someone in smartpoliceradio without even having their ID. Several mods will put crime information into a computer, exposing PED identity without explanation or without having properly acquired their ID (unless it's something like a warrant callout).

I think this might also explain several errors and crashes that may arise from plugins trying to access PEDs at different times. This could be for anything from current behavior/state to their name/ID.

PEDs should be as persistent as possible - or even given prioritized levels of persistence. Even though it's unlikely we'd ever see a given random PED ever again, especially if they are arrested and jailed, the game losing track of them and their vehicle, or their own inventory is creating errors/crashes/logical problems with plugins and callouts.

Interoperability and Properly Extending Core Functionality:

Without having the project be open source, it's hard for me to dive in to dispel any assumptions about what's going on, but the constellation of plugins we have at this point make it difficult to properly extend PEDs and items that should be attached to them inside a PED, crime, or other database. I can easily envision every PED having an searchable list of items provided we understand the API and have agreed is extensible enough to support illegality, ID/notID items, cost, value, types, and other data. It would most certainly make everyone's job easier if LSPDFR merged these features into the base mod in order to move the platform as close to ragepluginhook or the rage engine as possible. The best candidates are court system and inventory system.

The problems that result from not doing this? Well, Ever since installing LSPDFR+, I've lost use of the regular computer system, which it doesn't aim to even replace. This is obviously a problem with the plugin first and the base mod second, but I feel like attention should be paid to grant proper access and control over LSPDFR features - otherwise extend them to include those features. Stepping on toes should not come before making the game work better.

Please be more transparent and active:

Finally - We have a pretty neat community here, so please be more active with current work on LSPDFR and involve us and our talents as much as you can. I can understand certain reasons for the team to not go open source, but getting fast and relevant and constant feedback and testing on development would be great for everyone. 

Glad to be here and hoping to make myself useful!

Edited April 5, 20197 yr by Starsickle
Added police names