Quick request: under
screen choice(items):
could you please add
on "show" action Function(renpy.hide_screen, "say")
to hide the textbox? When the textbox opacity is nonzero, it hides some of the choices on certain menus.
Thanks.
If you have HomeBrew installed, just do "brew install megatools" and then use "megadl https://mega.nz/..." to download from the command line. Or use Chrome, which doesn't have the 2 GB limitation, but megadl works better.
Having trouble with 0.99. It won't load any saves from early in version 90 onwards with the error "AttributeError: 'absolute' object has no attribute '__dict__'". Basically, every save from September of 2023 onwards is failing.
Any ideas short of mass nuking everything from the last year and starting over?
I'm enjoying this story very much. Solid writing, good plot, funny dialog, etc.
One bit of technical feedback for future improvement: When users enable a non-transparent background for the dialog, it can get distracting to have that visible when there's no dialog. It often blocks important visual elements, makes it hard to see menu choices, etc. This is particularly noticeable during cutscenes, where the text box is just in the way, and when there are choices, where the bottom choices are half obscured behind the text box (which can't be hidden without also hiding the menu).
Just adding "window auto" goes a long way towards improving the behavior (as verified by typing it in the developer console), but there are still a bunch of stills with no dialog where an explicit "window hide" would be beneficial.
That (probably) minor tweak would be a big improvement.
I always just download a recent version of the Ren'Py SDK, drop the AVN into its folder, double-click the Ren'Py app, and run it from there. Pretty sure this one is based on Ren'Py 7, so for maximum compatibility, use Ren'Py 7.x (current is 7.7.1, I think). That also saves you the hassle of dealing with Apple's Quarantine behavior.
Well, I guess it isn't quite that simple. Four spots in the code are expecting None (in my_events.rpy, 01_asara.rpy, and two spots in worldmap.rpy), and should also be adjusted to check for 0. But that's probably a better fix than trying to handle NoneType everywhere that a numeric value would normally be expected.
Had to change to sys.stdout.write to actually see the log. Eileen is the culprit, and specifically, story_6. If I execute the code in that function by hand, it fails at Check_Req(ev_var) in line 90 with self.story == 6.
Digging in further, the call to player_inv.qty(AliceOutfit) returns None, rather than 0 as one might reasonably expect.
I suspect the fix is as simple as
def qty(self, item): for i in self.inv: if i[0] == item: return i[1] # returns quantity return 0
unless there's some reason to return NoneType instead of 0 for that function.
At least that keeps the exception from happening. I'm assuming that it will eventually get added to the inventory as expected when I do whatever thing I need to do.
Ran into a bug when loading existing saves:
While running game code: File "game/myscripts/my_time.rpy", line 3187, in script $ AllAvailableEvents() File "game/myscripts/my_time.rpy", line 3187, in <module> $ AllAvailableEvents() File "game/myscripts/my_events.rpy", line 80, in AllAvailableEvents File "game/myscripts/my_events.rpy", line 90, in AvailableEvents File "game/myscripts/my_events.rpy", line 217, in Check_Req File "game/myscripts/my_events.rpy", line 204, in Check_VarReq TypeError: '>=' not supported between instances of 'NoneType' and 'int'
Not sure if ignoring is safe or if I'm going to end up with weirdness.
For a quick workaround, edit options.rpy and add
define config.developer = True
Then quit and relaunch the app. When you get the problem (whether by progressing in the story or by loading from a save file), just hit Shift-O, then type:
stop sound fadeout 5.0
and hit return. Hit escape to get back out of developer mode.
Something very weird is going on in this build.
All saves from previous builds are broken, saying that they can't find a place to stop rolling back. I'm not seeing any missing labels, so I have no idea what's wrong with those.
But I tried restarting from scratch, and as soon as I quit and relaunch, even *new* saves from the last parts of Chapter 7 are failing to load.
I think maybe the rollback buffer size is way, way, way too small, and there are way too few jumps or statements that count towards Ren'Py knowing where you are.
I changed config.rpy to add this:
define config.rollback_enabled = True define config.hard_rollback_limit = 300 define config.rollback_length = 500
and now new saves are working as one would expect. The right fix is probably to put in more labels and jumps, I guess, but upping those limits from the current number (which is apparently not high enough for this AVN) will at least make it less fragile. *shrugs* Either way.
Seconded. Spelling/grammar nits are generally rare and minor, the pacing is comfortable, and it has solid storytelling with a compelling plot, interesting characters, a good sense of humor, etc. It is well worth reading.
I can only say that about roughly 6.2% of the AVNs that I've read or started to read, and most of the other titles on that short list are the sorts of titles that get updated once or twice per year, so I'm really impressed at the velocity you achieve without tanking the quality. 😁
+1. It drives the plot forward, giving a reason for the wife to leave the husband, which I'm assuming is going to happen at some point, and the MC isn't dating the wife's sister, so there's no hint of NTR there at all. If you want to change it, fine, but you shouldn't feel compelled to do so. Some people are fragile and will complain about everything, but if you cater too much to them, you'll end up with a story that's shallow and boring.
Weird punctuation nit in the latest update: "Now and then" is a common English idiom, and at one spot, you used a clause ending with "now" followed by "and" to start a compound predicate beginning with "then", which makes it look like you're using that idiom.
But then the sentence unexpectedly goes on afterwards. When readers realize it wasn't intended as an idiom, they can get very confused (because the remainder of the sentence is unparseable at that point) and may be forced to go back and reread the entire sentence to figure out what's actually going on.
Even though you don't normally use a comma before a compound predicate, this is one of those spots where it is *really* needed. Changing it to "...the address now, and then make..." would greatly improve understandability.
Yes, I'm arguing to violate Chicago or whatever, but adding a comma between those phrases isn't strictly wrong, and improves readability in this one weird edge case, so... yeah. Or you could just repeat the subject and make it a full compound sentence.
The Mac version has some weird stuff going on:
The result is that if somebody tries to run it with a trusted copy of Ren'Py (which I always do for malware reasons), it breaks badly. No idea if it would work when you run it by double-clicking or not.
Either way, you should probably stop taking payments for the old versions when you release the new ones, or at least change the description to say "This is NOT the latest version. Go __here__ to get the latest version" at the top.
After all, anybody who buys this version today for ten cents more than v0.18 is probably going to feel cheated. :-)