I tried a test in free mode, decompiled it with reflector and saw mild renaming as per the free limits. I just tested this again, after a break, AND IT DOES NOT WORK RELIABLY. If you are serious about developing this product you need to engage with developers, accept their feedback and make sure the damn thing works 100% of the time - esp for the price you are charging. It'll perhaps raise the bar a bit, but obviously not prevent the problem. NET intern and write some code ourselves. The best way to make it difficult for the average script kiddie, it appears, is perhaps to employ a. The general agreement it seems is that each commercial obfuscator has (can have) a deobfuscator. Looking at various threads on Unit圓D forums about obfuscation and other such IP protection methodologies it seems like a lost cause to think about it. Will try out the other obfuscators, cheers Quietus for the suggesting the alternatives. Unit圓D Obfuscator seems to have added a comment and a goto statement, this hasn't stopped reflector from showing the actual code :-| The original entry is (marked as 1) is visible for inspection. The Obfuscator seems to have produced a couple of phantom entries for each of the assembly member methods ( marked as 2). I've attached an image of what I see with Reflector. Thereafter I tried to browse the assembly using Red Gate's. I tried to Obfuscate a webplayer's unit圓d file using the tool.

I downloaded the demo of Unit圓D Obfuscator 1.3.08 from the site. Protection against decompilers considerably reduces the chances to recover the source code of an application in an assembly or high-level language (C#, VB, etc.). This method comes down to adding various false conditions to the algorithm body and scattering the checks of existing conditions, loops and unconditional branches over the function body. Some change names with such characters for more understandable, some replace unreadable characters with their codes, some just refuse to work with such characters.

Net works with the UTF8 encoding, not all decompilers correctly process its characters. It comes down to replacing names with unreadable characters, for example, Japanese characters. This method comes down to removing the metadata of events and properties from the assembly, which makes it impossible to recover or use these properties from high-level languages (C#, Boo. Supporting obfuscation control attributes () Renaming scripts, classes, methods, fields into a set of meaningless or unreadable characters Unity 3D Obfuscator - a special protection tool for Unity 3D applications.

Extracting unity3d file