Summary: A description of the structure of the XML license table.
If you want to automate a license system for your Monkey Compiled plugin, you should probably use the XML license table format. The Monkey Script Compiler can save an xml file with any number of valid licenses (for a particular product password). This Wiki page is a description of the xml structure of that file:
The XML document has a single node called <monkeycompilerlicensedata> which in turn contains four subitems:
The settings node contains all relevant project data, grouped into two categories:
The project node contains information about the manufacturer and the plugin:
While the license node contains the license password and code:
The keylist node contains a keycount subnode which indicates the number of defined licenses, and a number of identically named licensekey subnodes, each of which represents a single valid license data block:
Licensekey nodes contain a license string, and they have a number of empty fields for customer information. Of course when you have an XML parser in place it is very easy to add custom fields, but the standard ones are already included…