CensoredUsername / unrpyc

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

common.rpyc #120

Closed corona57 closed 3 years ago

corona57 commented 3 years ago

common.zip

Unable to open common.rpyc. help me! oh

CensoredUsername commented 3 years ago

Please provide additional information as requested in the README

corona57 commented 3 years ago

common.zip

Common.rpyc açılamıyor. bana yardım et! oh

Ekran Görüntüsü (36)

madeddy commented 3 years ago

The developer manipulated the rpyc file format so decompiling isn't easily possible like we see here.

Please provide if possible the name of the game/developer and from the games directory the file ".../your_games_path/renpy/script.py".

CensoredUsername commented 3 years ago

File is pretty damn mangled. Entire thing is base64-encoded from a cursory look can you confirm that bytecode.rpyb also doens't work?

corona57 commented 3 years ago

bytecode.rpyb in the file does not exist.

madeddy commented 3 years ago

bytecode.rpyb in the file does not exist.

No. I think you do not understand what @CensoredUsername say'd.

There is a second way to decompile game files and it IS clearly described in the readme for unrpyc how to get the files. But to understand this a user needs to read the information actually: https://github.com/CensoredUsername/unrpyc#game-injection releases

corona57 commented 3 years ago

hmm understand thanks.

corona57 commented 3 years ago

I did what you said but it still did not open.

CensoredUsername commented 3 years ago

Seems that whoever made this file used some non-trivial obfuscation, it's not too hard to break if you know some python reverse engineering (you can just rip the data straight out of the engine with some tools), but I have no interest in figuring it out myself as it won't be significantly portable to other games.

corona57 commented 3 years ago

I don't know reverse engineering. Believe me, if you make a video narration, people will be delighted .... for example on your youtube channel.

CensoredUsername commented 3 years ago

Here's the thing. reverse engineering isn't a process, it's a skill. Someone is trying to hide something from you, and you have to figure out how they did that so you can uncover it. But, the moment you publish this they have access to this solution as well and they can find a different way of hiding it, rendering all the published data moot. This means that the only way to break things effectively is to keep your approach secret.

I'm only interested in the public usability of this tool, so have little interest in that. There's a bunch of attacks that I know would easily work, but I can also think of ways to guard against them. So you need to be able to modify these attacks, and understand how they work. A youtube tutorial won't teach you understanding of programming and reverse engineering. You'll have to figure out how to get the data out of the engine on your own (or get someone to do that for you) and not publish it until it's broken for it to stay useful. Then, you can still use this tool to decompile it back to normal script files.

madeddy commented 3 years ago

I also asked two days ago for more information with wich we can work but you did not give them. More info gives us possibly a better view on the problem. Sometimes its just one little detail and without it nobody can help.

corona57 commented 3 years ago

after all there is an rpyc file and the program you did it cannot open. So this program is useless trash.

CensoredUsername commented 3 years ago

I do not make any claims of supporting anything but stock ren'py, which this file is most assuredly not. You're free to modify it yourself to figure out that support, for which all code is available already. Insults are however not tolerated here, so this discussion is over.