Okay, that makes more sense. I didn't remember it being that buggy before. Lemme explain...
Back in May this year, I was in a near fatal motorcycle accident (100% the other vehicle's fault too) that wrecked my bike, and put my in the hospital for a month with both of my wrists so mangled that they needed emergency surgery and had to be plated to my forearms to recover; in addition to multiple broken ribs, a few fractured vertebra, and a fractured ankle. I was in real bad shape, but one of the things that helped keep me sane and the boredom at bay during my recovery was my laptop (on of those ASUS ROG thin n' lights). I watched a lot of streaming content (everyone was letting me piggyback on their accounts), and played a lot of VN's (both erotic and otherwise), cause it's the kinda game that's easy-ish to play when you can't really hold a mouse or controller.
So I had already played through the game before, but when I saw it pop back up, I added it to my backlog since I've returned home (still recovering and in physical therapy, but I can at least bathe/feed/clothe myself) and I now have access to my desktop again. So I've been replaying games that I really enjoyed (Then & Now), new releases of my favorites (Pale Carnations), and checking in on others that I remembered fondly (like Hero Party Must Fall). Fresh platform (desktop rather than laptop), so no saves; but not a problem since I wanted to re-experience the game anyways. So that's probably why I downloaded the v0.4 since I was a returning player. Guess I forgot about it, and it didn't click earlier that it was an unstable alpha.
Welp, now I'm downloading the earlier version, and hoping that my save doesn't get borked in the process...