You're very, very, very close. Close enough to have 'accidentally' stumbled on it the day you referenced, where her stomach and muscles both hurt. Spoiler for the difference after the break.
You're hitting two out of three criteria for the Curvy / Fit And Fat / Middle Of The Road route - sugar/carb heavy meals and working out - but missing the third element - sufficient protein. Add some eggs / hamburgers / chicken to your diet and you'll be good to go.
JakYea
Creator of
Recent community posts
Oh, and it may not have come through, but the amount you earn doing work is proportional to your current energy levels. So if you're a couch potato in the moment when you phone in some work, you make essentially nothing, but if you are active enough to have a higher energy level (which reduces food-to-fat efficiency and slows down weight gain) you'll pull in a lot more money. Trying to play without ever raising your energy above the bottommost baseline is essentially impossible.
There is definitely an overly-narrow sweet spot in regards to income. It was one of the things I was adjusting before my hard drive bit the dust and I abandoned updating the project.
General consensus from the other people who played it through to the end seems to be : earn a lot early on, then batch work periods just after level transitions when the funds start looking meager.
Hey, thanks! That means a lot to me, both the advice regarding which images could do with a tweaking and the general attaboy. (And the cold hard cash, of course!)
You'll be unlikely to see sneak peeks of future stuff - I've found that showing off what I'm making kills the motivation to actually finish. Maybe someday this year or next another essentially-done game might just show up on my account.
Okay. I think I know what it is. (Again.) You're in the code too, right? In bedtime.rpy lines 127 through 139, you'll see I screwed up and put some of the
$ weight = [##]
entries as
$ weight == [##]
The double equals is used to check equality between two values, not to assign a value to a variable. So wherever the "weight == [##]" entries are it's not executing that code properly... and because it's a python command in ren'py (thus the $ prefix) it's not getting checked by the autochecker. AND because there's a few ways the value could hit 31, the First-Week-As-Curvy entry, I missed it in playtesting and some folks have gone down that path without hitting the roadblock.
I'm really and honestly behind on some RL stuff that needs to get done right away, but (fingers crossed) this might be the fix. I'll move to push 0.9.2 as quick as I can. If you're really jonesing to play that arc, you should be able to by going into the bedtime files and doing a find replace that changes every
$ weight==
into
$ weight=
If you blow through the repeated introduction, is Trisha's next look in the mirror the same as the first one (blue button down short sleeve and red shorts) or is it different (red top, white sweatpants, "Trisha, you're getting curvy" self-talk)?
After the meet up with Jasmine, does it say "Error - Didn't get a S D F pathway assignment"?
That's the worse case. I have no idea how that could happen.
It must be calling a specific function (the meeting script) while the weight variable is at the default level, but there's a IF/ELSE just before that function gets called after the third day of each 'week'/cycle that forces the variable to be on one of the three branching paths.
I'm out of time for today to work on it, but if I can't figure out how the function call is being made without the immediately preceding variable change taking place I guess I can add a binary flag that prevents it from showing that intro version of the meeting more than once. So far I'm only getting complaints about the 'balanced route', if it only happens there then I can have the binary exception trigger an immediate jump to being on the first Curvy meeting, but I'd really rather figure out how this is happening in the first place instead of spaghetti-coding a mystery fix into it.
Thanks again for helping me with the context around your reboots.
Alright. That's helpful, thank you.
And the meeting is the same? If it were working as designed you'd still see the same setting (the restaurant exterior) but the conversation with Jasmine would play out differently once you were inside and seated. Before the restaurant fades in, does it read "We join the story in progress" or "And so, time flew by" or "Months pass"?
Ah, crud. Thanks for letting me know.
I and another guy drove the wheels off this and didn't manage to get the error. I don't doubt it's happening to you, but I can't find it while playtesting. Additional information would be massively helpful in running it to ground.
What's the last two things it says to you before kicking you back? And does it kick you to the first meeting with Jasmine, or the game menu?