Masturbatrix - Tease-AI Awakening - Last updated 09-01-2026

[Rar1197]

<Version 1.40A draft feedback>

A few general issues with the new task handling logic...

Currently the 'task assigned' flags (TaskAssigned_01 etc) don't appear to be deleted when the tasks come to an end. So I think it will ask about the task every time after the 3 days have elapsed.

(ResetTasks) in Custom\Task\Task_Assign.txt doesn't deleted TaskAssigned_27 to TaskAssigned_30. It doesn't currently matter since the code is never called , but you should probably either update it or remove it to avoid errors in the future.

For tidiness you may want to remove all the instances of @SetFlag(TaskActive_01) etc from the update logic for the old versions in Custom\Start_And_Misc\Update.txt and from Custom\Start_And_Misc\Install.txt. This doesn't exactly do any harm , but it is creating a bunch of misleading flags that are no longer used.

[Rar1197]

<Version 1.40A draft feedback>

Suggestion for event selection logic in Insert\Session\Insert_SelectActivity.txt and Insert\Session\Insert_SelectGame.txt

Currently you check the Played_X flags after having randomly chosen an event , and select the next event in the chain if needed.

This has a couple of issues.
1) It allows an event that has been assigned zero weighting to be selected
2) It allows events to be selected that should in theory be disabled when the BT_Session flag is set.

Possibly the better solution would be to check the Played_X flags in the starting bit where you are doing the random selection.

So

Code: Select all

