Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
Dear Development Community,
due to some recent "module ID" conflicts we've seen reported in the last months, we remind you that the module ID used in the projectdefinition.txt MUST be unique to the dynamic library. The module ID is used by Cinema 4D to distinguish modules and, "similarly" to plugin ID, it's supposed to be unique. The practice of using any of the projects shipped with the sdk.zip as a template is fine as long as you keep attention on changing the module ID provided by default. Finally it's worthy reminding that the module ID should follow a reverse domain notation order as suggested from the value available here where based on your username and, eventually, the website used in your profile, we suggest a potential root representation.
projectdefinition.txt
sdk.zip
The SDK Team