Tease AI General Discussion

[1885]

Hey everyone, now that I've had a chance to find my bearings again I wanted to give an update on my plans moving forward.

First of all, let me say that I really appreciate the support from everyone. I didn't quite know what to expect when I got myself back into the forums, but everyone's been really understanding and it means a lot. Literally the worst I've had to deal with is the weird disorientation of the site itself being almost but not quite exactly like I remember it So really, thank you everyone.

I was also concerned that when I went back to code again, I wouldn't remember a damn thing about how to do it. Fortunately I can say that this is not the case, if anything I've been moving through my immediate bug-fixing goals faster than I expected. I had a lot of work to tie up the mess I left myself with the Glitter enhancements, but I've gotten that taken care of along with several bug fixes. All that I have left to do is write a script using the new Glitter Commands, so patch 42 should be up within the next couple of days.

I've read and re-read through the Tease AI threads, and I've put together a roadmap for development of Tease AI.

The two biggest priorities for me right now is bug-fixing and content creation.

The bugs are a problem. This next build will fix a few of them, but I think one of the biggest issues is not having a single source for bugtracking. Bugs reports are spread out over so many pages in this single thread that people aren't sure what's been reported, what's been fixed, and despite how religiously I read the the thread before, I even tended to miss some bug reports myself.

I'm looking into a couple options for organized bugtracking at the moment, but I will possibly have to hear back from some people before I know what avenue for sure to take. Bear with me, but in the interim I will still handle bugs as best I can.

The second priority for me right now is content creation, both in creating it myself as well as making it easy for other people. Currently the documentation for Tease AI is out of date, unorganized and in a couple cases incorrect (as with a couple typos in the guides). I'm also working on ideas to get documentation and resources more organized as well, and will move forward with that when I have something more concrete.

The other priority for me with content creation is to actually flesh out my Total Brat domme into a robust Personality that I can release to everyone. Wicked Tease is far from a complete Personality, more of a starter kit to give people ideas and let them add to it or create their own Personalities. The problem is, between bugs and scattered resources it's been way more difficult than I intended to take up scripting for Tease AI. Improved resources will help and is on my agenda, but I also want to be able to point to scripts in a more complete Personality to answer specific questions, give people guidelines to implement their own ideas, as well as scratch my own itch to be creating again. I never intended to be a programmer, I'm an artist foremost, and creating cruel women is what I do

I don't have an ETA for Total Brat, but I've been working about 50/50 on coding and scripting, so progress will be steady.

Once I have my feet planted a little more firmly in what I'm doing, I'll make Tease AI open source again and keep the builds updated. That will happen for sure, I just don't have an ETA for that yet either. I know there's quite a few people willing to help out in various things, I'm just not in a place where I can really mess with github again at the moment.

So TL;DR

Everyone here is awesome
Patch 42 will be up within a couple of days
I will be primarily focused on a half and half split of fixing bugs and making it easier to track bugs, and creating a full release for Total Brat
My secondary focus is improving documentation and resources for scripting and program operation
Tease AI will go open source again in the future, just don't know exactly when

If you have any questions, comments, feedback or opinions please let me know, I'll be happy to hear whatever you got

[mr-max]

[Drblaze2]

Hi, I've never posted in this forum (I think, I could be wrong). I do appreciate all the work you're putting into this. Truly, it's a great thing. Thanks again :)

[1885]

Well, as I resume my search for the answer to the ultimate question of life, the universe and everything, it's only fitting that that brings us to

Patch 42

https://mega.nz/#!bFcTyC4J!0Pi9qxMFd2hs ... PToxgOBrKI

Patch Notes:

Current patch number will appear in the title bar of the program: Provided I remember to keep this updated with every patch, this should help as I get ready to get serious about bigfixes

Tease AI now catches exceptions in many cases where there's no valid line to output to the chat window: Sometimes the code would end up parsing a list of choices down to nothing, which the program would try to select something from causing the program to crash. Now when this occurs in most cases, Tease AI will output an error message to the chat window (such as "ERROR: Tease AI did not return a valid Video Taunt"). This will allow the program to continue as normal instead of halting due to a single error.

Fixed the "spoiler" aspect of telling the domme you're close when using the metronome: When you told the domme you're close while using the metronome, the metronome would stop immediately if she was about to make you hold it, but keep going if she was going to tell you to stop. The metronome now keeps playing until she types her response, regardless if she's going to make you hold it or simply stop.

