PingPlotter Pro integrates the Windows Scripting host to allow extensions to be written / modified. This gives a lot of flexibility, but it's also a bit complex at this point.
This forum's goal is to share extensions that you can just "drop in" without having to do a lot of changes. You also have the ability to edit these extensions and "tweak" them, or use the knowledge in them to write your own extension. At present, the object model of PingPlotter Pro is *not* documented (and it might not be completely stable, in that it might change in a future release), so the extensions written for one version of PingPlotter Pro might not work with another version of PingPlotter Pro.
Licensed users are welcome to ask us for help in implementing extensions they may need.PingPlotter Pro version dependencies
All the extensions in this forum are built to work against PingPlotter Pro version 3.00.3p beta 9 or higher. The scripting system changed slightly in that release, so most of these scripts will *not* work with any version before that. Most of these will not work with 3.00.2p (released version). The latest PingPlotter Pro beta is available, but does require a PingPlotter Pro license to use.Installing an extension
PingPlotter Pro extensions are *usually* .ppx files that live in the PingPlotter Pro/scripts directory. The easiest way to install one is just to download the script and put it there.
If PingPlotter Pro is running, you'll need to close it and restart it before the extension is available for use (if you're running as a service, you'll need to stop the service and restart it). Depending on the extension, it may need to be enabled in Edit -> Options, Plugins & Scripting.Other Versions
The scripting engine had some significant changes between version 3 and version 4, and although the scripts don't have a lot of changes to make them work, they do need to be evaluated and updated. You can get copies of both V3 and V4 scripts here:http://www.pingplotter.com/extensions/A word to the wise
Note that you should treat these scripts like you would any script - someone could write a script that causes damage to your system (intentionally or not). Any Nessoft-released scripts are certainly tested to not cause any malicious damage. Any user-submitted scripts should be used with more care. We will, of course, test user scripts as well, but we can't take responsibility for any damage they may cause.