hpwPlayAction/MyCustomPlugin: Action-Insert-hints now accept more than one line delimited with [CRLF]
hpwPlayAction supports now command wizards for custom commands
hpwPlayAction.cfp/cfr are now read from plugin directory

MyEmbeddedPlugin allows to build custom plugins with completly embedded config and script-data.
Bugfix for TaskBarClickAndRestoreOnTop for About-dialog and command wizards
Bugfix: Free some more memory on initialization
Bugfix: Correct initialization of the parameter array for custom commands

Actioncode now stored in internal array and not in neobook variable.
Password only once stored in [MyPluginName_password] and not in each call
Optional custom parameter now up to 10 (Maximum in neobook)

You did not describe this plugin in depth but I just now looked at it and it looks very interesting. I will take more time to look at it but after reading the Word Docs you include, I am still not clear.

Am I correct to say that I can create a series of actions (in essence a page on a NB app) that can be "compiled" as a plugin file that others can then install as a plugin and add parameters to the scripts via the NB Script Editor/IDE?

This script's contents can be encrypted and the plugin can then be distributed for others to use. Correct?

Essentially, this offers an alternative to the other plugin that allowed subroutines but required a 'player' application to be run.

As stated by Gaev:

... also, I have an outstanding request/suggestion to "convert Function library file(s)" into "stand-alone compiled/binary plug-ins" ... which would also enable "easy swapping of plug-ins" within an application/exe ... plug-ins created from your Function library files.

This was written before this new plugin was released. Do you believe you have accomplished this with your plugin to create plugins?

Am I correct to say that I can create a series of actions (in essence a page on a NB app) that can be "compiled" as a plugin file that others can then install as a plugin and add parameters to the scripts via the NB Script Editor/IDE?

Yes. You describe your commands (For the config dialog) in your INI-file and that gets delivered to your customer/developer. The final end user of the developer does not need/see that INI-file. Only the bare runtime info is stored in the resource-section.

This script's contents can be encrypted and the plugin can then be distributed for others to use. Correct?

Yes. Powerscripter's to the front!

Essentially, this offers an alternative to the other plugin that allowed subroutines but required a 'player' application to be run.

Yes, but there is still the difference in speed. Real native compiled plugin-commands are faster. The scripts are still interpreted as in native neobook. Of cource the renamed MyNewPlugin.nbr is distributed!

This was written before this new plugin was released. Do you believe you have accomplished this with your plugin to create plugins?

Not exatcly, but similar. Gaev has given ideas and whishes for this latest plugin. (the evolution from MyCustomPlugin to MyEmbeddedPlugin)

A final step could be, to get the resource binding process away from external toolchain to internal functions of hpwEncode. But since that is fairly complex and ResourceHacker serves fine on that, I think there might be other interesting stuff with higher priority.