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 issues#2254 02/07/2024 14:16:59 SEVERE Duplicate pack path found (goku_fla.goku_b_243)!
Author: 
Nathan.S
Nathan.SDate created:
Type: bug
Visibility: Everybody
Assigned to:
Labels: Duplicate pack
State: opened 
> What steps will reproduce the problem?
> What is the expected output? What do you see instead?
> What version of the product are you using? Is it "nightly build"? Which operating system
do you have?
> Please provide any additional information below. If the problem is related to a SWF
file, attach it here, otherwise we can't help you.
DAT78.swf (4,028 KiB)So first and foremost I have taken action on the following steps:
I have been trying to locate the file(goku_fla.goku_b_243)! but I am unable to
Next I have installed an up to date version of JPEXS Free Flash Decompiler but the error
notification still persists
I have searched on the internet and youtube how to rectify this error, and unfortunately
there has been no necessary information that has been provided whatsoever
The version of JPEXS Free Flash Decompiler that I am currently using is: Version 20.1.0
that has been installed onto my computer today it was an .exe file of the application.
This is the error notification when opening the JPEXS program:
SEVERE Duplicate pack path found (file of the name) the notification is on the log section
on Jpex free flash
I have attached a screenshot of the notification error
Originally the file is a ssf format but I changed it to a swf to edit it, but in need of
assistance to resolve the notification error above.
Screenshot 2024-07-02 144123.png (393 KiB)The file I have attached is this one, its a DAT78.ssf file and it needs to be changed into
a swf format i.e. DAT78.swf to find and eliminate the notifcation error on JPEXS
DAT78.ssf (4,028 KiB)
In this file there are two scripts with the same name "goku_fla.goku_b_243".
If FFDec detects this, it prints the message you encountered, and for purpose of
decompilation, it displays only first script of that name.
I don't know how this can happen or how these scripts are then used.
It may be a result of some kind of obfuscation.
I think ignoring the latter scripts is a good strategy to avoid problems.
You should probably not worry about this problem.
two_scripts_same_name.png (52 KiB)State: new→opened