Encrypting MaxScripts
See my comments under the script, definitely wouldn't call that 'without a chance to decrypt' when it's in fact easier to decrypt the result created by this than a .mse file you'd create the usual way.
@blakestone: well, if you make something that's interesting and useful to a number of people, someone will find a way to break the protection and publish the 'open' version. If it's not that interesting, plain old .mse is okay, no one will bother. That said, C++ has an edge in this regard as most of the time, the disassembly you will get out of it is not all that useful, unless you are very commited to finding a way around it... in which case, there will be a keygen or something like that in no time either way. There's also minification and obfuscation which you can use together with saving the file as .mse, though that would only help if you want to make it hard for people to copy-paste sections of your code, not if you want to make it harder to circumvent a protection you have in place.