Fixed bug that caused script names to sometimes show up twice in the Scripts menu

Improved performance when handling many scripts in the Scripts menu: I've seen reports that the Script selection menu gets bogged down for some users when they have an excessive number of Scripts. I've gone through the code to improve performance in this area. If you had issues with this, please let me know how this patch works for you when browsing Scripts.

Tease sessions will no longer end if a Module Bookmark is active

Interrupts will now exit CBT routines correctly: Interrupts should now exit CBT routines immediately rather than waiting for them to finish.

#GeneralTime settings changed so that domme no longer thinks of it as morning until 4 a.m.

Glitter Overhaul: Changes in this patch

Before my hiatus I was working on some major changes to Glitter and its applications. Implementing these changes was actually poor timing on my part. My vision for it was a bit larger than I realized, and looking back on it now I think more stability issues should have been worked out first before I even thought about it. But the inspiration was too strong, and I ended up leaving myself with a huge mess of dangling code when I got back. I've been able to start getting it tied up, but to get it finished completely (and properly) is going to take a pretty good amount of effort. There's too many other priorities to completely focus on Glitter, but I have laid the foundation and will be putting it together in major pieces as I go - just not to the detriment of other critical areas I want to focus on. That being said, here's what's currently available in this patch:

Glitter settings in Apps tab have been updated to reflect the changes

• Glitter now has three modes: On, Scripts and Off. Off disables Glitter entirely, On will run all Glitter posts. Scripts mode will only display posts specifically called with the @Glitter() Command.
  
  Glitter Contacts are no longer defined by checkbox tags. They are now defined by Contact 1, Contact 2 and Contact 3. The personality of these Contacts is meant to be defined by the creator of the overall Personality, but adherence to that suggestion is not strictly necessary. It will provide a consistent theme for the dommes friends however. The Personality creator can provide descriptions for each Contact by creating a txt file in the AppsGlitter folder called Contact_Descriptions.txt. If this file does not exist, the group boxes in the Glitter tab will simply show them as Contact 1, Contact 2 and Contact 3.
  
  Each Glitter Contact has her own slideshow directory. This works exactly the same way as the domme directory, and allows the program to run separate slideshows for the domme's friends when they enter chat.

Commands:

@Glitter() - This Command lets you call a specific Glitter post from within scripts. These scripts should be placed in AppsGlitterScript.

So for instance, @Glitter(About to Ruin) would call the post saved at AppsGlitterScriptAbout to Ruin.txt

These scripts are written the same as other Glitter posts scripts, with the domme's initial post at the top and possible responses below. You can have as many possible responses for each Contact you like, the program will select one valid at random for each.

@AddContact1 - This Command lets Contact 1 join the chat room. A message will display in the window, and the program will then remember there's more people present than just you and the domme and act accordingly in various circumstances.

@RemoveContact1 - This Command removes Contact 1 from the chat room.

When scripts where one of the domme's Contacts is speaking, you must put the appropriate Command Filter at the start of the line! For example:

• Okay get ready #SubName, here she comes @AddContact1
  Hi #Contact1!
  @Contact1 Hi yourself #DomName #EmoteHappy
  @Contact1 And hello to you too #SubName
  @Contact1 I've always wondered what you two get up to in here
  Well, now you're about to find out #Lol

For more information, check out the included Module "Glitter Module_1", it uses the new Commands extensively

System Keywords

#Contact1 - Gets replaced with Contact 1's name
#Contact2 - Gets replaced with Contact 2's name
#Contact3 - Gets replaced with Contact 3's name
#ShortName - Gets replaced with the name entered for the domme in the Glitter tab of the Apps section. For instance, if the domme is named Elizabeth, and her short name is Liz, you can have her friends call her Liz by using #ShortName

Note: Contact1 is the only Contact currently implemented. Using any other Contacts will work to an extent as the program is now, but will cause problems in some areas so I wouldn't recommend using them just yet.

If you try the Glitter Module or making your own scripts with Contact 1, make sure to do the following two things:

Set up a slideshow for Contact1, it really goes a long way to demonstrate the new Glitter changes, and do not end a Module without removing Contact 1 first. Contacts will have their place in Stroke Taunts, but that is not functional just yet.

