Hey everyone. I've been developing a plugin recently and found it very frustrating having to reload lspdfr every single time a make a change to the code. After a couple of time of reloading, lspdfr just being to crash. Does anyone have any useful suggestions on a more efficient way to test a plugin? Thanks.

It ultimately depends on what you are trying to test and how your plugin integrates with LSPDFR. If you are testing functionality that does not strictly rely on LSPDFR or could perhaps be stubbed fairly easily, then it might be quite easy. Say you use LSPDFR to request backup, but care about the actual behavior on scene as opposed to them spawning and arriving, your stub could have a unit spawn nearby and then your logic takes over. However, if you rely on a lot of LSPDFR functionality or functions that cannot easily be stubbed, then you probably have to do the entire reload.

 

As for crashes when reloading too often, see Main.DisableAmbientScriptHooks in 

 

On 11/6/2022 at 1:57 PM, GoddlyGut said:

any useful suggestions on a more efficient way to test a plugin?

There is one trick.
After you have been through one sequence of cmds, You do not need to type in CLI again. If you hold Ctrl and press arrow-keys then you can browse through all your previous CLI cmds. It is marginally more efficient than having to type letters in the 3 cmds needed for unloadingPluginLSPDFR, loadingPluginLSPDFR  and forceduty, where the bolds are the only necessary tokens for the CLI-cmd in question.

On 1/22/2023 at 12:35 PM, GTAbear said:

There is one trick.
After you have been through one sequence of cmds, You do not need to type in CLI again. If you hold Ctrl and press arrow-keys then you can browse through all your previous CLI cmds. It is marginally more efficient than having to type letters in the 3 cmds needed for unloadingPluginLSPDFR, loadingPluginLSPDFR  and forceduty, where the bolds are the only necessary tokens for the CLI-cmd in question.

 

You can also use the "Bind" command in RPH to bind specific commands to keys. That way you could automate the process even further.