joelurmel
Engaged Member
- Nov 3, 2022
- 2,650
- 4,704
- 397
Your confusion stems simply from the fact that the latest Ren'Py v7 uses Python 3.9, which is why I use the master version.Then I don"t understand the line I quote, because it reads contradictory to me.
Anyway, seeing you've taken apparently the caretaker job for unren:win, i got some thoughts. If you allow.
Ok. This came just to mind.
- I think its of advantage to make two unren versionsin the future. One for v8 and another for the old Ren'Py. Pre v8 Ren'Py is EOL, so will not significantly change anymore, means with this also not the unren tools.
- The old version would be possible the last you make and will not need care anymore.
- The new version will have less code and will be way less convoluted and very much simpler all around, which will ease maintaining it.
- You changed a lot of cmd code, so i would use a new name-suffix to prevent confusion. Unren+current and legacy or +renpy version or something else.
- Maybe a new thread for a new unren could be of of advantage. This could replace the others(could still be linked the new), divide from the antique postings and where you have control of the first post(Descriptions, attachments, links).
![]()
I have no problem maintaining all Ren'Py version in a single code, and it's even much simpler for me, as long as I haven't finalized the code I use for testing before a Python version that would be faster and, above all, would report errors in child scripts and not just those in PowerShell, as is currently the case.
I'll take note of your recommendations and think about them, and I'll definitely do that with the new project.