I'll update this post as soon I have some results.
Test #1
- Spoiler: show
- Settings
- Working days: from Monday to Friday
- Leave home to go to work at 8
- Come back home at 12
- Always wake up at 7
- Always go to sleep at 22
- Same number of sessions for working/not working days
- Number of sessions per day: min: 2 max: 4
- No sessions during sleep
- Time between sessions: min: 1 minute max: 2 minutes
- Length of the session: min: 5 minutes max: 10 minutes
The script works!
At least with these settings, so it may just be a coincidence but I don't think so.
I did the set-up and then finished the session. After a couple of minutes she woke up and she started another session. I managed to do all the 4 sessions she planned for today.
These are the problems I encountered:- If you have set a limit to how many orgasm you can get, like I did, and you've already had all your orgasm and your Domme decides to let you cum, she will run the interrupt Was going to let you cum(in Interrupt\Out of Orgasms).
After that the session will end and she will not wake up unless you say hi. The same if you use your safeword and then decide to end the session; - I forgot to add a @CheckStrokingState at the beginning of the set-up script;
- Minor problems with the reset procedure;
- This is the biggest problem I had. As holaba_be described here everytime she woke up she punished me for missing 0 sessions and she has never played the alarm sound.
Problems 1, 2 and 3 are easy to fix. About the last one I don't have a solution at the moment.
I will need to do more tests, maybe tonight.
- Spoiler: show
- Settings
- Working days: from Monday to Friday
- Leave home to go to work at 8
- Come back home at 12
- Always wake up at 7
- Always go to sleep at 22
- Same number of sessions for working/not working days
- Number of sessions per day: min: 1 max: 2
- No sessions during sleep
- Time between sessions: min: 1 minute max: 2 minutes
- Length of the session: min: 5 minutes max: 10 minutes
I found a problem. After the initial session where I did the set-up script she went offline. It was 16:11, but she never woke up. So after 15 minutes I decided to put some flags to understand what was happening. I discovered that the script was playing a loop: (Start)>(Find day of the week)>(Friday)>(Friday_Sub is at home)>(Friday_Sub is sleeping)>(Start); but I'm not sleeping!
So I checked line (Friday_Sub is at home) where she decides whether I'm awake or not and I found this errorAs you can see in the @If command, after the "Or" it's missing the command #DateDifference and that's what is causing the loop.Code: Select all
@NullResponse @Flag(24-7_work_on_friday) @NotFlag(24-7_work_on_saturday) @If[#DateDifference(24-7_wake_up_working_day,minutes)]<=[0]Or[24-7_go_to_sleep_not_working_day,minutes]>=[0]Then(Friday_Sub is sleeping)
This error was present also in version 1.02 but I believe also in 1.01 and 1.00. This error is present in all the (XXX_Sub is at home) lines.
Conclusions
I fixed the code and I'm now checking if there are similar errors. Tonight I'll run other tests to see if everything is OK.
The only problem I still have to fix is #4 from Test #1
Small update on this script.
I was doing other tests and I was pretty confident that was everything OK but I found another bug.
This time Tease AI crashed...
I'm done for today. I'll check the script tomorrow...




