Yes, 1.0.1 saves aren't compatible, since the code base is completely new.
That's... something weird
I no longer have that saveYes, 1.0.1 saves aren't compatible, since the code base is completely new.
That's... something weird
Every 1.1.x save should load fine. The error above, I see for the first time in… ever. I could load my 1.1.7 file I had (to test the luggage situation) just fine with 1.1.9. Does this also happen when you try to load a recent save?
After the date with Minerava, the quest log/notebook brings up this errorYes, 1.0.1 saves aren't compatible, since the code base is completely new.
That's... something weird
Every 1.1.x save should load fine. The error above, I see for the first time in… ever. I could load my 1.1.7 file I had (to test the luggage situation) just fine with 1.1.9. Does this also happen when you try to load a recent save?
The date is her last quest for this update. This seems to be an issue with the "To be continued" message. Please ignore that tab until I have a patch out.
Gemma's content for this version ends with her "hair cut".
By chance, you don't know where that might have happened?I noticed that about half way through the "H" key stopped hiding the dialog box along with the mouse wheel rolling back the dialog incase you accidently clicked to fast..
Not really somewhere around the middle.. I know I know
where is the middle... I think somewhere in the area where or just before the night visit of Cindy
Updated the post, but also here, so no one has to scroll up.What are the fix's
Not really somewhere around the middle.. I know I know
I'm having the same issue, can't hide the dialogue box and can't roll back. I first noticed it, I think, when Judy was speaking to MC right before meeting the girls for breakfast after everyone woke up with various "upgrades".
I'm out of house for the evening.
For me it was a straight run through with a copule of saves without leaving the game.
screen MainMenu_Judy(judyItem):judyItem needs a default value of Nonescreen notify(message):message needs a default value of Nonescreen SettingsButton(thisLabel, tooltipInfo, thisAction=[ NullAction () ], isSelected=False, isSmall=False)tooltipInfo is a positional argument, but you use it like a keyword argument when you create SettingsButton instances. Either make it a kwarg (move it to the end of the params and give it a default) or change how you instantiate SettingsButtonsthisAction and isSelected as kwargs, but use them like positional argumentsSettingsButton(_("Info"), [ Function (game.toggleVariable, "affection system sheet") ], game.isTrue ("affection system sheet"), tooltipInfo="Adds a small button to open up an overlay displaying current affection values.")
# ^ correct ^ kwarg called as a positional arg ^ kwarg called as a positional arg ^ positional arg called as a kwargSettingsButton. Renpy must be doing some interpolation to say "I see you did this but you must have meant that".location_1st_floor_east, which is on the west side facing eastlocation_1st_floor_east_turn, which is on the east facing westlocation_1st_floor_east_turn, Picture — 1st Floor — West goes to location_1st_floor_east_picture instead of location_1st_floor_west_picture
Thank you for the list.
), buttooltipInfo="..." it will pulls it in the argument list back into the kwarg positions. All other keyword arguments will move one step to the front, if used as keyless argument.The issue seems to have resolved itself, possibly after a save and load. Didn't quite notice when but it seems fine now.
