itch.io

there's a joke in here somewhere about bloating scope and expansion

I want to step back and say this is an incredible achievement. It's both a good, fun, tough-but-fair game as well as a great piece of transformation/expansion content. Extremely well done, and out of nowhere!

Also, I have to say how refreshing it is that it's a complete, finished product; so many expansion games start off strong and then get utterly lost in scope creep, the developers disappearing into the thickets of the back half of their game's mechanics/plot/art and never releasing an ending.

Anyway, for anyone reading this: it definitely deserves your three bucks, and I'd say it's a bargain for the price.

(Oh, if there's one thing I'd like: a proper release for Mac. I can get it working via Heroic, but it's a bit of a pain. This is a Godot project, should be down to checking a box at build time, although I understand that getting proper code signing set up for Mac deployments means you have to pay the Apple tax...)

Very fun, and very much appreciate that in a game with lots of rules cross-checking there's no timer for each adventurer, so it feels very fair when I mess one up that it was because I wasn't fully applying the rules, not that I was rushed.

An update here @nunu: the latest version works just fine! So... not sure what changed. I wonder if I had a corrupted save or something and booting the game via the renpy SDK fixed it or something.

Interesting. It launches when I download and use that specific version of the launcher, too...
I'll see if I can pull some older versions of CabinByTheLake.app and see if there's a particular one that starts failing.

If I load the `game` directory into the renpy launcher and just run it from there (that is, discarding the runtime that the game ships with), it boots up just fine. So there must be some error either with the bundled renpy engine or its python runtime. What version of renpy are you building with?

Is anyone else getting an issue with the mac builds crashing on startup on an ARM mac? Something deep in the bundled python, it seems:

Crashed Thread:        0  Dispatch queue: com.apple.main-thread
Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Codes:       0x0000000000000001, 0x0000000000000000
Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [12113]

Might be a rosetta inconsistency, since the game is compiled for Intel CPUs, but it's weird that it's only started with the last few versions...

The generated JSON save file is just a sequence of _every_ state the game has been in, it looks like... that's going to start getting really big for some people's playthroughs.

The particles appear to be busted on the web player: the game loads, but the first time two orbs hit each other to merge, the game crashes with "WebGL context lost".

I'll poke around in a decompiled version of the twine and see if anything stands out to me, too.

it's the scene where she's leaving the store right after you're done making changes.

I can only seem to get the "breast pump" ending if I have everything set to maximum size and _then_ also pick "make more of the world amazonian" as well.

It looks like it incorrectly tags the shop Vanessa in is as "fetish clothing" even if you set it to "breast pumps".

I just fixed it in code by changing the unlock check, but another approach would be to check-and-set _every_ time someone chats with the other women.

There appears to be a logic issue where if you download v1.0 and load in a fully-unlocked save from the previous version, there's no way to trigger the new girl (it just says "Talk to the Others", but even after looping through all their dialogues, nothing happens).

Yep, looking at the code, I see the problem: there's no path for me to set `outfittier` to 2, since I've already given everyone their clothes.

Happy to provide testing as well. Perhaps related to relative paths for asset-loading?

Oh, one other thing: the girls don't load in the chairs in the screen, either. I wonder if there's some sort of bug in that code that just prevents forward progress, vs an input bug.

100% standard US keyboard. Spacebar did seem to get me past the Start selector, but no other inputs seem to work.

Yeah, whatever you're using to capture input doesn't seem to work on macs. Same experience here.