- Dec 24, 2018
- 3,137
- 6,582
They're likely referring to PhillyGames, the dev for "City of Broken Dreamers" & "Depraved Awakening."I don't know who 'philly' is or his games so I cannot say anything about that.
They're likely referring to PhillyGames, the dev for "City of Broken Dreamers" & "Depraved Awakening."I don't know who 'philly' is or his games so I cannot say anything about that.
the same and only.They're likely referring to PhillyGames, the dev for "City of Broken Dreamers" & "Depraved Awakening."
Thanks. I base a lot on the synopsis/overview the dev gives. I have seen CoBD around but the overview never seemed interesting enough for me to invest time in it (unlike Sins). DA seems a bit more interesting...maybe in the far future.They're likely referring to PhillyGames, the dev for "City of Broken Dreamers" & "Depraved Awakening."
I can't load any of my chapter II saves They all crash with:Let me know what you think?
I'm sorry, but an uncaught exception occurred.
While running game code:
File "renpy/common/00action_file.rpy", line 452, in __call__
renpy.load(fn)
Exception: Couldn't find a place to stop rolling back. Perhaps the script changed in an incompatible way?
Hmmm... so much for fixing the introduction to each new chapter.I can't load any of my chapter II saves They all crash with:
Code:I'm sorry, but an uncaught exception occurred. While running game code: File "renpy/common/00action_file.rpy", line 452, in __call__ renpy.load(fn) Exception: Couldn't find a place to stop rolling back. Perhaps the script changed in an incompatible way?
No worries, I don't mind playing from scratch this early in developmentSorry, last time I meddle with that.
Thanks for pointing it out. Something else to add to my "Don't ever do that shit again" list.No worries, I don't mind playing from scratch this early in development
Please, please bring Heather back before you end the game! She was the best part of the ProfessorUh, nope. I've decided (Or rather my Patrons have decided to) focus on A Father's Sins.
New releases will be every 3 weeks or so, depending on how long it takes to create each update.
I was shocked by the Poll results. Turns out I was spending a couple of weeks each month working on everyone's LEAST favorite game? Go figure. Should have actually ASKED my patrons a long time ago instead of assuming I knew what everyone liked.
So for the foreseeable future I will be focusing on SINS.
The PROF II will see another release or two - just to bring the chapter to a gracious conclusion - in my spare time.
Here's the Poll results from my Patreon page.
View attachment 1705093
And she never got any sexy time with any of the girlsPlease, please bring Heather back before you end the game! She was the best part of the Professor
Hm… No, that's not it. Your meddling with the code is fine.Hmmm... so much for fixing the introduction to each new chapter.
Sorry, will be the LAST time I meddle with that.
AT the end of each chapter, there's a prompt to save you game. Those should be working properly. Or at least I hope so.
or loading anything before the dream sequence at the end of chapter II.
intro.rpy
will land on the exact line of dialogue they were made on and do remember the dialogue (can skip forward). The ones jumping into day01.rpy
however will almost always rollback to a previous label, and do treat the dialogue as new (no skipping). The logical conclusion being that day01.rpyc
(the compiled file, mind) is not the one from Chapter II merged with the changes from Chapter III, but a newly generated one instead. That is the single most important thing you need to put on the aforementioned list of things to never do ever.day01.rpy
into the file: all saves will properly behave, again. And while this is not advisable for player's to do (as subsequent saves will likely also not be loadable on the official version) you yourself could adopt the habit of dropping the rpyc files from the previous release into the current one right before building the latter's release.I think the only difference is magic/superpowers as there is no tag called magic. It is a personal opinion though. There may be actual reasons behind the differences. Good luck with your game/project. Looking forward to experience yoursWhy are the tags under the title different than those under the description?
The above is also easily confirmed by dropping the rpyc file from Chapter II into Chapter III and having the latter's startup merge the changes fromday01.rpy
into the file: all saves will properly behave, again. And while this is not advisable for player's to do (as subsequent saves will likely also not be loadable on the official version) you yourself could adopt the habit of dropping the rpyc files from the previous release into the current one right before building the latter's release.
Uh, go play chapter III.Pixieblink I haven't played the last update, but please add an option to bring back maddy. I really, missed her (you may laugh but there were tears) in the last update. I know this game is extremely gruesome, but I hope she comes back in future updates. Maybe she would be dormant in any process or even be aloof in action, but let her resurrect and leave. I know I am a freeloader (and not a patron) but since this is a public platform I just expressed my opinion. Also, I am very grateful for this fast update and look forward to even faster updates. I cannot stand curiousity . Thanks for this wonderful experience, which is no less than any horror movie. Keep it up....
I've been looking at what you wrote. AND reading up on it.Hm… No, that's not it. Your meddling with the code is fine.
I just created a bunch of saves on the last version and tried loading them on the current one: the ones jumping intointro.rpy
will land on the exact line of dialogue they were made on and do remember the dialogue (can skip forward). The ones jumping intoday01.rpy
however will almost always rollback to a previous label, and do treat the dialogue as new (no skipping). The logical conclusion being thatday01.rpyc
(the compiled file, mind) is not the one from Chapter II merged with the changes from Chapter III, but a newly generated one instead. That is the single most important thing you need to put on the aforementioned list of things to never do ever.
The above is also easily confirmed by dropping the rpyc file from Chapter II into Chapter III and having the latter's startup merge the changes fromday01.rpy
into the file: all saves will properly behave, again. And while this is not advisable for player's to do (as subsequent saves will likely also not be loadable on the official version) you yourself could adopt the habit of dropping the rpyc files from the previous release into the current one right before building the latter's release.
Technical details can be gleamed fromYou must be registered to see the links.