@NullResponse @ChangeVar[Roll]=[Roll]+[#Var[Chance_SirenHero]]

becomes

Code: Select all

@NotFlag(Played_SirenHero) @NullResponse @ChangeVar[Roll]=[Roll]+[#Var[Chance_SirenHero]]

And

Code: Select all

@NullResponse @ChangeVar[Test]=[Test]+[#Var[Chance_SirenHero]]
@Variable[Test]>=[Temp] @NullResponse @Goto(Event_SirenHero)

becomes

Code: Select all

@NotFlag(Played_SirenHero) @NullResponse @ChangeVar[Test]=[Test]+[#Var[Chance_SirenHero]]
@NotFlag(Played_SirenHero) @Variable[Test]>=[Temp] @NullResponse @Goto(Event_SirenHero)

There is a minor edge case where my suggestion will not be fully correct - namely if the flag happens to expire part way through calculating the random selection. However I think the worst that happens is that you fall through to a classic session in this case , so it probably isn't an issue.

[Rar1197]

<Version 1.40A draft feedback>

In Custom\Start_And_Misc\Reward.txt the entry for (2Punishment) is wrong.

This

Code: Select all

You get @RT(2,two) punishment points! @ShowImage[GNMImages\Rewards\Punishment.png] @ChangeVar[Punishment]=[Punishment]+[1] @Timeout(10,ContinueY)

should be

Code: Select all

You get @RT(2,two) punishment points! @ShowImage[GNMImages\Rewards\Punishment.png] @ChangeVar[Punishment]=[Punishment]+[2] @Timeout(10,ContinueY)

[Rar1197]

<Version 1.40A draft feedback>

The update logic for version 140 needs to initialise the various 'Siren' variables that are currently initialised during installation :

Code: Select all

@NullResponse @SetVar[SirensSession]=[0]
@NullResponse @SetVar[Siren_Health_Extra]=[0]
@NullResponse @SetVar[SirensSession_Lost]=[0]
@NullResponse @SetVar[SirensSession_Won]=[0]
@NullResponse @SetVar[SirensSessionLarge_Won]=[0]
@NullResponse @SetVar[SirensSessionExtreme_Won]=[0]
@NullResponse @SetVar[DommeCheatSiren]=[0]
@NullResponse @SetVar[Sirens_Health_Bonus]=[0]   
@NullResponse @SetVar[SirenDiff]=[1]
@NullResponse @SetFlag(SirensAndLaddersEnabled)

[Rar1197]

Hmm , on further consideration it would have made more sense to send all these as private messages instead.

I'll do that for any remaining pre-release feedback instead to save you all the spam!

[genome231]

<Version 1.40A draft feedback>

A few issues with Custom\Start_And_Misc\Update.txt :

The section for (Version140) is setting the current version to 136 instead of 140.

At the end of (Version140) it goes to the End instead of Update for potentially updating to the next version. Though in practice this prevents the previous error from causing an infinite loop.

Change_SirenHero needs to be initialised as part of the update for version 140 , otherwise it won't get set for people that currently have version 130 or greater.

While we are testing. I have left the Update script in sort of an "open" state, so I can do changes
When 1.4 releases I will close it again.

I am unsure what you mean with this:
"Change_SirenHero needs to be initialised as part of the update for version 140 , otherwise it won't get set for people that currently have version 130 or greater."


Cheers
Genome

[Rar1197]

I am unsure what you mean with this:
"Change_SirenHero needs to be initialised as part of the update for version 140 , otherwise it won't get set for people that currently have version 130 or greater."

Cheers
Genome

Sorry , a bit of a typo , I meant 'Chance_SirenHero'

Currently there are only two places where Chance_SirenHero is set.
1) In Update.txt as part of the update for Version130
2) In Settings.txt when customising the probabilities.

This means that if someone applies this update and they are already at Version 130 then nothing will set that variable , unless they happen to tweak things in the settings.

This will mess up the event selection since it will be using a non-existent variable. It is possible it will just have the same effect as it being set to 0 , I'm not sure. Regardless it would be best if it got intialised to a sensible value.

[poiuz]

Hi, recently I came back to the program. I updated files to new version 1.36F, cleared saved data, started program and performed setup. In the past the domme ordered me to get locked up in the begining and after each session. Yet, now I am not able to make domme to order to get locked up. In the settings chastity training is enabled, as well as session (=on), capability and expectations are set to 24/7. I do not know what the "between sessions" means, therefore I left it off (maybe can someone explain to me also this, please?).

I tried various settings, multiple times but nothing seems to work. I do not remember exact setting when it worked last time so I tried to work it out, yet with no success.

Is it a bug or am I missing something?

Thank you for any advice!

SOLUTION: After hours of tries I figured that domme does not order lock up when finishing session but only when exiting by exit command from main menu..

Between session option in chastity settings remains still a secret for me

[Rar1197]

I think 'chastity between sessions' means that there is a chance of the Domme deciding to set an extended chastity period when exiting. If this happens then it won't be possible to start a new session until that timer is up.

[genome231]

Hi,

Just a "Still here" post.
Next version still in the works. However slow progress from my side.
Currently a lot going on taking time away from scripting.

Cheers
Genome

[Mammoothman]

Hi,

first of all, thanks for this amazing personality!

I do, however, have a problem when playing 'Supreme'. I don't see my cards. It's always just pictures of the Domme. She tells me the order of my cards, but I don't see them, so I do basically have to play blind (which ofc always ends in Curfew ). I dont know if it is supposed to be in a pop out window or not, but i just cant see my cards. I do, however, see the one she plays (that one gets shown).
Never had Black Jack, dont know if it will be the same there.
Is it supposed to pause showing new Domme pictures? Is there a known fix?

I downloaded it only a few days ago, so should be newest version. The TeaseAI Awakening version is 0.2.74
I used the setup from your PDF for Masturbatrix

[Rar1197]

Hi,

first of all, thanks for this amazing personality!

I do, however, have a problem when playing 'Supreme'. I don't see my cards. It's always just pictures of the Domme. She tells me the order of my cards, but I don't see them, so I do basically have to play blind (which ofc always ends in Curfew ). I dont know if it is supposed to be in a pop out window or not, but i just cant see my cards. I do, however, see the one she plays (that one gets shown).
Never had Black Jack, dont know if it will be the same there.
Is it supposed to pause showing new Domme pictures? Is there a known fix?

I downloaded it only a few days ago, so should be newest version. The TeaseAI Awakening version is 0.2.74
I used the setup from your PDF for Masturbatrix

If that version number is correct , then you are using an ancient version of TeaseAI Awakening , which will almost certainly be the issue.
I think the cards are displayed using the @ImageBar commands which were introduced in version 0.2.85.

The current version of TeaseAI Awakening is 0.3.90, so I would recommend trying with that version.

[genome231]

Hi

Hi,

first of all, thanks for this amazing personality!

I do, however, have a problem when playing 'Supreme'. I don't see my cards. It's always just pictures of the Domme. She tells me the order of my cards, but I don't see them, so I do basically have to play blind (which ofc always ends in Curfew ). I dont know if it is supposed to be in a pop out window or not, but i just cant see my cards. I do, however, see the one she plays (that one gets shown).
Never had Black Jack, dont know if it will be the same there.
Is it supposed to pause showing new Domme pictures? Is there a known fix?

I downloaded it only a few days ago, so should be newest version. The TeaseAI Awakening version is 0.2.74
I used the setup from your PDF for Masturbatrix

I believe rar1197 has said all regarding the probable issue.
I will just say thanks for the kind words
As per usual feedback, ideas and constructive criticism is highly encouraged.

Still working on version 2.4 which is turning out to be a biggie.

Until then
Cheers
Genome

[Mammoothman]

thanks for the feedback/suggestions, i will try with a newer version of TeaseAI. Didnt realize mine is that old already

[genome231]

Hi all

Just a few words on what I am working on:

• Full implementation of EmlaLock (online keyholding for chastity).
• Full implementation of play with chastity on.
• Full implementation of automatic strokers, vibrators and audio controlled E-Stim.
• Lots of other smaller stuff.

Especially the implementation of automatic strokers, vibrators and E-Stim is a biggie.
Basically all scripts has to be able to handle the many possible variations.
You can imagine using all toys in various different combinations.

Cheers
Genome