This project is the result of some reverse engineering of Virtools. It comes as a CK2 plugin.
The CK2 plugin adds the following two building blocks to Virtools:
When you save a composition file with the "hide script representation in schematic view" option disabled, Virtools will save extra information together with the script logic. The extra information saved includes dimension and placement of building blocks, shape of behavior links and parameter links etc. It is obvious that these data are vital to display the script schematic correctly in Virtools.
If a composition file is saved with the previously mentioned option enabled, scripts will be saved without this information, leaving the script logic alone. This effectively protects the script from being copied easily. However such protection is similiar to obfuscated Java bytecode -- it is possible to produce human-readable script from an obfuscated one, hence the name "Virtools Script Deobfuscation".
What this plugin does is fairly simple: it adds the information required to display the script back. That's it!
Create a new Virtools file and add a script. Then, drag BBDecoder
(Located in category Custom/VirtoolsScriptDeobfuscation) into
Schematic View. Connect script start arrow with BBDecoder's In 0.
Now, double-click to edit the only Parameter and set it as the file
which you want to decode and load (Editable format needed. Use tools
to convert VMO file before executing). At last, click the Run button
at the right-bottom corner of Virtools window. The decoded result
will be written in the current document.
This method is suit for beginner, especially for who just want to use this project.
Virtools Dev 3.5\Sdk\Samples\Behaviors\VirtoolsScriptDeobfuscation)VirtoolsScriptDeobfuscation.props.template and rename it
as VirtoolsScriptDeobfuscation.propsVirtoolsScriptDeobfuscation.sln with Visual Studio.Quick Build borrow the attached projects of Virtools SDK to compile itself. If you don't like this, or you need compile for different Virtools version. You should follow these steps.
VirtoolsScriptDeobfuscation.props.template and rename it
as VirtoolsScriptDeobfuscation.propsVirtoolsScriptDeobfuscation.props. Set macros with
proper values.VirtoolsScriptDeobfuscation.sln with Visual Studio.An example macros definition of VirtoolsScriptDeobfuscation.props
is here.
<VIRTOOLS_PATH>E:\Virtools\Virtools Dev 5.0</VIRTOOLS_PATH>
<COMPILE_TEMP_PATH>Temp</COMPILE_TEMP_PATH>
<VIRTOOLS_INCLUDE_PATH>E:\Virtools\Virtools Dev 5.0\Sdk\Includes</VIRTOOLS_INCLUDE_PATH>
<VIRTOOLS_LIB_PATH>E:\Virtools\Virtools Dev 5.0\Sdk\Lib\Win32\Release</VIRTOOLS_LIB_PATH>This plugin has a log system to track the internal data of the script.
Log system will spend IO and disk space. So it is only enabled in
Debug mode in default and served for debugging mainly.
Log system is actually enabled by macro VSD_ENABLE_LOG during
building. You also can directly define this macro to enable log system
forced as you wish.
The difference with old version is that new version use Virtools
Temporary Folder to log data. This address is dynamic. However, it
will be printed in Debug Window and Virtools Log Window. You
can easily find it.
According to Virtools' design, this folder will be clean
automatically by Virtools. However, this folder may still in there if
Virtools crashed or Visual Studio terminate Virtools during debugging.
Developer should clean it manually.
The performance of this plugin will significantly drop when using Debug mode. So do not use the plugin compiled with Debug mode in production environment. When a bug occurs, we also highly recommend you create a minimalist reproducing file to reduce the time consumption of debugging.