I updated to the newest version of the game, and I even went so far as to re-enter each action in my "AddedActions" folder. I wanted to be sure that there was no carryover problems. I had been unhappy with the pace of clothing removal at times, so one situation was reserved for solving that problem. All actions other than actions that removed clothing were coded so that they would not be used unless all clothing had already been removed. This way, if we got to, say, level 6 or 7, and we were still wearing clothing, we could choose this situation and the game would be forced to choose an action that removed any existing clothing.
Sometimes it seemed to work, but other times, we just got an action that was not supposed to be for that situation.
So, when I switched to the newest version, I left all the remove clothing actions out of my "AddedActions" file. This way the game would only use the remove clothing actions that are already included in the "BasicActions" file. The result is that, in the last couple of games, Bliss has had trouble keeping track of what clothing we are wearing. In the last game, it instructed me to remove an item of clothing that could not be removed prior to another item that I was still wearing. Also, it instructed my partner to remove her robe, which she didn't put on for the game and had not checked as being one of the clothing items she was wearing.
Also, the last of my clothing was not removed until we had reached level 9.
I had hoped that the newer version would have these problems fixed, but I think that it is worse. Is there a work-around? Can I use the feature that lets the game know exactly which clothing items to remove?