Not that one, but when the MC is on the beach and asked to choose between thicc and thin, I chose thin but game persists with thicc.
persistent.pickedPaleBooty0107 == True is assigned FALSE value
Oof! That's actually a bug, I'd say. I'm not sure how even I (who analyzes the code to find the best choices for the WT mod) managed to miss that one.
In most code languages (including Python and Ren'Py), one equals sign means assignment (setting the value), two equals signs mean comparison. In this part, the dev isn't setting the value to True (if you choose Anita) or False (if you choose Misaira), the dev is rather comparing if it's set to True or False. And without an "if" statement (or anything that handles the result of that comparison) around it, nothing is done to the variable.
I mean, it's not the only bad coding choice made by the dev, though. Using the persistent storage is one major flaw, which makes it hard to keep separate save files for different paths (only the choice you last picked, regardless of save file, is the one that persists). Persistent storage is meant for variables used regardless of save files, such as unlocking a scene in a gallery, preferences, even making sure warnings or choices are only shown on the very first playthrough or the very first time you encounter that choice.
I've already released my mod for 0.1.10 when I saw your post, and although I could go back in and fix this flaw from within my mod, I remember that it would only result in some minor dialogue changes in the contents released in 0.1.07 and 0.1.08 (nothing beyond those two releases yet).
So, for now, it's
technically a minor bug, given the minor effects this choice gives, but the dev
should fix this in code for the next release.
