- Nov 20, 2018
- 12,038
- 17,855
I do hope they return to this game as their current project is an ongoing clusterfuck, hasn't functioned correctly from release.
Cernunnos.
Isn't that how all of their games are? I remember their other game people were always making patches to fix errors after each update.
Technically, all of his games seem solid overall. I don't think I've ever seen many coding issues with Sister, Sister, Sister, this game, or Where Bad Girls Go. There are, however, design decisions sometimes that aren't great. In S³, there's a point at the aunt's house where you have to navigate the home. Basic navigation isn't bad there, but when you are trying to find a specific interaction with a particular character, it's not the greatest. Go down, go to the top-left; go down, go up; go down, go down; etc. Unless you use a walkthrough or look at the game's code, it's pretty much guesswork.Nahh.
SSS was already pretty good (relatively speaking). If anything, it got patched by so many of us because it was so popular back then. Its main flaw was spelling and typos (and what game doesn't have those). There were perhaps only three actual technical bugs (the truth or dare crash bug, not setting the "saw Lauren" variable in chapter 11 and the game jumping back into the middle of gameplay when you reached the ending). Everything else was polishing. There were some questionable design choices, but again, what game doesn't have those? The original game would have survived perfectly well on its own merits had none of us patched it. If anything, you could say we patched it because it had already reached a certain popularity threshold.
I think the other reason it got patched so much was that the rollback feature was disabled by default. Everyone felt the need to "fix" that one.
He did get a lot of poor feedback when he started Cuntswell, after deciding to write it in Visual Novel Maker rather than RenPy. But he'd already swapped back to RenPy by chapter 3 or 4. So yeah.
As far as I know, there's been no big problems with his current project (Where Bad Girls Go).
I guess what I'm saying is that the patches were a reflection that he was already doing well, not doing badly.
In WBGG, there's both a bug and poor design that may prevent a user from progressing on their own. Each girl in the game has her own story. After you have progressed through every story, you're allowed to move on to the Chapter Finale; you're not allowed to continue unless you've completed each girl's story. One of the stories is for June, but her sprite is located behind the sprite of Mary Agnes (the only character not having a story). You have to carefully hover near June's fingers (which you can barely even see) without activating Mary Agnes in order to click her and follow her story.
Additionally, there is one bigger bug I found in WBGG where the progress for one girl, Cheri, is canceled if you play another girl after her. I don't know which girl specifically, but if you play Cheri's story and then play this other girl (whoever she is), the persistent status of Cheri's story completion will be set to "false", so the game thinks you've not done Cheri's story. It was frustrating me, because I couldn't figure out why I wasn't allowed to run the game's Chapter 1 Finale. Text on the screen told me I had to complete every girl's story, but by this point I had. I had already found June's sprite and finished her story, and I'd already run the stories for all the other girls, including Cheri.
Finally, I opened the developer console and checked the values of persistent variables. When Cheri's was shown to be "false" (but all the others were "true"), I knew there was a problem, because I knew for a fact (have save games to prove) that I'd already run through her story before. I'm guessing, though, that others may not ever follow the order in which I played stories, so no one else found the same issue. Still, undoing progress in a game is a pretty serious bug, even if it's really easy to fix.