When there are several encrypted scripts on the site, each one contains functions rc4(), base64(), md5().
If you added the disable include option for these functions in the CLI, I could add them only to the first script.

UnsupportedNode: PropertyArrayStart
Ricciolo.StylesExplorer.MarkupReflection.XmlBamlReader.ProcessNext()
ilspy\ILSpy.BamlDecompiler\Ricciolo.StylesExplorer.MarkupReflection\XmlBamlReader.cs:494

Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/31365308-propertyarraystart-of-xmlbamlreader-processnext-is-not-implemented?utm_

Unit tests need to be created that tests obfuscating with all possible Mutator permutations that are 2 Mutators long. So basically given the dozen or so current Mutators, make sure Mutators don't just work on their separately, but together as well. I've run into a few random cases where using Mutators in specific combinations produces faulty payloads, and want a test that can do this for me.

Us

Environment

Vagrant:

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
  config.vm.box = "bento/centos-6.7"
  config.vm.synced_folder ".", "/vagrant", disabled: true
  config.vm.provision "shell", path: "bootstrap.sh"
end

`

Add 'since' information to plugin configuration parameters by inspecting the commit history.

Will it support Android Application Bundle (.aab) in the following ?

For example, test can be useful to check if the test suite passes when garbled, which is an important indicator to tell if garbling broke anything badly.

version can be useful to report garble's own version, on top of the version of Go.

When running confusion(Loading classpath...), this exception was thrown, how to solve it?

at the moment only ntw::system namespace and ntw::memory components are tested.
It would be great to have a test suite that covers most of the library.