LSPDFR 0.4 introduced an incredible set of features regarding customizeability with the data folder. To completely integrate such features third-party modifications without having modders create their own interpreter for LSPDFR's data files I suggest the following API additions:
Vehicle RequestBackup(Vector3 position, EBackupResponseType responseType, EBackupUnitType backupUnitType, string agencyScriptName, string flag);
Vehicle RequestBackup(Vector3 position, EBackupResponseType responseType, EBackupUnitType backupUnitType, string agencyScriptName, bool exactLocation, bool noResponseTask, string flag);
Vehicle RequestBackup(Vector3 position, EBackupResponseType responseType, EBackupUnitType backupUnitType, string flag);
Vehicle RequestBackup(Vector3 position, EBackupResponseType responseType, EBackupUnitType backupUnitType, string agencyScriptName, bool exactLocation, bool noResponseTask, int? occupants, string flag);
Implement another fuction argument "flag" (or possibly a function overload) that allows the use of either the default LSPDFR flags, or of custom flags added onto the XML. In case there is no vehicle with that flag, return as if the flag was not an argument. Would allow for usage of LSPDFR's own system for managing extra units instead on relying on each plugin implementing their own system to get units customized for a given necessity.
Ped CreateMPPed(bool isMale, Vector3 position, float heading);
Ped CreateMPPed(bool isMale, Vector3 position);
Implement a function to utilize LSPDFR's built-in ability to spawn a randomized mp_m/f_freemode_01 ped with distinct facial/hair features. Would allow the use of semi-random characters in callouts instead of built-in peds.
void ReleasePed(Ped ped);
Implement a function allowing plugins to release an arrested Ped.
Apart from these requests regarding the API, I'd also love to see a way to disable LSPDFR's control of the sirens with possibly something like:
Main.DisableSirenControl=false