CensoredUsername / unrpyc

A ren'py script decompiler
Other
824 stars 149 forks source link

Error -3 while decompressing data: incorrect header check #130

Closed Lyk5t closed 4 months ago

Lyk5t commented 2 years ago

hello, when I parse the rpyc file of a game, I get this error, can you please update the software?

CensoredUsername commented 2 years ago

I can't help you just with this information, please read the README section on issue reports.

Lyk5t commented 2 years ago

I am very sorry, I sent the wrong message, I will read the necessary place and get back to you

Lyk5t commented 2 years ago

I'm really sorry for sending the wrong message now i will explain the problems like this

I used the latest released version of unrpyc As you said in the readme, I threw the bytecode.rpyb file into the game/cache folder, then I put the un.rpyc into the game folder and ran the game. The result was no parsing, even the .rpa files.

game i tried Winds of the Destiny v0.6.0 the renpy version this game uses is 7.3.5

Finally, I throw the outputs of the game. traceback.txt unrpyc.log.txt the files i'm trying to parse extractD.zip

PS: sorry my english is not good

Lyk5t commented 2 years ago

hello, any progress?

CensoredUsername commented 2 years ago

rather busy rn, will investigate when I have time.

Lyk5t commented 2 years ago

so good work

madeddy commented 2 years ago

hello, when I parse the rpyc file of a game, I get this error, can you please update the software?

AFAIK this isn't a problem with unrpyc, but with the used header in the games unrpyc files. The files you attached uses in the begin of the first line of every script file MY_HEADER instead of RENPY RPC2 as it should be.

You can thank the developer(s) of this software app for the chosen change of the files to make them inaccessible like you experience just now. You can try to find some script which repairs this called "rpyc corrector" or renpy corrector or some similar name.

Good luck.

Lyk5t commented 2 years ago

hello, when I parse the rpyc file of a game, I get this error, can you please update the software?

AFAIK this isn't a problem with unrpyc, but with the used header in the games unrpyc files. The files you attached use in the begin of the first line of every script file instead of as it should be.MY_HEADER``RENPY RPC2

You can thank the developer(s) of this software app for the chosen change of the files to make them inaccessible like you experience just now. You can try to find some script which repairs this called "rpyc corrector" or renpy corrector or some similar name.

Good luck.

believe me, I guessed that the problem was related to ora, but I couldn't do anything because my python knowledge was insufficient. There was a my_header variable in the renpy files, I thought it was probably the problem here, probably the variable name here was not the same everywhere, I guess I guessed partially right

CensoredUsername commented 2 years ago

Did you try running the command line tool with the --try-harder option as listed in the README?

Lyk5t commented 2 years ago

Did you try running the command line tool with the --try-harder option as listed in the README?

no i haven't tried From https://github.com/CensoredUsername/unrpyc/releases bytecode.rpyb I downloaded the file and put it to the right place and ran it. Do I need to run it otherwise?

renkerenke commented 2 years ago

Did you try running the command line tool with the --try-harder option as listed in the README?

I stumbled over this unrpyc issue with a renpy application and the option worked for me. Thanks a lot!

CensoredUsername commented 8 months ago

@Lyk5t the injector might not work if people messed with the file format, so then the command line tool is the only option. Please consult the README for instructions if this is an issue.

@renkerenke Glad to hear that. That option causes unrpyc to accept a variety of things that aren't the official file format, and sometimes one works ;)

CensoredUsername commented 4 months ago

Closing this as there's been no activity for a long time, and this seems to just be obfuscation issues.