+ update 2020: WARNING - support of the decompiler is now VERY LIMITED. There are no active developers. This means we will NOT develop new features and/or fix most of bugs. We left the tracker running in case somebody from community would like to work on it. Sorry for the inconvenience.
State: new new: Initial state. As long as issue is in this state, the work on the issue has not yet begun. opened: Opened state means developer started working on the issue. Feature/Fix will probably be in the next release. postponed: This means developer is not working on it now, for some reason it cannot be implemented now. Issue may be opened again in the future. upgraded: Issue is in upgraded state when developer made changes to the program and new version was released. closed: This means the user is satisfied with issue results and no more changes are needed. invalid: These issues cannot be solved. ignored: Developer decided to take no action on this issue. returned: Program changes were made but user is not satisfied and returned the issue.
In a news you telling that deobfuscation is no longer develop because it's hard to do and
everything, okay, i believe it really is. The question is how i can solve this problem for
myself? i have in mind to read code of your decompiler and manage pure action script byte
code by myself, it would be like assembler in IDA, right? Or is it possible to manage
deobfuscation without reading sources of decompiler? i have quite few ideas how decompiler
is working and which problems can cause an obfuscation, so it would be helpful if JPEXS
developers give me an advice or suggestion about my future actions if i want deobfuscate
an swf file.