Regular script files are plain text so everyone can read them. Maybe you would like to protect your intellectual property or prevent users from tampering with your script code. SystemScripter can save your scripts in a special encrypted format.

To encrypt a script, simply choose File - Save As and specify Encrypted VBS as file type.

Since encryption is part of the Microsoft Script design, your encrypted script will continue to work just as before. However if a user tries to edit the script file, it looks scrambled:
 

Note the unencrypted comment lines. You can add as many unencrypted comment or script lines as you please, for example to keep your copyright visible.
Encrypted VBScript files use the file extension VBE instead of VBS so the WSH knows that it needs to decrypt the contents.

Please note: SystemScripter is one of the few editors that can decrypt encrypted scripts. To decrypt an encrypted script, you simply drag it into the editor or open it and specify the appropriate type.

This emphasizes that the WSH encryption scheme is not strong enough to protect sensitive things such as passwords. Never hard-code these things into your scripts. Still, we recommend you encrypt all scripts you use in production environments to keep casual "scripters" away from the code.