Hi developers,

 

I've had to fix a few files which had wrong information under 'Script/Plugin type' over the years (mostly people making standalone plugins who have marked their plugin as an LSPDFR one). I thought since we haven't made it clear, I'd post a topic here clarifying what these options mean, and when to use each one. This post will also be linked at the field description.

• 'LSPDFR callout(s)' - Your RAGEPluginHook plugin adds one or more callouts to LSPDFR via the API.
• 'LSPDFR plugin' - Your RAGEPluginHook plugin is loaded by LSPDFR or RAGEPluginHook, and talks to LSPDFR via the API.
• 'Standalone plugin' - Any plugin or script which does not depend on LSPDFR, and can operate without it. Any plugin which does not use the API, or optionally uses the API when LSPDFR is installed.

 

Of course, your plugin/script can be a mix of the above. As a result you can choose multiple options by holding the SHIFT key.

 

Thanks,

Cyan

On 1/14/2019 at 6:23 AM, Cyan said:

Any plugin or script which does not depend on LSPDFR, and can operate without it. Any plugin which does not use the API, or optionally uses the API when LSPDFR is installed.

 

Has this ever actually been achieved? I've never seen an implementation of a standalone RPH plugin loaded directly by RPH (not by LSPDFR), which can use the LSPDFR API. There's been discussions of how it ought to be possible with cross-app-domain Reflection, but I've never actually seen it implemented. Do you have any examples of this?