What version of security does the client use !

Aw crap the minimum is 20, not 10 right.

What do you mean by security of the client? Are you talking about the obfuscation of the client?

He probably means the protection (decompile-breaking, junk code) that is in some classes.

It actually isn't that hard to "break". I've made my deobfuscater for rotmg based off of rabcdasm. All that was needed was to identify the obvious junk code patterns with regex patterns and renaming of _-names to compiler friendly ones. Parse through all the decompiled files and remove junk code/rename _-names. I've released a couple clients that I ran through this deobfuscater of mine (the one embedded in my public 15.0 client and the fsv3 123.5.1 client I've made). I won't release the deobfuscater because it is easy to break and would rather not give kabam a reason to change up the obfuscation.

@nilly I will check your clients when i get home. I know you cwn deopfuscate the client easy. But it still wont be a clean source i get. Im not going into what software to use. And also im only uses it for reference.

// shadomir

---------- Post added at 03:04 AM ---------- Previous post was at 03:02 AM ----------

What im talking about is what the client is encoded with and obfuscated

---------- Post added at 04:24 AM ---------- Previous post was at 03:04 AM ----------

What im talking about is what the client is encoded with and obfuscated

@shadomir, not sure I understand what you are asking. I've never used SecureSWF on anything so I don't know exactly the type of changes that it makes. I do know that removing junk code with the addition of renaming _-names (the latter may not be needed) will allow decompilers like sothink to function properly.