Not quite. Just writing this program in python has complicated the support of the mechanisms used in the console version. I am currently working on a version written in C#. But I can't say when it will be released yet.I see you no longer have download links for the Windowed (GUI) Python version(s) from Gideon. Is support for those dropped permanently in favor console versions?
Okay, I'll check it out. I haven't checked what happens on commands 3-6 for a long time, all problems usually occur on the first two.Theres a bug in unren forall v8 -
if you run opt 1, then when its done, run options 3 through 6 at the least, then you get a red text pshell command error that it cant find the path/folder - cause it tries to write to \game\game\filename.
If you close and rerun the bat file, 3 thru 6 work fine.
It looks like after running 1 (and maybe even 2, didnt test it) %cd% doesnt get cleaned out from "current directory" including "\game" and those functions dont use %gamedir% so it, and list %cd%\game as part of their cmd path, so it gets mashed together.
I commonly use 1 (if needed), and the, 3, 4 and 6, for new games/updating games (as i sometimes clean out everything but saves), and so quickly got in the habit of punching one after the other, and noticed this.
It's strange, but everything worked out fine for me. Both versions. In order, I executed commands from 1 to 6. All worked correctly.Theres a bug in unren forall v8 -
if you run opt 1, then when its done, run options 3 through 6 at the least, then you get a red text pshell command error that it cant find the path/folder - cause it tries to write to \game\game\filename.
If you close and rerun the bat file, 3 thru 6 work fine.
It looks like after running 1 (and maybe even 2, didnt test it) %cd% doesnt get cleaned out from "current directory" including "\game" and those functions dont use %gamedir% so it, and list %cd%\game as part of their cmd path, so it gets mashed together.
I commonly use 1 (if needed), and the, 3, 4 and 6, for new games/updating games (as i sometimes clean out everything but saves), and so quickly got in the habit of punching one after the other, and noticed this.
Hmm. I always copy the batch file to the root of the game folder, i dont use the copy/paste of the path in, and run it from the game's root folder. Is that what you did?It's strange, but everything worked out fine for me. Both versions. In order, I executed commands from 1 to 6. All worked correctly.
I found the problem spot and fixed it. Indeed, after unpacking, the script did not return to the root folder. But after decompilation it came back, so I didn't notice the problem.Hmm. I always copy the batch file to the root of the game folder, i dont use the copy/paste of the path in, and run it from the game's root folder. Is that what you did?
Heres a test:
You don't have permission to view the spoiler content. Log in or register now.
So then if i just close the cmd window and rerun - 3 works as expected.
I am confused.......And I have both python 2.7 and 3.7 installed in the directory "C:\Python37" or "C:\Python27"...
This program uses python, which is part of the game engine, and not a third-party version.
Indeed.I was wondering if someone could give me an example of what Deobfuscate would be used for? Is there some jiggery pokery that can be done on rpa or rpyc files?
RPA-3.0 to RPA-4.0 /RPI-3.0 /ALT-1.0 and such for rpa filesRENPY RPC2 to MY HEADER or whateverProbably the second. I just wanted to say that any other versions of python other than the one in the game folder don't matter.I am confused.
Official Python is now a third party app? And The hacked and cut-down version in RenPy is, if we follow your statement above, a real "Python" install? Really? This would be a new and surprising information for me.(Did this answer just come wrong out or did your translator tool muck this up?)
Yes, but sometimes the changes are really crushing. Sometimes even so much that they do not give in.Anyway, its mostly a waste of time on their side. There is always someone who reverses this.
If the console closes itself during execution, then there is some kind of critical error. Run the console separately and run the script from there, then error should show up. Cleaning of all temporary files both was and remained available.I've noticed after switching to the unren for all (8.1 presently) that it isn't uncommon for it to do a poor job of cleaning up after itself. As an example I just did Misfits and was left with the decompiler directory as well as decomp.cab and decomp.cab.tmp files. And it is repeatable.
Now I'm beginning to wonder if this only happens when the script fails and I don't notice. The window closes on its own when attempting to decompile this game, so I am guessing that some exception occurred and the script died.
If the console closes itself during execution, then there is some kind of critical error. Run the console separately and run the script from there, then error should show up. Cleaning of all temporary files both was and remained available.![]()
\____/_/ /_/_/ |_|\___/_/ /_(_)_.___/\__,_/\__/ - forall(v8.1) (230126)
Sam @ www.f95zone.to
----------------------------------------------------
Enter the path to the game, drag'n'drop it or press enter immediately if this tool is already in the desired folder:
Available Options:
1) Extract RPA packages
2) Decompile rpyc files
3) Enable Console and Developer Menu
4) Enable Quick Save and Quick Load
5) Force enable skipping of unseen content
6) Force enable rollback (scroll wheel)
7) Deobfuscate Decompile rpyc files
8) Extract and Decompile
9) All of the above
Enter a number:2
----------------------------------------------------
Extracting _decomp.cab...
Searching for rpyc files...
-pc\game\ was unexpected at this time.
The script didn't like something on the path. It is difficult to say what exactly, since there is no all path. But I'm pretty sure it's not a hyphen or a space. Just checked them out.Extracting _decomp.cab...
Searching for rpyc files...
-pc\game\ was unexpected at this time.
Parenthesis perhaps?The script didn't like something on the path. It is difficult to say what exactly, since there is no all path. But I'm pretty sure it's not a hyphen or a space. Just checked them out.
Parentheses in the path don't work. Only PowerShell handles them.Parenthesis perhaps?
"MISFITS-Part2_(v13.2)-pc"
Any potential for a slightly better fail?Parentheses in the path don't work. Only PowerShell handles them.
I don't quite understand what you mean. If the question is about the possibility of processing parentheses with a script without crashes, then I will disappoint, I spent a lot of time on this question, but I could not solve it. Only if someone else finds the right solution that can be applied to the current implementation.Any potential for a slightly better fail?