File/Object protection

On 18/06/2015 at 02:20, xxxxxxxx wrote:

Hi all,

my command-Plugin is working verry well.
But I want to protect a File ore better an Object to be used only if the the Serial-NR is correct.

Ist there any possibility?
Maybe to "Hide" an Object if SN is incorrect?

Thanks a lot

On 18/06/2015 at 06:26, xxxxxxxx wrote:


what exactly do you mean with "protect a File ore better an Object"? You can encrypt your plugin using the "Source Protector" tool. Than you can do whatever you want to ask for serial numbers and react accordingly. For example you could check if a valid key file can be found and if not, you simply don't register your plugin classes.

Best wishes,

On 18/06/2015 at 08:33, xxxxxxxx wrote:

Hi Sebastian,
thanks for your reply.

I try to explane it what I whant to do:
The Problem is:
If you build anything in C4D it can be copyied in other files or shared via Internet.
I whant to protect an object so that it looks if there is a plugin registered.

So: If the Plugin is not registered the Objekt should be hidden.

Thanks a lot

On 18/06/2015 at 10:03, xxxxxxxx wrote:


what do you mean with "object"? A object plugin? That would be the only thing you could protect. But if you create a generator the user will always be able to convert that generator and use the created geometry any way he wants. Also one can hide of course an object by setting the proper bits – but there is nothing to prevent anyone else to write a script or plugin to change that bits.

Best wishes,

On 03/07/2015 at 09:37, xxxxxxxx wrote:

Hello Kissling,

was your question answered?

Best wishes,

On 06/07/2015 at 00:32, xxxxxxxx wrote:

No, not realy.
Or better:
not satisfactory!

There must be a way to protect an Object to be used only if the user has the wright C4D Serial Number.

On 06/07/2015 at 09:15, xxxxxxxx wrote:


You can 'Protect' an object by adding a python tag or object that looks at the serial, does whatever you want it to do (hide the object from render), then makes sure the tag/object is hidden using ChangeNBit.

This is the only way that I have found to protect an asset without it being a plugin. I, however, wouldn't recommend doing this as it's possible it could mess something up on the client side if they find and try to remove the 'protection'.

Hope this helps,