The latest updated version of RAGE Plugin Hook, required to play LSPDFR, can be found inside the LSPDFR download. It is not currently available on the RAGE Plugin Hook website.

What's the significance of the API? What exactly will it introduce?

Followers

July 15, 201510 yr

I know it has to do with other people making mods using LSPDFR's info, I think.

Can anyone explain it more in depth than that?

Quote

July 15, 201510 yr

It allows developers to create LSPDFR plugins, hooking directly into the code of LSPDFR. It allows for a more seamless interaction.

Invenio, Investigatio, Imperium

Quote

shadow3467 and AnneJordan75
2

July 15, 201510 yr

Author

It allows developers to create LSPDFR plugins, hooking directly into the code of LSPDFR. It allows for a more seamless interaction.

That's what I thought. So is it safe to say that with the release of the API we'll see a lot more mods being pumped out by the community? Call outs, tools, features etc.

I know FinKone was really looking forward to this lol

Edited July 15, 201510 yr by shadow3467

Quote

July 15, 201510 yr

That's what I thought. So is it safe to say that with the release of the API we'll see a lot more mods being pumped out by the community? Call outs, tools, features etc.
I know FinKone was really looking forward to this lol

Oh yes, I'm sure many developers will be pleased with the API :)

Invenio, Investigatio, Imperium

Quote

AnneJordan75 and shadow3467
2

July 15, 201510 yr

Author

Oh yes, I'm sure many developers will be pleased with the API :)

Awesome! Thanks for the quick reply.

Also thank you, and thanks Sam, LMS, Ragehook guy(s), and everyone involved in LSPDFR the mod and the website/forums. Can't wait to see what you guys come up with next!

Quote

July 15, 201510 yr

Management Team

It aims to expose LSPDFR functionality, such as pursuits, to developers so they can make use of our features and the experience will be exactly the same. We also provide functions to retrieve data from LSPDFR, such as whether a callout is in progress. The 0.2 API is very very basic as we focus on features and stability more at the moment and hence lacks a lot of internal features, but this will improve over time. Another reason why we didn't implement so many functions is that LSPDFR is a very early version and many things are subject to change or hacky solutions, so exposing them is not always a good idea. The most important feature of the current implementation is the ability to hook into the callback dispatcher so that user-created callouts are dispatched by LSPDFR as well as the ability to create pursuits (though no custimization yet). I plan to bring back the V API dev forum soon so I can get in touch with developers and their needs/ideas/problems.

Please do not PM me unless really necessary (knowing you helps). If you think you need my attention in a topic, tag me.

Quote

Straysify, Qwerasdzxc, shadow3467 and 1 other
4

July 15, 201510 yr

Author

It aims to expose LSPDFR functionality, such as pursuits, to developers so they can make use of our features and the experience will be exactly the same. We also provide functions to retrieve data from LSPDFR, such as whether a callout is in progress. The 0.2 API is very very basic as we focus on features and stability more at the moment and hence lacks a lot of internal features, but this will improve over time. Another reason why we didn't implement so many functions is that LSPDFR is a very early version and many things are subject to change or hacky solutions, so exposing them is not always a good idea. The most important feature of the current implementation is the ability to hook into the callback dispatcher so that user-created callouts are dispatched by LSPDFR as well as the ability to create pursuits (though no custimization yet). I plan to bring back the V API dev forum soon so I can get in touch with developers and their needs/ideas/problems.

Awesome! Thanks again for all your hard work!

Quote