There's actually a lot more stuff already in the program concerning the Glitter implementation, but this is what I'm releasing at the moment as other Commands won't work properly until I flesh some more things out. Glitter will grow little by little while I complete other work until it's finally done.

___________________________________

I'll still mainly be working on fixing bugs and building Total Brat, but as always I'm here to help any way I can. If you have any questions about how the new Glitter stuff works, or new bugs from this patch, or old stuff to remind me about, please send anything you got my way. In the meantime I'll keep working on the next patch and make announcements related to milestones on the roadmap as I have more information.

OB Patch 42.rar

Tease AI Open Beta Patch 42

(798.54 KiB) Downloaded 208 times

[avatarbr]

Glad to see you back 1885.

This Glitter update looks promising. I tried something in this direction in the Extend version of Wicked Tease. I will use it when this is ready.

One question. You are planning in get commands from Glitter? something like:

I will punish you @Glitter(Need suggestions)

Code: Select all

(Need suggestions)
Need suggestions about how punish #Subname
#Contact1 How about some CBT?

And the module get the suggestion and run the @CBT module.

I am bad in explain my ideas

[opiate]

Glad to see you back 1885.

This Glitter update looks promising. I tried something in this direction in the Extend version of Wicked Tease. I will use it when this is ready.

One question. You are planning in get commands from Glitter? something like:

I will punish you @Glitter(Need suggestions)

Code: Select all

(Need suggestions)
Need suggestions about how punish #Subname
#Contact1 How about some CBT?

And the module get the suggestion and run the @CBT module.

I am bad in explain my ideas

The only way to get a guaranteed trigger would be to use the new @Glitter commands in an interrupt that was called in your module. That would allow you to reliably call it.

[xeenith]

okay problem that is making me tearing my hairs... I ALWAYS keep chastity modules unchecked, I find it boring as hell and it's so not my thing, yet after several weeks or not using the program, I put the new patch, tried it a little and I'm supposed locked up

I can't find an option anywhere in file config or flags to deactivate the status and since no modules are up, the AI can't seem to deactivate it itself either soooo what can I do to get the supposed cage off one and for all, because in this state there is no use the the program at all

[1885]

okay problem that is making me tearing my hairs... I ALWAYS keep chastity modules unchecked, I find it boring as hell and it's so not my thing, yet after several weeks or not using the program, I put the new patch, tried it a little and I'm supposed locked up

I can't find an option anywhere in file config or flags to deactivate the status and since no modules are up, the AI can't seem to deactivate it itself either soooo what can I do to get the supposed cage off one and for all, because in this state there is no use the the program at all

Sorry you've been having trouble, I definitely need to add an option in the settings menu to modify system states like Chastity. In the meantime, you can fix this by making a new text document that looks like this:

• This will fix the chastity problem @ChastityOff
  The problem is now fixed
  @End

Name it whatever you want like "ChastityFix.txt" and save it anywhere. Then load Tease AI and click on the little folder button on the bottom of the apps window. Open the txt file you just created, and when the domme says "the problem is now fixed:, restart Tease AI. You should now be "out of chastity" and be able to run the program like normal.

I'll add an actual setting for this in an upcoming patch so you don't have to resort to this if it happens again.

[png]

Then load Tease AI and click on the little folder button on the bottom of the apps window. Open the txt file you just created, and when the domme says "the problem is now fixed:, restart Tease AI. You should now be "out of chastity" and be able to run the program like normal.

Holy shit I never knew about that!!! I want my hours testing script back!!!!

[opiate]

Then load Tease AI and click on the little folder button on the bottom of the apps window. Open the txt file you just created, and when the domme says "the problem is now fixed:, restart Tease AI. You should now be "out of chastity" and be able to run the program like normal.

Holy shit I never knew about that!!! I want my hours testing script back!!!!

I second this lol

[Lestat]

Holy shit I never knew about that!!! I want my hours testing script back!!!!

I second this lol

Lol, I sympathize

[djord]

The other priority for me with content creation is to actually flesh out my Total Brat domme into a robust Personality that I can release to everyone. Wicked Tease is far from a complete Personality, more of a starter kit to give people ideas and let them add to it or create their own Personalities. The problem is, between bugs and scattered resources it's been way more difficult than I intended to take up scripting for Tease AI. Improved resources will help and is on my agenda, but I also want to be able to point to scripts in a more complete Personality to answer specific questions, give people guidelines to implement their own ideas, as well as scratch my own itch to be creating again. I never intended to be a programmer, I'm an artist foremost, and creating cruel women is what I do

