First of all i wanted to thank you again for working so hard on this personality and improving it more and more
PtheV wrote: ↑Sun Sep 10, 2017 10:46 am
In v1.05 this should be a lot easier. As long as you have the "owns a chastity device" box checked in settings, it will come up at some point. If you want to be sure and/or don't want to wait, you can ask her "put me in chastity" and get a response.
I have the same problem that she never puts me in chastity even if i have it set to "sometimes".
Since i was starting to wonder wheter it was just a case or not, i gave a look at those custom/callreturn/pvCr_ChastityDecision scripts and i found a bug...and that's why she was never even checking to see if putting me in chastity or not (as i supposed).
On lines 118 forward, after setting the deal for her to be the keyholder there is:
Speaking of which... @RapidCodeOn
(pvChastitySet)
@NullResponse @CheckDate(pvChastityMaxReached,OUT)
@Variable[pvChastityLevel]=[1] @NullResponse @Goto(level 1)
@Variable[pvChastityLevel]=[2] @NullResponse @Goto(level 2)
..
...
The problem here is that the pvChastityMaxReached has never been set yet, so the checkdate will make it always skip to OUT without checking....you need to put a @SetDate(pvChastityMaxReached,XX) somewhere in the talk about her being the keyholder, so when it reaches that part for the first time it will go through and actually do her checks to see if putting in chastity or not.
There is also another bug in these scripts:
-lines91-92
Do you want to change your mind on any of this?
[yes] No problem @Goto(reset chastity)
But there is no (reset chastity) subpart in the script....it is called (reset)...you have to change one of the two :D
Finally the files in the custom/pvEndhastityIn folder, which are the ones in which, supposedly she tell you to lock yourself, miss the @ChastityOn (and she doesn't ever really mention locking you up either)