inside jennifer , lustyverse:shackbang , lustgyverse: passsion on display
In the case of Inside Jennifer, it says Season 1, but the game was actually completed in Season 1, and I heard directly from the developer that there are no plans to make a Season 2.
Please could you make an new script for the new version?
In the v0.8 is not working the old script... I put the script on the game folder because in this version there is not mod folder.
That should still work. I just checked and they didn't change that portion of code at all for v0.8.0. I just tested it and it is still working for me. Not sure what to tell you there.
But you also shouldn't need the script anymore. It only needs to run once in any version of the game. They store that data in the persistent file so once you run it the change is permanent across all versions until they change how they manage the save names. I actually updated the instructions the other day to recommend deleting it after booting up the game once.
That should still work. I just checked and they didn't change that portion of code at all for v0.8.0. I just tested it and it is still working for me. Not sure what to tell you there.
But you also shouldn't need the script anymore. It only needs to run once in any version of the game. They store that data in the persistent file so once you run it the change is permanent across all versions until they change how they manage the save names. I actually updated the instructions the other day to recommend deleting it after booting up the game once.
The Ren'Py app that comes with this v0.8.0 version is slightly modified, a custom key is used for the encoding/decoding, so the usual rpyc decompilers won't work with the files... I think I saw already this trick at a game earlier but I don't know the solution for the decompilation at the moment. Anyway I tried the universal crack by smasher_the_smith and it's still working but starting a new game then at the 1st choice selecting either one makes the game crash... It seems the game is buggy because that crack works correctly with v0.7.0. Haste only leads to mistakes.
It sounds like you might have already figured out how to decompile it, but their decryption implementation is located in the {game-root}/renpy/script.rpy file, within the build_archive_rpyc() function. I made an update to my local copy of unrpyc to decrypt using their algorithm but it's a quick hack and not something ready to release to others yet.
But the great part is that it isn't needed except for people like me who prefer to run it from the command line. Since the game injection version of
You must be registered to see the links
uses the local RenPy functions of the game to decompile, it means it uses their own code to decrypt the files. Just make sure you use the .rpy file not the .rpyc. It can't read the .rpyc version because they changed the algorithm for reading those files.
As for the crashing, it looks like they intended to replace the relationship_points variable with two new ones so they could track the infidelity of each MC separately, but then they never actually used those two new variables. Everything still refers to relationship_points, but they deleted it to add man_or_pussy and thot_or_wife.
I see you uploaded an all-in-one version with a fix included and pre-cracked, but for anyone who already downloaded a copy and doesn't want to download it all again attached is a file that fixes the bug. Drop it anywhere in your /game folder. I recommend creating a /game/mods folder to place it in so it is easy to find and remove later. They will definitely be fixing this one before Steam release since it is literally game breaking.
For easy searching for the error, it looks like this:
Code:
NameError: name 'relationship_points' is not defined
Yes. I intentionally write my mods in a way to avoid overwriting files so that they don't need updated every game version. They only need updated when the game developer happens to change the functionality that I am overwriting or replacing in a way that isn't compatible with my code anymore.
They actually added two new characters with this update.
Yes. I intentionally write my mods in a way to avoid overwriting files so that they don't need updated every game version. They only need updated when the game developer happens to change the functionality that I am overwriting or replacing in a way that isn't compatible with my code anymore.
They actually added two new characters with this update.
Okay, I played the update. v0.8.0. Here are my thoughts (and be warned, I have a lot to say):
Although before that, Inceton is doubling down on the DRM, aren't they? We can't even decompile the rpyc files now, unless you specifically know what you're doing? Great.
Okay, I played the update. v0.8.0. Here are my thoughts (and be warned, I have a lot to say):
Although before that, Inceton is doubling down on the DRM, aren't they? We can't even decompile the rpyc files now, unless you specifically know what you're doing? Great.
Damn... I'm trembling with every new piece of news about this incredible game...
Right now, I'm hovering my mouse over your spoiler... I don't want to see it... or do I?
Damn, why do you post things like this?
Damn... I'm trembling with every new piece of news about this incredible game...
Right now, I'm hovering my mouse over your spoiler... I don't want to see it... or do I?
Damn, why do you post things like this?
Are there actually signatures for Thoth on Trial?
Although I searched around a bit, I couldn't find anything...
I'll probably have to create one myself.
!!! Don't use the attached file without reading the warnings inside method 2 first !!!
Inceton updated the save system starting in v0.6.0 in a way that breaks for anyone with a large number of saves. This same bug is present in v0.7.0+, but with a higher limit. You will know you encountered this specific bug when the game crashes whenever you enter the save/load screen and you see an error message like this (the line number might change in future versions):
Code:
File "game/screens.rpy", line 940, in <module>
IndexError: list index out of range
You will only see this error when you are on a page with a used save slot higher than the limit. If you are on a page higher than the limit but have no saves on that page, the game will not crash. If you have a save on a page higher than the limit, but are currently on a page lower than the limit, the game will not crash.
The limits are as follows:
v0.6.0 = 500 saves (50 pages)
v0.7.0+ = 1,000 saves (100 pages)
Inceton "fixed" this in v0.7.0 by doubling the limit (as I predicted they would), but people managing to create this many saves are going to hit that new limit fast so it's really just a temporary band-aid. Their "fix" also only works for people who never played v0.6.0. If you played v0.6.0 you will still be stuck at 500 save slots on v.0.7.0 because they screwed up that too.
Hi, please could you make an new script about the saves expansion for the new version?
In the v0.8 is not working the old script... I put the script on the game folder because in this version there is not mod folder.
Guide to Inceton's Encryption How to Decompile Thot on Trial v0.8.0 and Make 3rd Party .RPA and .RPYC Files Work
That subtitle is a mouthful.
Inceton added a form of encryption to their files in v0.8.0. This causes several issues, including being unable to decompile the .rpyc files with common tools and being unable to load 3rd party files distributed in .rpyc form (that includes .rpa files since they are simply an archive with internally packed .rpyc files). This means things like URM break and crash the game before it even finishes loading.
Fortunately this can all be worked around. Here a few methods you can use. I will try to keep this updated if they make any changes.
Decompiling .rpyc Files
The nature of the way they implemented the encryption means that any tool which hooks into the local copy of the RenPy functions included with the game will still work. This is pretty always going to work since otherwise the game couldn't read the files. One such tool is
You must be registered to see the links
. The command line version won't work without tweaks, but the injected version will.
Making 3rd Party Files Work
Since they modifed the way RenPy loads and saves source files, we need to as well. I created a file that does this for you. Download it, then copy and paste that file into the game's /renpy folder and overwrite the existing file. All it does it adds back the old read/write functions alongside the new ones and attempts to use them if the encrypted versions fail.
You must be registered to see the links
You must be registered to see the links
I normally try to avoid making mods that require overwriting files, but I see no choice in this case. I could monkey patch the Script class, but all that would accomplish is changing which file I would need to overwrite. I would then need to overwrite __init__.py file to modify it's the import_all() function. And so forth up the chain.
Technical Details on the Encryption
This section is for other mod developers or simply those curious. If you are a mod developer and ship your mod files pre-compiled in .rpyc or .rpa format and wish to encrypt your mod files so they work without users having to utilize my method above for making 3rd party files work, you will need to modify your packaging tool to implement the same encryption algorithm.
Hi, please could you make an new script about the saves expansion for the new version?
In the v0.8 is not working the old script... I put the script on the game folder because in this version there is not mod folder.
I tested that earlier and it is still working for me. They didn't change that code so I don't see how it would break now. You shouldn't even need it since you ran it before and it is a run-once-forever solution unless you are deleting your persistent file.
There won't be a mod folder unless you happen to install one of my mods. You would need to create it manually. It's no big deal if you don't; I just like to be organized and keep things clean. Makes deleting mods really easy instead of hunting for the file(s) that you can't even remember the name of within a list of 50+ other files.
Let's try to debug why it isn't working for you. Please answer the following questions or perform the following actions:
How specifically isn't it working? Be very precise please
Is the game crashing on launch (before you see the menu)?
Is the game launching but then crashing when you try to save/load (like it did in v0.7.0)?
Something else?
Please include screenshots or copy and paste any errors you are seeing
What operating system are you running (Android, iOS, Linux, Mac, Windows)?
Did you copy over old saves or modify files in the save directories in any way?
Did you run an old version of the game since you last ran v0.7.0?
What specifically did you copy? Did you copy the mod file from the old version of the game? did you copy over a version you had saved elsewhere? Did you redownload it?
Can you provide a link to the F95Zone post you got the game download link from (not my save fix mod)?
Enable the developer console if you haven't already. If you don't know how to do so, my crack includes it. Then open the dev console (Shift + O), run this command, and tell me what it outputs: len(persistent.save_name_list). It should be a number (500, 1,000, or 5,000). The Escape key exits the console, or you can type exit and then press enter
Guide to Inceton's Encryption How to Decompile Thot on Trial v0.8.0 and Make 3rd Party .RPA and .RPYC Files Work
That subtitle is a mouthful.
Inceton added a form of encryption to their files in v0.8.0. This causes several issues, including being unable to decompile the .rpyc files with common tools and being unable to load 3rd party files distributed in .rpyc form (that includes .rpa files since they are simply an archive with internally packed .rpyc files). This means things like URM break and crash the game before it even finishes loading.
Fortunately this can all be worked around. Here a few methods you can use. I will try to keep this updated if they make any changes.
Decompiling .rpyc Files
The nature of the way they implemented the encryption means that any tool which hooks into the local copy of the RenPy functions included with the game will still work. This is pretty always going to work since otherwise the game couldn't read the files. One such tool is
You must be registered to see the links
. The command line version won't work without tweaks, but the injected version will.
Making 3rd Party Files Work
Since they modifed the way RenPy loads and saves source files, we need to as well. I created a file that does this for you. Download it, then copy and paste that file into the game's /renpy folder and overwrite the existing file. All it does it adds back the old read/write functions alongside the new ones and attempts to use them if the encrypted versions fail.
I normally try to avoid making mods that require overwriting files, but I see no choice in this case. I could monkey patch the Script class, but all that would accomplish is changing which file I would need to overwrite. I would then need to overwrite __init__.py file to modify it's the import_all() function. And so forth up the chain.
Technical Details on the Encryption
This section is for other mod developers or simply those curious. If you are a mod developer and ship your mod files pre-compiled in .rpyc or .rpa format and wish to encrypt your mod files so they work without users having to utilize my method above for making 3rd party files work, you will need to modify your packaging tool to implement the same encryption algorithm.
Guide to Inceton's Encryption How to Decompile Thot on Trial v0.8.0 and Make 3rd Party .RPA and .RPYC Files Work
That subtitle is a mouthful.
Inceton added a form of encryption to their files in v0.8.0. This causes several issues, including being unable to decompile the .rpyc files with common tools and being unable to load 3rd party files distributed in .rpyc form (that includes .rpa files since they are simply an archive with internally packed .rpyc files). This means things like URM break and crash the game before it even finishes loading.
Fortunately this can all be worked around. Here a few methods you can use. I will try to keep this updated if they make any changes.
Decompiling .rpyc Files
The nature of the way they implemented the encryption means that any tool which hooks into the local copy of the RenPy functions included with the game will still work. This is pretty always going to work since otherwise the game couldn't read the files. One such tool is
You must be registered to see the links
. The command line version won't work without tweaks, but the injected version will.
Making 3rd Party Files Work
Since they modifed the way RenPy loads and saves source files, we need to as well. I created a file that does this for you. Download it, then copy and paste that file into the game's /renpy folder and overwrite the existing file. All it does it adds back the old read/write functions alongside the new ones and attempts to use them if the encrypted versions fail.
I normally try to avoid making mods that require overwriting files, but I see no choice in this case. I could monkey patch the Script class, but all that would accomplish is changing which file I would need to overwrite. I would then need to overwrite __init__.py file to modify it's the import_all() function. And so forth up the chain.
Technical Details on the Encryption
This section is for other mod developers or simply those curious. If you are a mod developer and ship your mod files pre-compiled in .rpyc or .rpa format and wish to encrypt your mod files so they work without users having to utilize my method above for making 3rd party files work, you will need to modify your packaging tool to implement the same encryption algorithm.
For what it's worth I'd also like to know. At the end of the day, we're all just a bunch of folks twiddling our fidget sticks so anything to break the monotony.