I don't have an ETA for Total Brat, but I've been working about 50/50 on coding and scripting, so progress will be steady.

Woohoo! Is she going to be more of a sociopath?

Thank you for the bug fixes!

[1885]

Holy shit I never knew about that!!! I want my hours testing script back!!!!

I second this lol

Lol, I sympathize

I guess I should I have put a "Test Script" label on that button. Sorry about that

Woohoo! Is she going to be more of a sociopath?
Thank you for the bug fixes!

She's not a sociopath like "1885 webtease sociopath", but she's a lot more cruel. With Total Brat there's this undercurrent that your only purpose to her is to suffer, and that makes you pathetic enough in her eyes that she has no real sympathy for you. Not so much in a humiliation sense, more in a "she's going to do whatever she wants to you and she couldn't care less if you can take it or not because she has no respect or pity for you" sense.

[djord]

She's not a sociopath like "1885 webtease sociopath", but she's a lot more cruel. With Total Brat there's this undercurrent that your only purpose to her is to suffer, and that makes you pathetic enough in her eyes that she has no real sympathy for you. Not so much in a humiliation sense, more in a "she's going to do whatever she wants to you and she couldn't care less if you can take it or not because she has no respect or pity for you" sense.

Oooo! Very nice. I cannot wait! ^_^

[NEGEV]

The new Glitter Module crashes everytime on my PC
Here is the crash report

************* Ausnahmetext **************
System.ArgumentOutOfRangeException: Der Index lag außerhalb des Bereichs. Er darf nicht negativ und kleiner als die Auflistung sein.
Parametername: index
bei System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
bei System.Collections.Generic.List`1.get_Item(Int32 index)
bei Tease_AI.Form1.Timer1_Tick(Object sender, EventArgs e) in C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease AI\Tease AI\Form1.vb:Zeile 4130.
bei System.Windows.Forms.Timer.OnTick(EventArgs e)
bei System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.79.0 built by: NETFXREL2.
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll.
----------------------------------------
Tease AI
Assembly-Version: 1.0.0.0.
Win32-Version: 1.0.0.0.
CodeBase: file:///E:/Teases/Tease%20AI/Tease%20AI/Tease%20AI.exe.
----------------------------------------
Microsoft.VisualBasic
Assembly-Version: 10.0.0.0.
Win32-Version: 14.6.79.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll.
----------------------------------------
System.Windows.Forms
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.79.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.79.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
System.Drawing
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.79.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
Accessibility
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.79.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll.
----------------------------------------
System.Runtime.Remoting
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.79.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll.
----------------------------------------
System.Speech
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.79.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Speech/v4.0_4.0.0.0__31bf3856ad364e35/System.Speech.dll.
----------------------------------------
AxInterop.WMPLib
Assembly-Version: 1.0.0.0.
Win32-Version: 1.0.0.0.
CodeBase: file:///E:/Teases/Tease%20AI/Tease%20AI/AxInterop.WMPLib.DLL.
----------------------------------------
Interop.WMPLib
Assembly-Version: 1.0.0.0.
Win32-Version: 1.0.0.0.
CodeBase: file:///E:/Teases/Tease%20AI/Tease%20AI/Interop.WMPLib.DLL.
----------------------------------------
mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.79.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.
----------------------------------------
System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.79.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------
System.Configuration
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.79.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.
----------------------------------------
System.Core
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.79.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll.
----------------------------------------
System.Xml
Assembly-Version: 4.0.0.0.
Win32-Version: 4.6.79.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.
----------------------------------------
Microsoft.GeneratedCode
Assembly-Version: 1.0.0.0.
Win32-Version: 4.6.79.0 built by: NETFXREL2.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.
----------------------------------------

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.

04:53 Tori: So I offered to let her come play with you this morning *grins at you*
04:54 Tori: You think you can handle that?
04:54 Malte: yes
04:54 Tori: I'm glad to hear that boy
Capri has joined the chat room
04:54 Tori: Because here she is right now
04:54 Tori: Hey Capri!
Capri is typing...