Encryption of scripts to be inserted into text files

Question

I am working on a closed source game that uses a scripting language for automation. Almost all the logic of the game is processed by scripts. Scripts can be compiled into bytecode format, but due to the nature of the language, identifiers must be saved. Compiled scripts can be embedded in other text resource formats using binary text encoding.

I want to encrypt compiled scripts to protect the source during distribution, but since the language, bytecode format, and binary text encoding scheme are proprietary, do I need to worry about encryption? If so, should I just outrage some bytes and call them day, or should I use a full-featured encryption solution? Encryption should not unduly increase the size of the executable file, as the scripts can be large, and boot time is important.

Answer 1

Windows , exe , . , * nix.

, .exe, .exe, , . , .obj, exe - , , .

, , , , , , .

Answer 2

, . , - .

, , . , , , , , , - , .

, , , . , .

Answer 3

, , , . . , , , .

, , , , . , - , , . , , , . , , .

, , , .

Answer 4

.

, . , . .

, , . . - . , , , , , , . : , , , . , , .

Attaching files to an executable binary, on the other hand, is probably a good idea. This would eliminate the need to find them at runtime on the file system (locating at runtime is known to be somewhat more complicated on Unix systems than on Windows, due to hard links: on Windows, the executable can easily get its own path, but on Unix, the presence of hard links means that "the executable path is not defined."