Maxon Developers Maxon Developers
    • Documentation
      • Cinema 4D Python API
      • Cinema 4D C++ API
      • Cineware API
      • ZBrush GoZ API
      • Code Examples on Github
    • Forum
    • Downloads
    • Support
      • Support Procedures
      • Registered Developer Program
      • Plugin IDs
      • Contact Us
    • Categories
      • Overview
      • News & Information
      • Cinema 4D SDK Support
      • Cineware SDK Support
      • ZBrush 4D SDK Support
      • Bugs
      • General Talk
    • Unread
    • Recent
    • Tags
    • Users
    • Login

    Always use unique Module ID

    Cinema 4D SDK
    1
    1
    963
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • maxonM
      maxon
      last edited by

      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.

      The SDK Team

      1 Reply Last reply Reply Quote 1
      • ferdinandF ferdinand unpinned this topic on
      • First post
        Last post