- May 16, 2017
- 714
- 3,753
I really like the game, Lindsay is gorgeous. But I think it really needs a walkthrough
- Thread starter UncleVT
- Start date
- Nov 30, 2018
- 11,925
- 53,081
All I hear is some crackling noise but I don't think it's any sort of issue just the sound effect that is used for the dream.
- Jan 10, 2018
- 2,337
- 3,106
That's the surrealistic sound effect that lets you know it's a dream.
- Jan 10, 2018
- 2,337
- 3,106
I can't say I like the way the game ends without a warning to save. That needs fixing.
This update is a trivial one to finish the last update. Probably better to skip this and wait for the next substantial update. It isn't worth the trouble to download.
This update is a trivial one to finish the last update. Probably better to skip this and wait for the next substantial update. It isn't worth the trouble to download.
- Oct 6, 2017
- 696
- 1,609
choices, choices, choices...What happened to bj scene?
You don't have permission to view the spoiler content.
Log in or register now.
is there a walkthrough for this game, because i got the bj scene first time i played this game now i cant seem to get it.
Also i dont get the scene where you first meet and serve the author, but bit later get the option to get the first chapter?
This game is great, much better than the rating might suggest, but is the latest update really just the extra 15 seconds of content?
- Dec 27, 2017
- 5,697
- 19,657
There is a definite coding error during Lindsay's first work day. She is supposed to wait on 3 tables. But because of the error, she goes directly from starting work to Mister Fletcher telling her to take a break.
Here's the offending code:
label lbl04tables:
The problem is that there is a value in the table variables when they are tested. It doesn't make any difference that the value is "False". The variables will never be evaluated properly, and we never even see the options to go to the tables.
A simple fix is to change the tests to 'if v04table1 == "False"' and so on for each of the tests. I believe changing the original definitions to '$ v04table1 = ""', etc. would also work. But I haven't tested that. Someone who actually knows how to code this stuff could probably answer that.
Here's the offending code:
label lbl04tables:
$ v04table1 = "False"
$ v04table2 = "False"
$ v04table3 = "False"
menu tables04:
"table 1" if not v04table1:
$ v04table1 = "True"
jump lbl04table1
"table 2" if not v04table2:
$ v04table2 = "True"
if metdougplane == "False":
jump lbl04table2mdf
else:
jump lbl04table2mdt
"table 3" if not v04table3:
$ v04table3 = "True"
jump lbl04table3
if v04table1 and v04table2 and v04table3:
jump lbl04bar1
The problem is that there is a value in the table variables when they are tested. It doesn't make any difference that the value is "False". The variables will never be evaluated properly, and we never even see the options to go to the tables.
A simple fix is to change the tests to 'if v04table1 == "False"' and so on for each of the tests. I believe changing the original definitions to '$ v04table1 = ""', etc. would also work. But I haven't tested that. Someone who actually knows how to code this stuff could probably answer that.
