On 06/02/2017 at 13:46, xxxxxxxx wrote:
Basically we issue multilicenses as a "package" containing 2 serials - the standard C4D serial and the multilicense serial. The multilicense serial is linked to the C4D serial (digits 7-11 are identical), and specifies the number of licenses for the package.
So for any given serial package, the C4D serial and the multilicense serial will always be the same, and you can get them with GeGetSerialInfo(c4d.SERIALINFO_CINEMA4D) and GeGetSerialInfo(c4d.SERIALINFO_MULTILICENSE). If you want to key specifically to the number of seats, use SERIALINFO_MULTILICENSE, which indicates the seat count in digits 4-6.
In many cases, a single customer may have multiple serial packages - either because they were purchased separately or because they want to specify use counts and link plugins for specific users or departments. But really you as a plugin developer only need to worry about licensing one license per seat enabled in each multilicense.
The only time the multilicense number will change within a release cycle is if the customer purchases additional seats for that serial package, in which case digits 4-6 will change to show the new seat count.
So for instance, MAXON NEWS NETWORK may have 10 seats for their Broadcast department and 5 seats for the Online department. Those are two separate packages, and one will have a multilicense key with 010 in digits 4-6 and the other with 005 in digits 4-6. They might want to license your plugin for use in the Online department, and you'll key against the associated multilicense number with 005 in digits 4-6. That number will always stay the same for the release cycle, unless they increase the seat count (in which case, they need to purchase additional license(s) for the plugin.
I hope that makes sense.