JPEXS Free Flash Decompiler Issue Tracker

If you are looking for the decompiler itself, visit https://github.com/jindrapetrik/jpexs-decompiler

NEW : We have got a new blog where we post some interesting SWF internals info.

List of issuesList of issues

#2549 ActionScript variable names are changed when saving modified source in SWF files
Author:
Date created:
Type: bug
Visibility: Everybody
Assigned to:
Labels: AS1/2
State: opened Help

> What steps will reproduce the problem? Paste ActionScript source code into containing multiple variables into an existing .as file, fully overwriting the file's original source, save the .as file, then save the .swf file. The same behavior is reproducible using the Import Scripts functionality and if the original source is deleted, saved, then the new source pasted. > What is the expected output? What do you see instead? After saving the .swf, the source in the modified .as files is not identical to source pasted from the clipboard. Variable names are changed, such as "_loc8_" becoming "_loc16_". This breaks key functionality. > What version of the product are you using? Is it "nightly build"? Which operating system do you have? JPEXS v.24.1.0 and Windows 11. > Please provide any additional information below. If the problem is related to a SWF file, attach it here, otherwise we can't help you. The original and modified .swf files are attached. The expected source code, which is being pasted into the .swf using JPEXS, is also attached.
Download(Original) TrueHUD_Widgets.swf (33 KiB)Download(Modified) TrueHUD_Widgets.swf (34 KiB)Download(Expected) TrueHUD_InfoBarBase.as (27 KiB)Download(Expected) TrueHUD_PlayerWidget.as (38 KiB)
What do you mean by "This breaks key functionality." ? There are just local registers, it does not matter how they are named, they are not accessed outside the function. When editing AS in FFDec, local registers inside function are assigned starting with function parameters, then rest of them in order of appearance. Other compilers may assign local register names differently. If you think it really breaks, then tell me the specific point - a method, where this is a problem. It should be only cosmetical, not a reason to break program logic.
State: new→opened