- Dec 17, 2017
- 838
- 487
Sry for the late reply folks.
But, let's just clear this up about the Unren versions:
Unren 0.9 itself has no code changes too 0.8 version. The only difference is it comes with a "hacked" unofficial (and by now outdated) unrpyc for decompiling RenPy scripts, because the multiprocessing in unrpyc did not work with post 7.2 RenPy. So Sam removed it. Slower with single core decompiling, but working. However the 0.9 version can be seen as stable for everything except decompiling.
So. Reasons and current state:
Sam indented to rewrite Unren completely in python, we talked some about this but he sadly didn't have much time for it (so far...). I did then most of the python rewrite early this year, some testing and run into a few problems. I came then to expect for the foreseeable future many additional problems, because we wanted to support different things like:
Any more questions? Ask away.
...
That Sam, or the guy who now collaborate to the project (don't remember his pseudo), make a new version.
I don't think Sam will work on the current/old Unren again or change the dev state of 0.9. AFAIK(!) There are good reasons....
Sam, are you working on a new version of v0.9 UnRen-dev.bat? If so, do you have a targeted completion date? Thank you.
But, let's just clear this up about the Unren versions:
Unren 0.9 itself has no code changes too 0.8 version. The only difference is it comes with a "hacked" unofficial (and by now outdated) unrpyc for decompiling RenPy scripts, because the multiprocessing in unrpyc did not work with post 7.2 RenPy. So Sam removed it. Slower with single core decompiling, but working. However the 0.9 version can be seen as stable for everything except decompiling.
So. Reasons and current state:
Sam indented to rewrite Unren completely in python, we talked some about this but he sadly didn't have much time for it (so far...). I did then most of the python rewrite early this year, some testing and run into a few problems. I came then to expect for the foreseeable future many additional problems, because we wanted to support different things like:
- old and new RenPy versions; with this the need for
- python2 and 3 and
- multi-OS...
Any more questions? Ask away.
Uhm... AFAIK RenPy 7.4 is still just in the pre-release stage and nobody shouldn't use it for productive work. Are you sure you didn't mix something up there? Or do i misunderstand somehow?You're probably forgetting nothing. The version 7.4.0 of Ren'py introduced many changes in the way it deal with Python, what make unrpyc.py being actually unusable. But the "un.rpyc" version of the tool still works perfectly.
Last edited: