Dude! great that you are back. Dont push to hard! Chill and release things when they are done and dont work to much.1885 wrote: Sorry again for how long it took to get this patch out. Any bugs that come up now can be fixed in a timelier manner than this patch took, most of the delay was due to me having to crash course on a lot of complicated code. If you have any bugs or comments or questions please let me know and I'll take care of it as soon as I can
Tease AI General Discussion
Moderator: 1885
- Vinc
- Explorer At Heart

- Posts: 213
- Joined: Sat Oct 29, 2011 10:21 pm
- Gender: Male
- Sexual Orientation: Straight
Re: Tease AI Open Beta - Updated to Patch 53
-
SensEx
- Explorer

- Posts: 43
- Joined: Fri Feb 26, 2016 2:08 pm
- Gender: Male
- Sexual Orientation: Straight
- I am a: Dom (Male)
- Dom/me(s): I only submit to my queen
- Sub/Slave(s): I no longer take applications
Re: Tease AI Open Beta - Updated to Patch 53
I definitely second that adviceVinc wrote: Dude! great that you are back. Dont push to hard! Chill and release things when they are done and dont work to much.
Keep your TODO's and set reminder but don't think"it must be done now or tomorrow"
work one by one, don't try to learn everything at the same time focus on ONE thing "you desire to add"
If you struggle too much just move to the next item on your list.
-
Mat
- Explorer At Heart

- Posts: 429
- Joined: Sun Feb 26, 2012 8:34 pm
- Gender: Male
- Sexual Orientation: Straight
- Location: UK
Re: Tease AI Open Beta - Updated to Patch 53
Sorry, It's been a while since I had enough time to post..
I've found a few bugs since I last posted..
I've had these two errors while a slideshow was playing:
ArgumentOutOfRangeException: Index was out of range.
With the latest patch, Patch 53.. When the slideshow is set to tease it shows numbered images in the order of:
image1
image10
image11
...
image2
image20
image21
etc. rather than 1, 2, 3..
The writing tasks, and the box the shows what to write, appears on top of the side chat, so then you need to resize the main image pane type in that box instead.
At the end of a tease, tasks "downloaded" don't show when side chat and "lazy sub av" is open.
On a side note, there are two lazy sub apps.. one as an app and the other appears over the domme avatar.
It's not really a bug but the metronome starts before the tts voice says "start stroking"
I'm not sure if it was meant to be like it is but only one edge hold range box goes down to seconds, the others stay at minutes
And a couple of suggestions:
On the Scripts tab, it either says all requirements met, or not. Could you get it to highlight which specific requirements aren't met? Sometimes it can be a pain to check them all if there is a lot of requirements.
Possibly add a button under the Misc tab to test for url images that 404 (images, not the site url). And/Or if it can't retrieve an image, suppress the error message and have it immediately try a different one or a local one. I'm not sure if that's the reason I'm getting the errors during a slideshow or not.
I know it's been mentioned before, but could you save the settings to a file in the program's directory rather than appdata? That way you don't have to keep track of which random file name is for which version of Tease AI. Also you'd be able copy the installation between machines and still have it work. I suppose you'd need to make your own settings class to handle saving/loading though, but it shouldn't be too hard.
Having had a quick look at the code, I couldn't find anywhere that you initialise the random number generator apart from:
Private Sub RefreshRandomizerToolStripMenuItem_Click
So it will probably keep repeating numbers. You should initialise it first using "Randomize()"
(https://msdn.microsoft.com/en-us/librar ... 90%29.aspx)
Sorry if I missed something and you already do..
Finally I'd like to say that I agree with Vinc and SensEx. There's nothing that I can really add but I'd definitely say, like Vinc said, don't work too much, your health is more important than releasing updates as quick as you can
I meant it more at the end of a slideshow rather than at a specific point in a script. Thanks for the tip thoughavatarbr wrote:Just a tip, you can use @NewDommeSlideshow at any point in the scripts to change that.Mat wrote:Just a quick suggestion/request..
Could you make it so that if the domme sideshow gets to the end it automatically chooses a new one?
Normally it's not a problem but sometimes it randomly selects a set with only a few images in.
Thanks1885 wrote:Done, added the option in Patch 52 as a Slideshow Option settingMat wrote:Could you make it so that if the domme sideshow gets to the end it automatically chooses a new one?
Normally it's not a problem but sometimes it randomly selects a set with only a few images in.
I've found a few bugs since I last posted..
I've had these two errors while a slideshow was playing:
ArgumentOutOfRangeException: Index was out of range.
- Spoiler: show
- Spoiler: show
With the latest patch, Patch 53.. When the slideshow is set to tease it shows numbered images in the order of:
image1
image10
image11
...
image2
image20
image21
etc. rather than 1, 2, 3..
The writing tasks, and the box the shows what to write, appears on top of the side chat, so then you need to resize the main image pane type in that box instead.
At the end of a tease, tasks "downloaded" don't show when side chat and "lazy sub av" is open.
On a side note, there are two lazy sub apps.. one as an app and the other appears over the domme avatar.
It's not really a bug but the metronome starts before the tts voice says "start stroking"
I'm not sure if it was meant to be like it is but only one edge hold range box goes down to seconds, the others stay at minutes
And a couple of suggestions:
On the Scripts tab, it either says all requirements met, or not. Could you get it to highlight which specific requirements aren't met? Sometimes it can be a pain to check them all if there is a lot of requirements.
Possibly add a button under the Misc tab to test for url images that 404 (images, not the site url). And/Or if it can't retrieve an image, suppress the error message and have it immediately try a different one or a local one. I'm not sure if that's the reason I'm getting the errors during a slideshow or not.
I know it's been mentioned before, but could you save the settings to a file in the program's directory rather than appdata? That way you don't have to keep track of which random file name is for which version of Tease AI. Also you'd be able copy the installation between machines and still have it work. I suppose you'd need to make your own settings class to handle saving/loading though, but it shouldn't be too hard.
Having had a quick look at the code, I couldn't find anywhere that you initialise the random number generator apart from:
Private Sub RefreshRandomizerToolStripMenuItem_Click
So it will probably keep repeating numbers. You should initialise it first using "Randomize()"
Code: Select all
' Initialize the random-number generator.
Randomize()
' Generate random value between 1 and 6.
Dim value As Integer = CInt(Int((6 * Rnd()) + 1))Sorry if I missed something and you already do..
Finally I'd like to say that I agree with Vinc and SensEx. There's nothing that I can really add but I'd definitely say, like Vinc said, don't work too much, your health is more important than releasing updates as quick as you can
Re: Tease AI Open Beta - Updated to Patch 53
Hi 1885!
Had an idea and thought it worth sharing! :D
It comes in regards to the domme tag creator!
Theres a huge difference in how "sexy" pictures are and how sexy is to each individual. I think it would a nice addition if you beside tagging could sort of rate the pictures from 1-10 or 1-5.
1 being lowest, 10 highest.
then add a tag like the others but like @TagRating(5) <-- this show a image with a rating of 5. This could be further expanded by having commands like @TagRatingMinimum(), @TagRatingMaximum() and @TagRatingBetween().
@TagRatingMinimum(4) <-- this would show an image with a rating of at least 4 (4 included)
@TagRatingMaximum(6) <-- this would show an image with a rating of no higher than 6 (6 included)
@TagRatingBetween(3, 6) <-- this would show an image with a rating between 3 and 6 (3 & 6 included)
Regards
Genome
Had an idea and thought it worth sharing! :D
It comes in regards to the domme tag creator!
Theres a huge difference in how "sexy" pictures are and how sexy is to each individual. I think it would a nice addition if you beside tagging could sort of rate the pictures from 1-10 or 1-5.
1 being lowest, 10 highest.
then add a tag like the others but like @TagRating(5) <-- this show a image with a rating of 5. This could be further expanded by having commands like @TagRatingMinimum(), @TagRatingMaximum() and @TagRatingBetween().
@TagRatingMinimum(4) <-- this would show an image with a rating of at least 4 (4 included)
@TagRatingMaximum(6) <-- this would show an image with a rating of no higher than 6 (6 included)
@TagRatingBetween(3, 6) <-- this would show an image with a rating between 3 and 6 (3 & 6 included)
Regards
Genome
Tribute to 1885 & those involved with Tease-AI.
Thank you for spending time on this awesome project!
Thank you for spending time on this awesome project!
- 1885
- Explorer At Heart

- Posts: 648
- Joined: Fri Jul 08, 2011 4:27 am
- Gender: Male
- Sexual Orientation: Straight
- I am a: Switch
Re: Tease AI Open Beta - Updated to Patch 53
Important Information!
We discovered an issue with the latest Patch 53 tonight, and want to get this out there as soon as possible so people can be aware of it.
There was a bug introduced in Patch 53 where if you didn't have Save Session Images checked in General Settings, any blog images would get saved to the root folder instead (as opposed to not getting downloaded at all, which was the intended function). So if you don't have this option checked, please check your root folder "C:\, E:\, etc" because it might be filling up with tumblr porn.
Patch 54 will be done within a couple of days, and this bug is fixed, but this is a critical bug and I wanted to make everyone aware of it as soon as possible. Until patch 54, if you have privacy concerns, either play with Session Image saving enabled or manually clean up your root folder after a session. Or wait for Patch 54, which should be out soon.
We discovered an issue with the latest Patch 53 tonight, and want to get this out there as soon as possible so people can be aware of it.
There was a bug introduced in Patch 53 where if you didn't have Save Session Images checked in General Settings, any blog images would get saved to the root folder instead (as opposed to not getting downloaded at all, which was the intended function). So if you don't have this option checked, please check your root folder "C:\, E:\, etc" because it might be filling up with tumblr porn.
Patch 54 will be done within a couple of days, and this bug is fixed, but this is a critical bug and I wanted to make everyone aware of it as soon as possible. Until patch 54, if you have privacy concerns, either play with Session Image saving enabled or manually clean up your root folder after a session. Or wait for Patch 54, which should be out soon.

-
Stefaf
- Explorer At Heart

- Posts: 107
- Joined: Sat Apr 02, 2016 7:43 am
- Gender: Male
- Sexual Orientation: Straight
- I am a: None of the above
- Location: Germany
Re: Tease AI Open Beta - URGENT INFO PLEASE READ
Hello everyone!
I must shamefully admit that I have caused that massive bug in Patch 53.
As 1885 mentioned: If you have deactivated the option "Save Blog Images From Session", the blog images were stored in your root directory!
This means therefore that if you installed Tease-AI on your hard disk C, the images were saved to C:\ ! If you started Tease-AI from "P:\blah\Tease-AI" the images have been stored in "P:\". I think you understand the principle.
I am really sorry, but we discovered the problem just now. At the moment the final preparations for patch 54 are running. Therefore, you should not have to wait too long.
We hope you didn't have problems, if you share the computer.
To work around the problem in the short term, you can activate the option "Save Blog Images From Session". Then the files are saved correctly in your Tease AI folder.
I must shamefully admit that I have caused that massive bug in Patch 53.
As 1885 mentioned: If you have deactivated the option "Save Blog Images From Session", the blog images were stored in your root directory!
This means therefore that if you installed Tease-AI on your hard disk C, the images were saved to C:\ ! If you started Tease-AI from "P:\blah\Tease-AI" the images have been stored in "P:\". I think you understand the principle.
I am really sorry, but we discovered the problem just now. At the moment the final preparations for patch 54 are running. Therefore, you should not have to wait too long.
We hope you didn't have problems, if you share the computer.
To work around the problem in the short term, you can activate the option "Save Blog Images From Session". Then the files are saved correctly in your Tease AI folder.
Re: Tease AI Open Beta - URGENT INFO PLEASE READ
Apology not accepted!Stefaf wrote:Hello everyone!
I must shamefully admit that I have caused that massive bug in Patch 53.
As 1885 mentioned: If you have deactivated the option "Save Blog Images From Session", the blog images were stored in your root directory!
This means therefore that if you installed Tease-AI on your hard disk C, the images were saved to C:\ ! If you started Tease-AI from "P:\blah\Tease-AI" the images have been stored in "P:\". I think you understand the principle.
I am really sorry, but we discovered the problem just now. At the moment the final preparations for patch 54 are running. Therefore, you should not have to wait too long.
We hope you didn't have problems, if you share the computer.
To work around the problem in the short term, you can activate the option "Save Blog Images From Session". Then the files are saved correctly in your Tease AI folder.
You're doing an awesome job and everyone is just thankful that you're even doing it in the first place!
Thanks for bringing the bug to attention
So instead of accepting any apology, you go ahead and accept these awesome glasses
Regards
Genome
Tribute to 1885 & those involved with Tease-AI.
Thank you for spending time on this awesome project!
Thank you for spending time on this awesome project!
- Trusfrated
- Explorer At Heart

- Posts: 465
- Joined: Mon Nov 08, 2010 8:41 am
- Gender: Male
Re: Tease AI Open Beta - URGENT INFO PLEASE READ
I have to say, I really like Side Chat. Being able to maximize the media window is a big plus for me. Thank you for doing this!
The problem is, I really like Glitter, too! Would it be possible to allow both an app (or Glitter only) and Side Chat to co-exist, perhaps in vertically resizable areas? I know screen real estate is at a premium; could perhaps the clock be relocated to the title or menu bar, or made semi transparent in the media window as a compromise?
Just thought I'd throw out a couple ideas. For me, Glitter is the app with the most potential for interaction during a script. So, it would be nice to see it if I use Side Chat exclusively.
The problem is, I really like Glitter, too! Would it be possible to allow both an app (or Glitter only) and Side Chat to co-exist, perhaps in vertically resizable areas? I know screen real estate is at a premium; could perhaps the clock be relocated to the title or menu bar, or made semi transparent in the media window as a compromise?
Just thought I'd throw out a couple ideas. For me, Glitter is the app with the most potential for interaction during a script. So, it would be nice to see it if I use Side Chat exclusively.
Re: Tease AI Open Beta - URGENT INFO PLEASE READ
Hi everyone
Just a sum up of all the new commands:
Added @YesMode() Command -
@YesMode() allows you perform a specific action if the user enters one of their "Yes" words while YesMode is active. There are two ways to use @YesMode()
@YesMode(Goto, GotoLine)
@YesMode(Video, GotoLine)
Goto mode will go to the specified GotoLine if the user enters a Yes phrase
Video mode will stop a currently playing video if the user enters a Yes phrase and go to the specified GotoLine. If the video ends or is stopped first, the Video mode will be cleared and the script will move to the next line as usual
You can clear YesMode with @YesMode(Normal)
Added @NoMode() Command -
@NoMode() allows you perform a specific action if the user enters one of their "No" words while NoMode is active. There are two ways to use @NoMode()
@NoMode(Goto, GotoLine)
@NoMode(Video, GotoLine)
Goto mode will go to the specified GotoLine if the user enters a No phrase
Video mode will stop a currently playing video if the user enters a No phrase and go to the specified GotoLine. If the video ends or is stopped first, the Video mode will be cleared and the script will move to the next line as usual
You can clear NoMode with @NoMode(Normal)
Added @CameMode() Command -
@CameMode() allows you perform a specific action if the user says one of the exact following expressions while CameMode is active: "Came", "I Came", "Just Came" or "I just came". Case doesn't matter, but Came mode will only pick up those four exact phrases. So "I just came" would activate it, "But I just came yesterday" would not. There are three ways to use @CameMode()
@CameMode(Goto, GotoLine)
@CameMode(Video, GotoLine)
@CameMode(Message, MessageText)
Goto mode will go to the specified GotoLine if the user enters one of the above phrases
Video mode will stop a currently playing video if the user enters one of the above phrases and go to the specified GotoLine. If the video ends or is stopped first, the Video mode will be cleared and the script will move to the next line as usual
Message mode will have the program process one of the above "I came" phrases as whatever text is specified as MessageText
You can clear CameMode with @CameMode(Normal)
Added @RuinedMode() Command -
@RuinedMode() allows you perform a specific action if the user says one of the exact following expressions while RuinedMode is active: "Ruined", "I Ruined", "Ruined it" or "I ruined it". Case doesn't matter, but Ruined mode will only pick up those four exact phrases. So "I ruined" would activate it, "I think I ruined my carpet" would not. There are three ways to use @RuinedMode()
@RuinedMode(Goto, GotoLine)
@RuinedMode(Video, GotoLine)
@RuinedMode(Message, MessageText)
Goto mode will go to the specified GotoLine if the user enters one of the above phrases
Video mode will stop a currently playing video if the user enters one of the above phrases and go to the specified GotoLine. If the video ends or is stopped first, the Video mode will be cleared and the script will move to the next line as usual
Message mode will have the program process one of the above "Ruined" phrases as whatever text is specified as MessageText
You can clear RuinedMode with @RuinedMode(Normal)
Added @Edge() Command - The @Edge() Command is used to indicate the user has been told by the domme to edge, just like @Edge currently does. However, @Edge() allows you to put any combination of the following modifiers in parentheses for different results when the user indicates they are on the edge:
Hold - User will be told to hold it
NoHold - User will be told to stop stroking
Orgasm - User will be told to cum
Ruin - User will be told to ruin
RuinTaunts - Enables @RuinTaunt Command Filter (used in Edge.txt and HoldTheEdge.txt) for lines that taunt the user about the orgasm they're about to ruin
LongHold - User will be made to hold a long edge
ExtremeHold - User will be made to hold an extreme edge
HoldTaunts - Enables @LongHold or @ExtremeHold Taunts (used in Edge.txt and HoldTheEdge.txt) for lines that taunt the user about how long the edge they're about to hold/holding is going to be
These Modifiers may be used in any combination:
@Edge(Orgasm, NoHold) - User will be told to cum when they reach the edge
@Edge(Ruin, Hold) - User will be told to hold an edge, and afterwards told to ruin their orgasm
@Edge(Orgasm, LongHold, HoldTaunts) - User will be told to hold a long edge then allowed to cum; @LongHold Taunts will be active
The program will disregard any combinations that don't make sense, such as:
@Edge(Orgasm, Ruin) - The program disregards "Ruin" regardless of order
@Edge(Hold, NoHold) - The program disregards "Hold" regardless of order
@Edge(Hold, RuinTaunts) User will be told to hold the edge, @RuinTaunt Command Filters will not be activated as no Ruin modifier was included
Added @DecideOrgasm() Command - This Command will make the domme decide if and how the user can have an orgasm based on their domme settings.
This works the same way as @DecideOrgasm. When @DecideOrgasm is used, the domme decides if the user will cum, ruin or be denied based on her domme settings. Depending on what she decides, @DecideOrgasm will either go to (Orgasm Allow), (Orgasm Ruin) or (Orgasm Deny).
@DecideOrgasm() allows you to set the GotoLines for allowed, ruined and denied orgasms (specified in that order - Allowed GotoLine first, Ruined GotoLine second and Denied GotoLine third). For example:
@DecideOrgasm(Allowed to Cum, Made to Ruin, Denied Orgasm) - In this case, if the domme has decided the user can cum, the script will move to (Allowed to Cum). If she decides to ruin, it will move to (Made to Ruin). And it will move to (Denied Orgasm) is she decides to deny. From there the next @Edge-related Command will end with an orgasm, ruined or denial depending on the domme's decision.
@DecideOrgasm() is extremely useful if you want to have more than one orgasm decision per script. This lets you set orgasm decision paths with different tones, such as having different reactions to the orgasm result based on the domme's mood
Added Command @RT() - This is shorthand for @RandomText(). @RT(boobs, tits, breasts) works exactly the same as @RandomText(boobs, tits, breasts).
Added Commands @RTOn and @RTOff - These are shorthand for @RapidTextOn and @RapidTextOff and function exactly the same.
I was using @RandomText and @RapidTextOn/Off so much in my own scripts that these shorthand Commands just became absolutely necessary. Hope others can take advantage of them as well.
Added Command @ShowLocalImage() - Since genre image Commands such as @ShowLesbianImage, @ShowFemdomImage etc can now reference Local or URL Files, @ShowLocalImage() has been created to allow you to specify genre images in Local files only. You can use a comma to create a list to randomly choose from, or use "not" to show any Local image but the genres specified. For example:
@ShowLocalImage(lesbian) - Show a local lesbian image
@ShowLocalImage(hentai, captions) - Show either a local hentai or captions image
@ShowLocalImage(not, captions) - Show any local image that is not a captions image
@ShowLocalImage(gay, maledom, not) - Show any local image that is not a gay or maledom image
Just a sum up of all the new commands:
Added @YesMode() Command -
@YesMode() allows you perform a specific action if the user enters one of their "Yes" words while YesMode is active. There are two ways to use @YesMode()
@YesMode(Goto, GotoLine)
@YesMode(Video, GotoLine)
Goto mode will go to the specified GotoLine if the user enters a Yes phrase
Video mode will stop a currently playing video if the user enters a Yes phrase and go to the specified GotoLine. If the video ends or is stopped first, the Video mode will be cleared and the script will move to the next line as usual
You can clear YesMode with @YesMode(Normal)
Added @NoMode() Command -
@NoMode() allows you perform a specific action if the user enters one of their "No" words while NoMode is active. There are two ways to use @NoMode()
@NoMode(Goto, GotoLine)
@NoMode(Video, GotoLine)
Goto mode will go to the specified GotoLine if the user enters a No phrase
Video mode will stop a currently playing video if the user enters a No phrase and go to the specified GotoLine. If the video ends or is stopped first, the Video mode will be cleared and the script will move to the next line as usual
You can clear NoMode with @NoMode(Normal)
Added @CameMode() Command -
@CameMode() allows you perform a specific action if the user says one of the exact following expressions while CameMode is active: "Came", "I Came", "Just Came" or "I just came". Case doesn't matter, but Came mode will only pick up those four exact phrases. So "I just came" would activate it, "But I just came yesterday" would not. There are three ways to use @CameMode()
@CameMode(Goto, GotoLine)
@CameMode(Video, GotoLine)
@CameMode(Message, MessageText)
Goto mode will go to the specified GotoLine if the user enters one of the above phrases
Video mode will stop a currently playing video if the user enters one of the above phrases and go to the specified GotoLine. If the video ends or is stopped first, the Video mode will be cleared and the script will move to the next line as usual
Message mode will have the program process one of the above "I came" phrases as whatever text is specified as MessageText
You can clear CameMode with @CameMode(Normal)
Added @RuinedMode() Command -
@RuinedMode() allows you perform a specific action if the user says one of the exact following expressions while RuinedMode is active: "Ruined", "I Ruined", "Ruined it" or "I ruined it". Case doesn't matter, but Ruined mode will only pick up those four exact phrases. So "I ruined" would activate it, "I think I ruined my carpet" would not. There are three ways to use @RuinedMode()
@RuinedMode(Goto, GotoLine)
@RuinedMode(Video, GotoLine)
@RuinedMode(Message, MessageText)
Goto mode will go to the specified GotoLine if the user enters one of the above phrases
Video mode will stop a currently playing video if the user enters one of the above phrases and go to the specified GotoLine. If the video ends or is stopped first, the Video mode will be cleared and the script will move to the next line as usual
Message mode will have the program process one of the above "Ruined" phrases as whatever text is specified as MessageText
You can clear RuinedMode with @RuinedMode(Normal)
Added @Edge() Command - The @Edge() Command is used to indicate the user has been told by the domme to edge, just like @Edge currently does. However, @Edge() allows you to put any combination of the following modifiers in parentheses for different results when the user indicates they are on the edge:
Hold - User will be told to hold it
NoHold - User will be told to stop stroking
Orgasm - User will be told to cum
Ruin - User will be told to ruin
RuinTaunts - Enables @RuinTaunt Command Filter (used in Edge.txt and HoldTheEdge.txt) for lines that taunt the user about the orgasm they're about to ruin
LongHold - User will be made to hold a long edge
ExtremeHold - User will be made to hold an extreme edge
HoldTaunts - Enables @LongHold or @ExtremeHold Taunts (used in Edge.txt and HoldTheEdge.txt) for lines that taunt the user about how long the edge they're about to hold/holding is going to be
These Modifiers may be used in any combination:
@Edge(Orgasm, NoHold) - User will be told to cum when they reach the edge
@Edge(Ruin, Hold) - User will be told to hold an edge, and afterwards told to ruin their orgasm
@Edge(Orgasm, LongHold, HoldTaunts) - User will be told to hold a long edge then allowed to cum; @LongHold Taunts will be active
The program will disregard any combinations that don't make sense, such as:
@Edge(Orgasm, Ruin) - The program disregards "Ruin" regardless of order
@Edge(Hold, NoHold) - The program disregards "Hold" regardless of order
@Edge(Hold, RuinTaunts) User will be told to hold the edge, @RuinTaunt Command Filters will not be activated as no Ruin modifier was included
Added @DecideOrgasm() Command - This Command will make the domme decide if and how the user can have an orgasm based on their domme settings.
This works the same way as @DecideOrgasm. When @DecideOrgasm is used, the domme decides if the user will cum, ruin or be denied based on her domme settings. Depending on what she decides, @DecideOrgasm will either go to (Orgasm Allow), (Orgasm Ruin) or (Orgasm Deny).
@DecideOrgasm() allows you to set the GotoLines for allowed, ruined and denied orgasms (specified in that order - Allowed GotoLine first, Ruined GotoLine second and Denied GotoLine third). For example:
@DecideOrgasm(Allowed to Cum, Made to Ruin, Denied Orgasm) - In this case, if the domme has decided the user can cum, the script will move to (Allowed to Cum). If she decides to ruin, it will move to (Made to Ruin). And it will move to (Denied Orgasm) is she decides to deny. From there the next @Edge-related Command will end with an orgasm, ruined or denial depending on the domme's decision.
@DecideOrgasm() is extremely useful if you want to have more than one orgasm decision per script. This lets you set orgasm decision paths with different tones, such as having different reactions to the orgasm result based on the domme's mood
Added Command @RT() - This is shorthand for @RandomText(). @RT(boobs, tits, breasts) works exactly the same as @RandomText(boobs, tits, breasts).
Added Commands @RTOn and @RTOff - These are shorthand for @RapidTextOn and @RapidTextOff and function exactly the same.
I was using @RandomText and @RapidTextOn/Off so much in my own scripts that these shorthand Commands just became absolutely necessary. Hope others can take advantage of them as well.
Added Command @ShowLocalImage() - Since genre image Commands such as @ShowLesbianImage, @ShowFemdomImage etc can now reference Local or URL Files, @ShowLocalImage() has been created to allow you to specify genre images in Local files only. You can use a comma to create a list to randomly choose from, or use "not" to show any Local image but the genres specified. For example:
@ShowLocalImage(lesbian) - Show a local lesbian image
@ShowLocalImage(hentai, captions) - Show either a local hentai or captions image
@ShowLocalImage(not, captions) - Show any local image that is not a captions image
@ShowLocalImage(gay, maledom, not) - Show any local image that is not a gay or maledom image
Tribute to 1885 & those involved with Tease-AI.
Thank you for spending time on this awesome project!
Thank you for spending time on this awesome project!
-
Stefaf
- Explorer At Heart

- Posts: 107
- Joined: Sat Apr 02, 2016 7:43 am
- Gender: Male
- Sexual Orientation: Straight
- I am a: None of the above
- Location: Germany
Re: Tease AI Open Beta - URGENT INFO PLEASE READ
genome231 wrote:Apology not accepted!
You're doing an awesome job and everyone is just thankful that you're even doing it in the first place!![]()
Thanks for bringing the bug to attention![]()
So instead of accepting any apology, you go ahead and accept these awesome glassesbecause you sir! Are awesome!
Sometimes I think that since I joined the project, it's falling apart and people don't like what i'm doing. We release a new version, and shortly thereafter, we note that I did not think of certain things. whats resulting in errors ... Well this time, at least the program did start and brought no error message. And i had several thousand Images from testing the reworked ImageCommands in a loop. this way i had enough useless images to test the @DeleteLocalImage and the new @DeleteImage command. ^^
But thanks anyway!
Do you also have a complete list? Or at least one that is relatively complete?genome231 wrote:Hi everyone
Just a sum up of all the new commands:
...
I ask, because we want to rework the script-Auditing. But I still lack of the overview, for what which command is exactly and how it is used and so on.
I once extracted a list of all the commands in Source-Code. But we haven't yet had time to fill this list with comments and descriptions - bugfixing is more important right now. If you or anyone else has a list with description, we could use it to create a simple help file and realize the script auditing.
Isn't ImageTagging awful enough?genome231 wrote:Hi 1885!
Had an idea and thought it worth sharing! :D
It comes in regards to the domme tag creator!
Theres a huge difference in how "sexy" pictures are and how sexy is to each individual. I think it would a nice addition if you beside tagging could sort of rate the pictures from 1-10 or 1-5.
1 being lowest, 10 highest.
then add a tag like the others but like @TagRating(5) <-- this show a image with a rating of 5. This could be further expanded by having commands like @TagRatingMinimum(), @TagRatingMaximum() and @TagRatingBetween().
@TagRatingMinimum(4) <-- this would show an image with a rating of at least 4 (4 included)
@TagRatingMaximum(6) <-- this would show an image with a rating of no higher than 6 (6 included)
@TagRatingBetween(3, 6) <-- this would show an image with a rating between 3 and 6 (3 & 6 included)...
It's possible, but in my poor opinion i would put this aside for a moment - I had the Idea once too. But i overthrew it for the moment. Imagetags aren't that far implemented yet. In general it's a great feature. I like, when the domme isn't talking nonsense about a certain image. But in Scripts which heavily use this feature, you don't see the lines containing it, if you don't have images with tags. You don't even get an information about it. That's a real problem.
But I would not be me if I had not been thinking about a solution:
Script auditing ... In my mind the after the revision, I would like so show a report, what you have to change in your configuration to get the best experience for the current personality.
This would include, what commands are not usable or filtered out, what ResponseFiles are missing, What Dommetags are missing in which SlideshowFolder, which ImageTags are missing, are all Jump-Marks set, are there any unrecognized Commands and maybe thousand things i don't even know yet.
This would give all users a tool, to look: Hey, that's something i'd like the domme to use/do. But i have to do this, to get it working.
And then all scripters can use those tagged Commands as much as they like, without running the risk that important things are filtered out.
But then we have to take care of another problem. ImageTagFile-Maintainance. Right now there is no simple way to maintain an imagefile. Are the images in there still available, is the file valid and all other things i can't imagine right now. This issue has to be solved at some point. It could be possible to transfer the Tags into the files itself or an external MetaFile, if the format has no Metadatasection...
This way it could be even possible to maintain the Tags in a separate program like PS-Brigde, Lightroom or whatever and import them back into Tease-AI. Afterwards images could be shared with applied tags - Of course, under the rules of copyright.
But that's all music of the future... Right now Script Auditing and Bugfixing is what needs to be done.
In general it's possible. In Tease-AI-UI? A few days ago i tried to add fullscreenMode. In general applications it's a piece of cake, but in Tease-Ai UI-is something ... lets say... difficult. But maybe 1885 could help you here - I would definitely break the UI and rework it.Trusfrated wrote:I have to say, I really like Side Chat. Being able to maximize the media window is a big plus for me. Thank you for doing this!
The problem is, I really like Glitter, too! Would it be possible to allow both an app (or Glitter only) and Side Chat to co-exist, perhaps in vertically resizable areas? I know screen real estate is at a premium; could perhaps the clock be relocated to the title or menu bar, or made semi transparent in the media window as a compromise?
Just thought I'd throw out a couple ideas. For me, Glitter is the app with the most potential for interaction during a script. So, it would be nice to see it if I use Side Chat exclusively.
- 1885
- Explorer At Heart

- Posts: 648
- Joined: Fri Jul 08, 2011 4:27 am
- Gender: Male
- Sexual Orientation: Straight
- I am a: Switch
Re: Tease AI Open Beta - URGENT INFO PLEASE READ
The UI actually is going to be broken down and reworked. I want it to be smoother, less convoluted (in code) and more versatile in terms what you can see at any given time and what size you can make it.Trusfrated wrote:I have to say, I really like Side Chat. Being able to maximize the media window is a big plus for me. Thank you for doing this!
The problem is, I really like Glitter, too! Would it be possible to allow both an app (or Glitter only) and Side Chat to co-exist, perhaps in vertically resizable areas? I know screen real estate is at a premium; could perhaps the clock be relocated to the title or menu bar, or made semi transparent in the media window as a compromise?
Just thought I'd throw out a couple ideas. For me, Glitter is the app with the most potential for interaction during a script. So, it would be nice to see it if I use Side Chat exclusively.
It may take a little time to get there, but the UI work is on the roadmap for Patch 56.

Re: Tease AI Open Beta - URGENT INFO PLEASE READ
Gratz on your 500th post!1885 wrote:..
And guys, keep up the good work, I bet there are plenty of people who are using this program without even having an account on here!
I bet you're being appreciated, for all that you do!
- Trusfrated
- Explorer At Heart

- Posts: 465
- Joined: Mon Nov 08, 2010 8:41 am
- Gender: Male
Re: Tease AI Open Beta - URGENT INFO PLEASE READ
Just a suggestion...
Could the Wishlist be developed so it could be used during a session? It seems like now, it is only for quick little interludes outside of a normal session. If that's not the case, I haven't seen anyone write any scripts that use it. I see a lot of potential for financial domination-type scripts that involve buying the domme items in order to change her mind about things. For instance, to get out of punishment, get out of chastity, avoid a denial or a ruined orgasm, change her apathy level, etc. And maybe sometimes there is a chance you wasted your tokens and she doesn't care about being nice to you.
I suppose tokens could be used for these kinds of things currently? I know the domme can give me tokens for Risky Pick, but can I give her tokens to "buy" 15 minutes out of chastity? But buying her gifts seems like a less awkward way to get access to favors, as opposed to handing her "cash" in my opinion.
Could the Wishlist be developed so it could be used during a session? It seems like now, it is only for quick little interludes outside of a normal session. If that's not the case, I haven't seen anyone write any scripts that use it. I see a lot of potential for financial domination-type scripts that involve buying the domme items in order to change her mind about things. For instance, to get out of punishment, get out of chastity, avoid a denial or a ruined orgasm, change her apathy level, etc. And maybe sometimes there is a chance you wasted your tokens and she doesn't care about being nice to you.
I suppose tokens could be used for these kinds of things currently? I know the domme can give me tokens for Risky Pick, but can I give her tokens to "buy" 15 minutes out of chastity? But buying her gifts seems like a less awkward way to get access to favors, as opposed to handing her "cash" in my opinion.
- 1885
- Explorer At Heart

- Posts: 648
- Joined: Fri Jul 08, 2011 4:27 am
- Gender: Male
- Sexual Orientation: Straight
- I am a: Switch
Re: Tease AI Open Beta - Updated to Patch 54
Patch 54, where are you? Right here! (Fuck, I'm old
)
Reminder: If you've been using Patch 53 and had session image saving turned off, please check your root folder (C:, F:, G: etc.) because a bug caused all blog images to be saved to the root folder. That has been fixed for this patch.
Patch 54 Updated with 54.4
Here: https://mega.nz/#!HIM2xbTK!TsBhikBvRube ... KeQyu0NGRg
Important Note: Tease AI's assembly version will now reflect the current patch (so this is Tease AI version 0.54). This means your current settings will not be immediately accessible. To import your current settings to this version, use the Import button in the upper right hand corner of the General Settings menu, and navigate to the Tease AI folder in your Local AppData directory (If you need help finding this directory, click the Start button in Windows and search for %LocalAppData%Tease_AI). Select your most resent user.config and Tease AI will restart with those settings which will then be saved.
As of Patch 54, Stefaf's code duplicates this config file and saves it to "[Tease AI root folder]SystemSettings[version].user.config". So the importing process will be much easier for future versions, as you will simply be able to import from this location.
If you need further assistance importing previous settings, please let me know and I'll walk you through it in more detail.
Patch Notes:
Critical Bugfixes -
Stefaf: BugFix and Cause... Remote Images where stored to the RootDirectory, if Save Blog Images From Session was deactivated
Improvements -
Major overhaul to the Tasks system (The daily task letters the domme can create using the @SendDailyTasks Command)
Side Chat now functions independently of other Apps. If Side Chat was active when another app was opened, then Side Chat will return on its own once that app is closed
Enhanced @CustomTask() Command and added Session Tasks settings in Ranges settings tab - Session tasks (@CBT, @CBTBalls, @CBTCock and @CustomTask()) no longer run for a random number of times. The number of times tasks run is now determined by the new settings in the Ranges settings tab for Session Tasks. For Custom Tasks, you may specify a specific amount of times to run the task using a comma. For example:
Added "Display Progress in Chat Window" option to Writing Tasks app. This setting provides feedback on how many lines/mistakes are remaining in chat during the writing task
Added Button to WritingTasks panel that allows the user to open Side Chat directly from that panel
Decreased the amount of time it takes for the domme to make her first Edging taunt by 15 seconds
BugFixes -
Tease AI will now move to the next script type in the cycle if the current script has run out of lines
Fixed bug where Glitter Contacts would drop the last word of their sentences when the domme was out of the room
Fixed bug where Playlists did not move on to Link scripts after running Modules
Fixed bug where Responses would get locked to [After Tease] lines if the domme continued a session after the orgasm decision
"Edging Ends Taunts" is no longer checked after the Taunt Cycle ends. This bug occurred if the Module didn't immediately call @StopStroking or @Edge
@ShowImage type Commands in Linear scripts are now filtered correctly when @LockImages is activated
@LockImages now functions correctly when Glitter Contacts are in the room
@CheckDate() should now work correctly
"Like This Image" and "Dislike This Image" in the picture window right-click menu now disable the correct menu strip items when clicked
SYS_EdgeTotal is now updated when EdgeMode edges are reported
@Month() and @Day() Command Filters have been added to the new Filtering process. hey were left out of Patch 53 by accident
Fixed bug where @SubOld and @SubYoung were not getting filtered correctly
Commands -
Added @CustomMode() Command - You can use @CustomMode() to set any keyword or phrase to a mode that will move to a GotoLine in the script when used. The current types that @CustomMode() can use are Goto and Video. For example:
Added "Deny" overload to @Edge() Command (For example, @Edge(Hold, Deny). This functions exactly like a denied orgasm after the @DecideOrgasm Command. This simply lets the program know that the user was just denied an orgasm. Mostly useful for coordinating with end of tease Task letters
Stefaf: Added Command @DeleteImage: This will remove the current image from all local Sources. (File system, URL-Files, LikedList, DislikedList, LocalImageTagList). But it won't delete an image located in the Domme- or Contacts-Image directory or one of it's subdirectories
Added @LockVideo and @UnlockVideo Commands - @LockVideo will prevent Tease AI from switching back to the image window when a video ends. This is useful for times when you want to play multiple videos in a row for whatever reason without the domme slideshow popping up in between. @UnlockVideo will deactivate this mode and switch back to the image window when used
Keywords -
New #Keywords added: #EdgeHold, #LongHold, #ExtremeHold - Returns a random value based on the user's Sub settings, and automatically displays it as an amount of time in seconds, minutes and/or hours. For example:
Stefaf: #ButtImageCount - Displays the number of local Butt images (if activated) as well as the number of links in the selected Butt genre URL File (if activated)
Stefaf: #BoobsImageCount - Displays the number of local Boobs images (if activated) as well as the number of links in the selected Boob genre URL File (if activated)
Fixes added from Community Members:
As always, if you have any questions, comments or feedback please let me know and I'll address them as soon as I can. Please report any bugs and we'll do our best to take of those as well

Reminder: If you've been using Patch 53 and had session image saving turned off, please check your root folder (C:, F:, G: etc.) because a bug caused all blog images to be saved to the root folder. That has been fixed for this patch.
Patch 54 Updated with 54.4
Here: https://mega.nz/#!HIM2xbTK!TsBhikBvRube ... KeQyu0NGRg
Important Note: Tease AI's assembly version will now reflect the current patch (so this is Tease AI version 0.54). This means your current settings will not be immediately accessible. To import your current settings to this version, use the Import button in the upper right hand corner of the General Settings menu, and navigate to the Tease AI folder in your Local AppData directory (If you need help finding this directory, click the Start button in Windows and search for %LocalAppData%Tease_AI). Select your most resent user.config and Tease AI will restart with those settings which will then be saved.
As of Patch 54, Stefaf's code duplicates this config file and saves it to "[Tease AI root folder]SystemSettings[version].user.config". So the importing process will be much easier for future versions, as you will simply be able to import from this location.
If you need further assistance importing previous settings, please let me know and I'll walk you through it in more detail.
Patch Notes:
Critical Bugfixes -
Stefaf: BugFix and Cause... Remote Images where stored to the RootDirectory, if Save Blog Images From Session was deactivated
Improvements -
Major overhaul to the Tasks system (The daily task letters the domme can create using the @SendDailyTasks Command)
Linear scripts now parse Command Filters using the new system, which should provide much greater stabilityTasks should now function as originally intended
Multiple uses of the same #Keyword will now produce different results
Tasks are now filtered through the new routine which should greatly improve stability
Task-related #Keywords should no longer return 0 as a value
@RandomText() and @RT() can now be used in Task lines
"Domme is sending you a file" window now displays correctly when Lazy Sub AV is active
Task letters are now able to process the following Commands during their creation:
@SetFlag(), @TempFlag(), @DeleteFlag(), @SetVar[], @ShowVar[], @ChangeVar[], @RoundVar[], @DeleteVar[], @SetDate()
@UpdateOrgasm, @UpdateRuined, @ChastityOn, @ChastityOff, @RestrictOrgasm(), @RestrictOrgasm, @PornAllowedOff, @PornAllowedOn
@DecreaseOrgasmChance, @IncreaseOrgasmChance, @DecreaseRuinChance, @IncreaseRuinChance,
@AddTokens(), @RemoveTokens(), all other Token related Commands
@Morning, @Afternoon and @Night Command Filters now filter more accurately relative to user's Daily Wake Up Time
Task-related Ranges added to Ranges tab, corresponding to the following #KeyWords: #TaskStrokes, #TaskStrokingTime, #TaskEdges, #TaskHoldTheEdgeTime, #TaskCBTTime
Side Chat now functions independently of other Apps. If Side Chat was active when another app was opened, then Side Chat will return on its own once that app is closed
Enhanced @CustomTask() Command and added Session Tasks settings in Ranges settings tab - Session tasks (@CBT, @CBTBalls, @CBTCock and @CustomTask()) no longer run for a random number of times. The number of times tasks run is now determined by the new settings in the Ranges settings tab for Session Tasks. For Custom Tasks, you may specify a specific amount of times to run the task using a comma. For example:
Implemented Daragorn's Timed Writing Tasks feature. Timed Writing Tasks can be activated/deactivated in the Ranges settings tab@CustomTask(Spanking, 5) - This would run the Custom Task "Spanking" 5 times. This number includes the first instruction taken from "_First.txt
Added "Display Progress in Chat Window" option to Writing Tasks app. This setting provides feedback on how many lines/mistakes are remaining in chat during the writing task
Added Button to WritingTasks panel that allows the user to open Side Chat directly from that panel
Decreased the amount of time it takes for the domme to make her first Edging taunt by 15 seconds
BugFixes -
Tease AI will now move to the next script type in the cycle if the current script has run out of lines
Fixed bug where Glitter Contacts would drop the last word of their sentences when the domme was out of the room
Fixed bug where Playlists did not move on to Link scripts after running Modules
Fixed bug where Responses would get locked to [After Tease] lines if the domme continued a session after the orgasm decision
"Edging Ends Taunts" is no longer checked after the Taunt Cycle ends. This bug occurred if the Module didn't immediately call @StopStroking or @Edge
@ShowImage type Commands in Linear scripts are now filtered correctly when @LockImages is activated
@LockImages now functions correctly when Glitter Contacts are in the room
@CheckDate() should now work correctly
"Like This Image" and "Dislike This Image" in the picture window right-click menu now disable the correct menu strip items when clicked
SYS_EdgeTotal is now updated when EdgeMode edges are reported
@Month() and @Day() Command Filters have been added to the new Filtering process. hey were left out of Patch 53 by accident
Fixed bug where @SubOld and @SubYoung were not getting filtered correctly
Commands -
Added @CustomMode() Command - You can use @CustomMode() to set any keyword or phrase to a mode that will move to a GotoLine in the script when used. The current types that @CustomMode() can use are Goto and Video. For example:
Added Command @ClearChat - Clears the main chat window and Side Chat@CustomMode(I'm done, Goto, Finished Task) - This would move the script to the line (Finished Task) if the user types "I'm done" (not case sensitive)
@CustomMode(I saw boobs, Video, Video Closed) - This would stop a video and move to the line (Video Closed) if the user types "I saw boobs" (not case sensitive)
Only one @CustomMode() Command should be used per line, but you may have as many custom modes activated at a time that you wish. Remember that individual Modes are cleared when they resolve, and all modes are cleared when transitioning between script types. To manually clear a mode, use @CustomMode(ModeText, Normal)
Added "Deny" overload to @Edge() Command (For example, @Edge(Hold, Deny). This functions exactly like a denied orgasm after the @DecideOrgasm Command. This simply lets the program know that the user was just denied an orgasm. Mostly useful for coordinating with end of tease Task letters
Stefaf: Added Command @DeleteImage: This will remove the current image from all local Sources. (File system, URL-Files, LikedList, DislikedList, LocalImageTagList). But it won't delete an image located in the Domme- or Contacts-Image directory or one of it's subdirectories
Added @LockVideo and @UnlockVideo Commands - @LockVideo will prevent Tease AI from switching back to the image window when a video ends. This is useful for times when you want to play multiple videos in a row for whatever reason without the domme slideshow popping up in between. @UnlockVideo will deactivate this mode and switch back to the image window when used
Keywords -
New #Keywords added: #EdgeHold, #LongHold, #ExtremeHold - Returns a random value based on the user's Sub settings, and automatically displays it as an amount of time in seconds, minutes and/or hours. For example:
Stefaf: #BlogImageCount - Displays the number of links contained in all active URL FilesBefore you go to bed tonight, I want you to hold an edge for #LongHold
This would return a value based on the user's Long Edge Hold settings, rounded to the nearest 5. If the user had 3-5 minutes as their range for example, and the program selects a random time of 202 seconds, then the above line would display as follows:
Before you go to bed tonight, I want you to hold an edge for 3 minutes and 20 seconds
Stefaf: #ButtImageCount - Displays the number of local Butt images (if activated) as well as the number of links in the selected Butt genre URL File (if activated)
Stefaf: #BoobsImageCount - Displays the number of local Boobs images (if activated) as well as the number of links in the selected Boob genre URL File (if activated)
Fixes added from Community Members:
Stefaf has also created the following list if you would like to see the Commands/Keywords that have been added or altered for this patch at a glance:Stefaf: Bugfix ErrorImage was shown randomly if one of all imagegenres had no images.
Stefaf: Bugfix ContectMenu MainImageBox did not activate or deactivate the MenuItems correct.
Stefaf: Improvement: Remove from URL-File option in ContextMenu MainPicturebox removes a ImageUrl from all URL-Files.
Stefaf: Function txt2List(String) was not able to deal path = "" or path = nothing. Improved Error handling and logging.
Stefaf: Added Offline-Mode-Support to the ImageDataContainer-Class and fixed some minor bugs in it.
Stefaf: All lists retrieved with functions in Class myDirectory are now sorted alphabetically.
Stefaf: Added Feature: User-Settings are now saved in: "App-DirectorySystemSettings"
- Spoiler: show
Stefaf: Commands @PornAllowedOff and @PornAllowedOn where not replaced correct in Domme Output.
Stefaf: ImageCount-Keywords didn't count Images in URL-Files and none did neither react to OfflineMode nor @PornAllowedOff.
Stefaf: #LocalImageCount didn't count local Butt and Boob Images.
Stefaf: ImageDataContainer was searching Sub-folders instead of top level only and vice versa.
Stefaf: GetGoto() was not able to jump to the first line of a script.
Stefaf: ErrorImage has been shown randomly if one of all image-genres had no images.
Stefaf: ContextMenu of MainImageBox did not activate or deactivate the MenuItems correct.
Stefaf: Improvement: Remove from URL-File option in ContextMenu MainPicturebox now removes a ImageUrl from all URL-Files.
Daragorn: BugFix: "Edging Ends Taunts" state wasn't reinitialized when Tease AI was reset
Daragorn: Clean-up of 1885's implementation of Daragorn's original Timed Writing code
Daragorn: BugFix: Some aspects of the program didn't pause when Settings Menu was open and "Pause Program When Settings Menu is Visible" wasn't checked
Daragorn; BugFix: When Glitter contacts were present and an image was shown as part of a response, the image would immediately get replaced by a picture of the domme or contact
Stefaf: BugFix and Cause... Remote Images where stored to the RootDirectory, if Save Blog Images From Session was deactivated.
Stefaf: Bugfix: @DeleteLocalImage was sometimes deleting the wrong image. It also removes the file from LikedList, DislikedList and LocalImageTagList now. But it won't delete an image located in the Domme- or Contacts-Image directory or one of it's subdirectories.
Stefaf: Bugfix & Rework : @ShowImage[]
- Spoiler: show
Stefaf - Bugfix: BBnB is working now. (@TnAFastSlides, @TnASlowSlides, @TnASlides, @CheckTnA)
Stefaf - Improvement: Added Logging if a custom vocabularyFile is missing. Now this will create a new Error-Log-Entry.
Stefaf - Improvement: Removing an URL from an URL-File in SettingsWindow took way too long. Now it's faster.
Stefaf - Imporvement: @ShowLocalImage() Now the ImageDataContainer-Class is used. It doesn't try to get an single image from a single random genre any more. Instead it tries to get a single image from all given genres.
Stefaf - Improvement: Added logging at several points.
Stefaf - Bugfix: 404 caused the Script to stop. Errors during ImageLoading will create now a LogEntry.
Stefaf - Added Support for relative filepaths when using GenreImage-UrlFiles. Files outside the "ImagesSystemUrl Files"-directory are neither included on Rebuild nor Refresh! But they are included in DeleteCommands.
The PropertyNames containing the URL-FilePaths have been renamed, in order to enhance readability. Those settings have to be reapplied. This will also prevent the use of wrong Url-Files, when the settings were imported.
Stefaf - Improvement: Changed the way how UserSettings are stored. Now every(!) time a setting has changed, the settingsfile will be saved after a delay of one second(to keep disk traffic low).
Stefaf - Improvement: Changed Labels for ImageURL-Files to readonly Textboxes. the Settings are now applied via DataBinding. Same on the ImageUrl-Checkboxes.
- Spoiler: show
As always, if you have any questions, comments or feedback please let me know and I'll address them as soon as I can. Please report any bugs and we'll do our best to take of those as well
Every aspect of the program will be overhauled at some point, most likely in every Patch (for this one it was the Tasks feature). The Wishlist feature will be overhauled and enhanced at some point, but there are several priority things we'll have to get through first. At some point though, for sureTrusfrated wrote:Could the Wishlist be developed so it could be used during a session? It seems like now, it is only for quick little interludes outside of a normal session. If that's not the case, I haven't seen anyone write any scripts that use it. I see a lot of potential for financial domination-type scripts that involve buying the domme items in order to change her mind about things. For instance, to get out of punishment, get out of chastity, avoid a denial or a ruined orgasm, change her apathy level, etc. And maybe sometimes there is a chance you wasted your tokens and she doesn't care about being nice to you. :'-(
Last edited by 1885 on Sat May 28, 2016 12:42 am, edited 4 times in total.

Re: Tease AI Open Beta - Updated to Patch 54
What a sweet patch!
Great work! :D
Regards
Genome
Great work! :D
Regards
Genome
Tribute to 1885 & those involved with Tease-AI.
Thank you for spending time on this awesome project!
Thank you for spending time on this awesome project!

