Look at what version of the tool is now and how many more were in changelog. Maybe you should use something newer?
Stuff from the museum is just for looking at, not for use. Maybe try something from this century.
I admit this behavior of this so called "devs" pisses me of. Its base knowledge and even mentioned by the RenPy author to use just stable software version for productive work.... As for nightly builds, their use has become more and more frequent lately, so there is nothing left but to keep up with the times.
I am of the opinion there should be some "default" code thingy to deal with all the user statements and such, instead writing for every new one separate code.
So this is not a user statements, these are innovations of RenPy itself. There are changes in all engine files, especially in Ast.py and atl.py files.I am of the opinion there should be some "default" code thingy to deal with all the user statements and such, instead writing for every new one separate code.
Ok used version 8.2 for all, which I assume is the latest. I removed the single quotes from the filename (which I must admit never picked up) but still will not extract the images. FWIW I looked at the RPA file using a hex editor and seen the filename version also inside single quotes.Stuff from the museum is just for looking at, not for use. Maybe try something from this century.
Edit: Ups. He answered it already. Overlooked it.
I noticed also the game you cited has after the unpacking single quotes(') in the game name, which caused with my tool problems as i unpacked. You could try and remove them. Maybe this fixes it for you also... for me unpacking worked then, however i use my own tool.
Checked and corrected the processing of needless indexes in the archive (which were links to the "current folder"). Now unpacking.
Confirmed, ver 8.3 works fine. Thank you very much for your help and prompt fix. You Sir are a legend.
Yeah, you're right. I think i found it:
Strangely true.
In some cases, such a decision was enough.
store.atl.xxx be renpy.store.atl.xxx needed. Not sure. Don't remember where it was.extrapos and extrakw vars and their empty init state.
Well, so far it is, but I'm not sure that this is all the difference. I don't like the decompiled code obtained in this place, but there is nothing to compare it with, so I don't know what else is required.Ok. Interesting. The second looks like it should be worked in one code block somehow. There must be a way to integrate this "loc" thing with the other.
Anyway, i think i have seen something in the code of renpy which suggests it could instead ofstore.atl.xxxberenpy.store.atl.xxxneeded. Not sure. Don't remember where it was.
Also there is even more of this problems coming i think:You must be registered to see the links<-- this look like the issue we did have last year with the changes inextraposandextrakwvars and their empty init state.
v8.3 doesn't work on many VN's. It's borked, especially for scripts inside subfolders within "game".
This is the first time I hear about such a problem. In all the games that I decompiled, all the files with scripts were safely located, no matter how deep they sat.
Try the latest University of Problems for an example (the OEM version, not the compressed). I try your project periodically but I've run into issues depending on the version. I used v8.3 "console" with it and it crashes during decompile of rpyc... but unarchiving of rpa works fine in this particular case. I went back to using my decomp to sort it but am not able to keep mine updated due to mod update obligations (there's only so many hours in a day, you get it). Give that a shot and let me know your outcome.
I checked. All archives were unpacked and all script files were processed without errors. The game has started. The only problem that was is the brackets in the folder name, which, unfortunately, are not handled correctly. If you remove them, the script works fine.
This game is nearly 5 years old which means its in a old RenPy version made - in fact a v6.99. For this you should need a older UnRen version like the original one from User Sam. Its pinned here in this subforum.
There is AFAIK no such RenPy version. I think you have transposed digits there. The v7.4.11 exists instead and is the last version before the new RenPy 7.5.x and 8.x branches(lots of changes).
As explained above...
Obviously it was a typo bud, I'm quite aware of all the versions. The point remains, the issues I described are factual as of UFAv8.3