Hello all,

I had an idea for a little project last night, but I'm not entirely sure if it's doable with the current API, or even if it will ever be doable at all.
The idea is to basically create an online database with the persona data from LSPDFR, which would include priors, warrants, etc.
My question is, would it be possible to develop an API plugin capable of tapping into that database to retrieve, for example, the wanted status of a ped from that database instead of generating on the go?

Yes actually it probably would, but in the long run it'd so much of a pain in the ass that it wouldnt be worth while. Also welcome to the community! :)

Yes actually it probably would, but in the long run it'd so much of a pain in the ass that it wouldnt be worth while. Also welcome to the community! :)

Nope. ID checks and information are generated on the fly. Warrants and criminal history are not stored and cannot be pulled from the database. You can simply generate the DOB and names.

Edited September 10, 201510 yr by AlconH

No she's not talking about real life person database stuff, I dont think, because I already knew what you just said. Idk XD

No she's not talking about real life person database stuff, I dont think, because I already knew what you just said. Idk XD

What the hell are you talking about? The OP wants to use the LCPDFR API to create an online database that contains information regarding ped names from the LCPDFR database. Nothing to do with real people.

Okay whatever, no need to get all bent out of shape about it, I was confused by what your saying, and yes someone could create a plugin that could do that it would be quite difficult though, but It'd be the same as how LSPDFR already does it

First of all thanks for the ideas.

So, let me see if I got it straight. The ped backgrounds are generated on the fly based on random chance, right?

The idea was to retrieve the name and DOB generated by LSPDFR and then query an online database for wanted status. I don't necessarily need LSPDFR to forward the wanted status/background to the db, actually, ideally it would be the opposite: a plugin that queries the database, retrieves the wanted status and flags the ped, regardless of whether LSPDFR generates a wanted flag or not. I've included a very rough and crude workflow below of what should happen.

I understand this is a bit of a novel project, but with R* shutting down multi-player modifications, it seems this may be as close to a "multi-player" experience for LSPDFR as we are going to get in the foreseeable future.

First of all thanks for the ideas.

So, let me see if I got it straight. The ped backgrounds are generated on the fly based on random chance, right?

The idea was to retrieve the name and DOB generated by LSPDFR and then query an online database for wanted status. I don't necessarily need LSPDFR to forward the wanted status/background to the db, actually, ideally it would be the opposite: a plugin that queries the database, retrieves the wanted status and flags the ped, regardless of whether LSPDFR generates a wanted flag or not. I've included a very rough and crude workflow below of what should happen.

I understand this is a bit of a novel project, but with R* shutting down multi-player modifications, it seems this may be as close to a "multi-player" experience for LSPDFR as we are going to get in the foreseeable future.

My concern with your flow is:

There are so many different possible combinations for the names, that entering information and reports via the application outside of the game would take a long, long time before anything actually shows in game because the chances of you encountering the same name twice is very slim. You could always mass produce the data, but even then, I'm not sure how many potential combinations there are for the names.

I'd also be concerned about the resources needed to run an application like this. There'd be a bit of querying involved and if the plugin picks up traction it could become quite expensive and time consuming to maintain.

My concern with your flow is:

There are so many different possible combinations for the names, that entering information and reports via the application outside of the game would take a long, long time before anything actually shows in game because the chances of you encountering the same name twice is very slim. You could always mass produce the data, but even then, I'm not sure how many potential combinations there are for the names.

I'd also be concerned about the resources needed to run an application like this. There'd be a bit of querying involved and if the plugin picks up traction it could become quite expensive and time consuming to maintain.

Oh, ok. I was under the impression that the names weren't randomly generated by combining a random first name to a random last name (props to the LSPDFR team for that!), but rather fetched from an internal database.

You are right in that it makes the whole thing a little pointless if the chances of player A running into the same person as player B are that slim.

In all honesty, I might have underestimated the resources needed to pull this off, in fact, I probably did, since I haven't really thought about that yet. As of now this is pretty much just an idea for a pet project. I do have an ok VPS sitting idle right now that I'd use to host the online side of the application, but yeah, I agree that it might not be enough, especially if it picks up.

Thanks for your input!

We're going to eventually implement something like this, hooked to LCPDFR.com.

Edited September 11, 201510 yr by Cyan

We're going to eventually implement something like this, hooked to LCPDFR.com.

Oh, excellent! I thought you guys would at one point. Looking forward to it then!
And if you need some ideas, i'm ready and willing to contribute :)

Oh, ok. I was under the impression that the names weren't randomly generated by combining a random first name to a random last name (props to the LSPDFR team for that!), but rather fetched from an internal database.

For LSPDFR, I don't believe it works like this. LCPDFR did, but that was because it pulled from a database of a bunch of first names and a bunch of last names. LSPDFR pulls from the FCRP (Fort Carson Roleplay, a San Andreas Multiplayer server run by G17) player list. My character was Will_Peavey, so it is possible to have Will Peavey as a ped name; one of Sam's characters was Jessica_Smith, so it is possible to have Jessica Smith as a ped name; but I don't think it would be possible to have Jessica Peavey as a ped name. (Unless someone joined with the name Jessica_Peavey, but I'm pretty sure that never happened...)