- Thread starter playb0y44
- Start date
You mean the one where I am stuck with 33/63? I can't, because I have overwritten it after I fixed the issue. Didn't want to accidentily use it again, because it let to so much frustration.
However, I did dig a bit deeper into the code than the stuff I posted here. The issue is this:
if hour == 8 and release13 == 1 and a13_5 == 1 and emily_bath_present == 0 and a13_10 == 0:
scene first_floor
$ emily_bath_present = 1
t "%(ey)s is in the bath - what should I do?"
menu:
"Open door":
...
pictures
...
$ advance_minutes (15)
if a13_9 == 0:
$ events += 1
$ a13_9 = 1
jump main
This is the event that sets a13_9 to 1. There is no reference to a13_58, so if you run into this one before you try to go to the bathroom at 23:00, then you're buggered. Because the condition for that event, which will set a13_58 to 1 is this:
if hour == 23 and release13 == 1 and a13_5 == 1 and a13_9 == 0:
So if you did whatever triggered a13_5, and go to the bathroom in the morning first, there is no way you can trigger the event in the night.
I'm not complaining, mind you. You clearly state that this is still a beta. But that looks like one of those beta oversights to me.
- Jun 16, 2019
- 293
- 187
It seems that many players have the same issue, so it's not a user problem but a game problem.
What you should have in the game is probably a checklist of events, so any player can understand what is missing.
Add the checklist and have as hints, instead, what must be done for each specific event to be deployed.
I don't know what it is about I tried a lot of times of passages 57/72 from v 11 following behind her at 00.00 after photographs and nothing works what put kensodoi is out of order I don't think so it will be possible to pass it
for me the episode not triggering is #52, doesnt looklike it tracks when you follow J to her room after photoshot with swimsuit at pool
exactly I have written 57 / 72. From v11 and I don't know how I am supposed to go farther.
- Mar 7, 2020
- 129
- 123
- Aug 27, 2018
- 1,209
- 2,968
- Aug 27, 2018
- 1,209
- 2,968
It’s tough to be me
Some players find it too difficult - some players find it too easy.In release 13 I expand the time span for modt of the events - simply to make it easier to play.
The same for 14.
does anyone has a save for the end of v12, i've had all the events exept 70/71 and i cant find it.
- Jun 8, 2018
- 106
- 572
- Aug 27, 2018
- 1,209
- 2,968
Patreon's get a WT so they always can find a way through. I'll guide you here, but can't do it if any mod have been enabled in the game.
- Jan 25, 2018
- 1,133
- 1,904
I don't understand why people bitch. They get free game they can enjoy. They should all be grateful to Bob for giving everyone the game for free. If they have problems they go to the patrons and if you don't like the game they don't play. What I noticed is that only the people who get it for free are not satisfied. All the patrons but enthusiastic. With Event 58 is no mistake. Personally, I would have had all events triggered only in a certain order (not only Event 58). Personally I love this and for me it means additional fun, because it is a bit more difficult to unlock everything and you can enjoy the game a bit longer. Every dead end means extra fun.
Last edited:
- Aug 27, 2018
- 1,209
- 2,968
Hi - if there are dead ends please let me know - that's not my intentions
- Mar 18, 2020
- 197
- 282
v13 i enjoyed a lot. My favorite part is when, once shy girls help corrupt new girls. The Story is interesting as well, in the past we had this huge decision with the Beard to sacrifice something to gain more from the girls back, maybe we can repeat that in some way? maybe the MC has to learn some dance moves or beat boxing? i mean the contrast to his age would be kinda hilarious. Oh and ya would the coming episodes be even more easy, that would be a shame, cuz. to think a bit and puzzle about the next step is a quality in its own. Anyways great work!
- Jan 25, 2018
- 1,133
- 1,904
There is with event a13_58 because there is the condition:
and a13_9 == 0:
Therefore if you trigger a13_9 first you cannot trigger a13_58 afterwards.
To fix it you had to write to the preconditions of event a13_9: and a13_58 == 1
I thought you did it on purpose, so I didn't report it.