Password protect styles/macro's?

[Pixual]

Hi,

I'm wondering, is it possible to password protect your own fabricated styles/macros within Railclone itself? If so, how to set this up?

Thanks in advance!

Jakob de Vries
Pixual

[iToo]

Hi, It's not possible actually, but want to add it to next releases.

[Dragan]

It could be on two levels of security:
1. Password/license to activate RC object/Library
2. Password to open Styles/Macros for editing

Although, I personally would keep just the first option and keep the Styles and Macros open so more users can benefit from analyzing/editing the styles.

 

[Pixual]

Hi all!

Thanks for the quick responses!
@Dragan, could you specify how to set this up? I get that it would be benificial to see the setup inside the macro's. In this case however, it's required that this knowledge will be locked from opening and editing, but at the same time, we would like to give the user the flexibility of using the script.

@iToo, this would be an awesome feature if it could be done inside RC itself!

Greetings, Jakob

[Dragan]

@Dragan, could you specify how to set this up? I get that it would be benificial to see the setup inside the macro's. In this case however, it's required that this knowledge will be locked from opening and editing, but at the same time, we would like to give the user the flexibility of using the script.
Greetings, Jakob

I`m creating a lot of RC Preset/Object as well as Macros. Usually, those are for specific clients so I don't need to think about protecting them. I have some Macros on my Gumroad page (I didn`t upload for a while   ) and those are free.
I was thinking also about protecting RC Presets/Libraries with some kind of user password inside RC so it could be unlocked after purchase and reduce possible piracy. This could be on-time usage only to unlock at the start. It will be useful for Itoo and for people who create RS presets for sales.


 


 

[iToo]

I was thinking also about protecting RC Presets/Libraries with some kind of user password inside RC so it could be unlocked after purchase and reduce possible piracy. This could be on-time usage only to unlock at the start. It will be useful for Itoo and for people who create RS presets for sales.

Unfortunately that will not help with piracy, because passwords/keys may be easily included together the libraries.
Advanced anti-piracy system requires keys tied to the hardware ID, and this is much more complex. Not an option for user libraries, i'm afraid.

[Pixual]

nfortunately that will not help with piracy, because passwords/keys may be easily included together the libraries.
Advanced anti-piracy system requires keys tied to the hardware ID, and this is much more complex. Not an option for user libraries, i'm afraid.

Hi, It's not possible actually, but want to add it to next releases.

Hi!

@iToo, as you stated in above quotes, in what way are you thinking to secure these scripts in a next release if password protection isn't an option for the user libraries?

[iToo]

@iToo, as you stated in above quotes, in what way are you thinking to secure these scripts in a next release if password protection isn't an option for the user libraries?

We'll add the option to protect Style editor with a password. It may be useful for outsourcing, sharing work between companies, etc.
Even if you want to sell "read only" libraries, but in this case the final user don't need the password to use them. So it's more difficult that password is leaked.