Probably, since the story reset doesn't actually roll anything else back, right? I must have missed the gym membership time limit.
Yeah, that reset is very minor, and it's unlikely to reset the gym membership (unless there's some very bad memory overflow issue in the game, in which case I'd expect a lot more problems). The reset at the end of the Blackmail thread (with Angelica and Laura) that occurs early in the game is more involved, but even for that one I can't see who the gym membership would be affected.
Something I meant to suggest earlier: have the hint Eye icon change color or something to signify if it's active or not. I've been stuck a few times where I wasn't sure if it was on or off, and there were no active events at the time for me to check against.
Good idea. There are five states that the system can be in, and here's what I'm thinking of doing (bearing in mind that it's fairly easy to change the color of the eye, but harder to change its shape):
- Highlighting is disabled - the eye will be invisible;
- Highlighting is permanently enabled and there are no active events - the eye will be orange (its current color);
- Highlighting is permanently enabled and there are some active events - the eye will be green;
- Temporary highlighting is enabled (active events are highlighted only if you hover over the eye) and there are no active events - the eye will be grey; and
- Temporary highlighting is enabled and there are some active events - the eye will be green.
If you have some other ideas about how the eye should be implemented, please let me know.
Edit: Testing the patch now, and two things: 1) Somehow, I jumped to ginaLounge3 without completing 1 and 2 (but having completed 0 prior to patching). In the Threads screen, 2 is showing as available tomorrow, but 1 and 4 are greyed out.
Pseudo-edit: just occurred to me: it probably actually triggered 1, but the wrong node on the Threads page was colored in.
It's probably working exactly as it's supposed to. In the QSP game, some threads (such as ginaLounge) contain events that can be carried out in random order (these are mostly the spectre1viper threads), and I spent way too much time trying to figure out how to get that working in my thread systems. I eventually got it working, and was then able to play those parts of the game (I never finished playing the QSP version, which is why I had to write the Ren'Py version). And then I decided it really wasn't necessary that these events came in a random order, but had spent so much time getting random events working that I couldn't bring myself to throw away all that work.
Anyway, with the random threads the events will be marked in green in the order in which you see them. If you replay the game later you'll see the events in a different order. But, once you've seen all the events, the thread will be marked as complete, regardless of the order.
Edit: There is a bug in the thread board - the event that shows up in white will not necessarily be the one that will trigger tomorrow. Something for me to fix in the next patch.
Also, in the last section of the event, the amount of text exceeded the textbox size, and I couldn't read it (Same thing on ginaPool 0).
You'll find this happening more and more as you get farther into the game. If you hover over the text you can use your mouse wheel to scroll through the text. This isn't ideal, but I'm not sure what the best way to fix this is. One way is to break the text into many smaller paragraphs, and the player can click through them all while the video continues to play. But some players aren't that interested in the text and will complain that there's too much clicking. Another way is to add scroll bars, but I tried this and couldn't get this working nicely (the scroll bars showed up even if they weren't needed, which is most of the time). A lot of the text also needs to be reformatted as it contains lots of random line breaks, resulting from the automatic extraction of the text from the QSP game. This is definitely something I need to think about how to resolve, and I'm open to suggestions about what you think would be best, and then I'll try to implement it.
