JPEXS Free Flash Decompiler Issue Tracker

If you are looking for the decompiler itself, visit

List of issuesList of issues

#698 set,get,override fields unnecessarily debofuscated with §
Author: user Berni11
Date created:
Type: bug
Visibility: Everybody
Assigned to: admin JPEXS
Labels: Deobfuscation
State: closed Help

> What steps will reproduce the problem? > What is the expected output? What do you see instead? It's about a bug in the decompiled ActionScripts: FFDec adds sometimes these characters, which produces Syntax Errors: § I saw them, when the text is: .set, .get and .override FFDec makes them to these: .§set§, .§get§ and .§override§ > What version of the product are you using? On what operating system? I'm using version 3.0.0 and operating system is Windows Vista 32Bit. > Please provide any additional information below. Attach the file you have problem with if neccessary. If you do not want to publish files YOU CAN CHANGE VISIBILITY TO PRIVATE
Is it AS3 or AS1/2 file?
Title: →set,get,override fields unnecessarily debofuscated with §
I don't know which ActionScript Version it is, as I didn't created the .swf file, but I think it is AS3. Other Flash Decompiler which I have tried didn't added these characters. If it helps, I have added one of the AS files (extracted with FFDec) and the swf file it came from. (10 KiB)DownloadWrapper.swf (115 KiB)
This should be fixed in latest nightly build.
State: new→upgraded
Assigned:admin JPEXS
Thanks for the update, but the new nightly build has another bug now: it add this the character (§) now to every void.
It also adds the character (§) to names which contains a umlaut (ä, ö, ü))
This should be fixed in latest nightly build, try it.
Same for void. as3.swf/TestMovie: public function testStatic() : §void§
State: upgraded→returned
the void is fixed in 4.0.2 release
State: returned→upgraded
Problem is back in 4.0.5
Please try the latest nightly build. I can't find any problem in Wrapper.swf/
realmaster42: Can you reproduce it with the latest nightly build?
@honfika, nope, it's fixed now, thanks.
Ok thanks, Berni11's problem was fixed, too. (More than2 months ago) So I close this issue.
State: upgraded→closed