[Tease AI] Fury - New Tease AI Personality - Updated 3-5

[markus]

Hi!

Since Fury has it ups and downs for me, I wasn't sure when I should drop some feedback.
There were times when my feedback would have been 'Wooooooooooohooo, amazing', other times 'Booohh, boring'.
So I didn't want to give feedback too early.

Then reading GodDragon's last post just now, with some other criticisms about Fury in mind, one word/idea popped up in my head: 'Storymode'.
Please let me explain a little bit...

Some criticism was about that cycle (stroke, cbt/rest/edge,... and only sometimes a module), some ppl don't like it (what I can understand), but I can see the idea of it, and I like it a lot!
I have 'adopted' that idea to my personality (not MY, just a mix of mostly HoT, MissBlue, some other scripts and a handfull of own additions mixed together on my own).
What I did was writing one quite simple script which has only simple things in it (like the cycle in Fury) cbt/rest/edge, and copied it until I thought it's a good balance, now I have 346 files of that script mixed together with 204 pure module files.
Now a session feels like a completly new experience, while the modules are still the 'good, old' ones.
What I want to point out here is that this basic idea of yours to use more cycles and make more use of the technical given possibilities to create a random session is absolutly great,... other personalities were going the 'module-route' to create random experiences, but that becomes repetitive also after a while, you instead go for a new 'route' (shorter, but evolving modules), ... this is like fresh blood for TAI and it's scripts, and such fresh blood is totaly needed to push this whole TAI-thing further, please keep it up that way!

But, ... on the other hand, ... sometimes Fury get's to repeat itself,... that is when the risk is given that it get's old.

About the story-mode I have mentioned before,... I want to know what the story of Fury is lead me to, I am really curious what happens next, but I think I am not patient enough to go through all those sessions needed until I progess further in the story.
It could be like every time you start you have a 50/50 chance for a 'standard' session and a 'special' session,... but at least every second time you start up Fury it would give a 'special' session AKA story-evolution.
Sounds like an idea or sounds stupid?

Best greetings,
markus

[dmas964]

Let me know either way, and if it looks like we need to look at the issue further

I have flags:
C2_Active
C2_SetInitialPhase

[1885]

So she just made me do the do x strokes to pictures game twice in a session and the first time ended with 2,4k and the second was supposed to be 3k, even though the session duration was almost over. 3k is like 15 minutes at 200 BPM. That's insane and gets pretty boring really fast (like stroking for 15 minutes to pictures without any change) especially if done twice a session.

Yeah ever since I made the change to how Fury processes Modules, that's become a bit unbalanced. I've been testing Fury extensively these last few days, as I finished incorporating all the unofficial patches, which ended up being such a monumental change to the code in places that I want to make sure everything's running smoothly before I release the next build. Over this process, I've been refining not only how often these modules run, but tweaking the modules themselves to balance them for how much more likely they appear. There's a lot of stuff coming with the next patch, and I'll be hoping to address some of that

Some criticism was about that cycle (stroke, cbt/rest/edge,... and only sometimes a module), some ppl don't like it (what I can understand), but I can see the idea of it, and I like it a lot!

I like it too, because it always felt more like an actual session with a domme that way. I never had an online session with a domme where she was constantly playing games and presenting challenges and tasks or what not, it's always been a lot of stroking and edging, and occasionally a game or challenge. But I've kinda come to see that while Tease AI wears the skin of a chat session, at its core it functions like a webtease, so Fury isn't going to present the best experience when so much that she can do is hidden behind random die rolls that rarely hit. So for those people that want to have those experiences more often, I want the option to be there for that.

I'd also like her to function as that pure emulation of a domme, where it's a lot of stroking and edging, and occasionally she'll mix things up with a new game. I think having a settings menu within Fury itself, and giving people that level of flexibility will be a good idea

What I want to point out here is that this basic idea of yours to use more cycles and make more use of the technical given possibilities to create a random session is absolutly great,... other personalities were going the 'module-route' to create random experiences, but that becomes repetitive also after a while, you instead go for a new 'route' (shorter, but evolving modules), ... this is like fresh blood for TAI and it's scripts, and such fresh blood is totaly needed to push this whole TAI-thing further, please keep it up that way!

I definitely will. For all the coding and routines involved in building Fury, I'm still a storyteller at heart, and I love weaving in those narratives throughout Fury that unlock more things for Fury and the Contacts to use against the player. I may tweak some of those numbers as well though. Once Contact 2 is fully active, she has a 15% chance to start any given session. That may be too low, so I may have her chance build over time, so you don't end up with bad RNG and never get her to come back

About the story-mode I have mentioned before,... I want to know what the story of Fury is lead me to, I am really curious what happens next, but I think I am not patient enough to go through all those sessions needed until I progess further in the story.
It could be like every time you start you have a 50/50 chance for a 'standard' session and a 'special' session,... but at least every second time you start up Fury it would give a 'special' session AKA story-evolution.
Sounds like an idea or sounds stupid?

It's a good idea, I want people to be able to customize their experience with Fury just like they can with Tease AI itself. I've quite a lot of tweaks and additions already, but once I get the next patch I put out, I think I'll start creating that settings menu, and really try to give people some extensive customization options

I have flags:
C2_Active
C2_SetInitialPhase

You should be all set, it's just a matter of hitting the right die roll so you end up with a Contact 2 session. I'll be making some tweaks after the next patch to customize how often those things happen, but if you want to try to game the system a little to make her appear a little easier:

Spoiler: show

Fury will punish you if you leave a session early, but if you start a session and leave before she actually tells you to start stroking, it won't get counted against you. So you could technically start Fury, and if the domme shows up, just immediately exit and restart, and repeat that until you get Contact 2. Bear in mind, the way the scripts run now, you'll see the domme's image when you first start no matter what. But look and see who actually types, and if it's Contact 2, you're good to go

[GodDragon]

I'd also like her to function as that pure emulation of a domme, where it's a lot of stroking and edging, and occasionally she'll mix things up with a new game. I think having a settings menu within Fury itself, and giving people that level of flexibility will be a good idea

Hmm. While that might be true for online sessions because creativity is limited to some extend, rl sessions (not professional but sessions with a partner) for me have never been that heavily focused on pure stroking and edging. There was always as twist to it, a game, a challenge, bound body parts, other stimulation, tasks, rules, commands etc.
Like of course it might be a T&D session but it's more than just stroking to pictures. It's teasing with twists. Sudden hits, orgasm or denial can come at any time. Toys were used frequently too. So yea, maybe I am just more into the complicated stuff because I also like being on top sometimes and I also like to play with fire anyway. And sometimes it's not teasing at all and just pure breaking you or punishing you. And while the riding crop or whatever is a nice part there are many more things. I guess I also have experienced a lot and I need a certain creative dynamic in my relationships. An example for mostly pure T&D sessions is Liana Good on Pornhub. But she makes it incredibly interesting because he or she isn't just stroking most of the time. There are so many twists and challenges to her teasing that it is interesting because it's not just the same thing over and over again. And especially because it is no real human it gets even more boring than a teasing girl stroking you herself for the whole time. Fury has some variation to her and I like that but I think she might resemble a few dommes but I have defintely experienced different things.

Nice to hear that progress is going well!

[avatarbr]

I definitely will. For all the coding and routines involved in building Fury, I'm still a storyteller at heart, and I love weaving in those narratives throughout Fury that unlock more things for Fury and the Contacts to use against the player. I may tweak some of those numbers as well though. Once Contact 2 is fully active, she has a 15% chance to start any given session. That may be too low, so I may have her chance build over time, so you don't end up with bad RNG and never get her to come back

I start to implement some sort of "themes sessions" in HoT, and got that same problem: I want to have a small chance to start the theme, but I don't want something so small you rarely will see.

I had the same idea to increase the chances everytime a session don't get a theme.

default chance = 10%
After a session without a theme, chances increase to 15%.
2 sessions without, and the chances increase to 20%. All up to 80% (I don't want to know 100% a theme will show after x sessions, like I dont want to know a theme have 0% chances to show 2 times in a row).

I know when YOU created something is hard not be aware of what is happening, but if you forget it, can get some nice surprises.

[pastwarulez]

Hey, I just had some time to play around with Fury and noticed that you implemented

Spoiler: show

palming

. Thank you so much! The speed of your work on this is incredible!

[1885]

Hmm. While that might be true for online sessions because creativity is limited to some extend, rl sessions (not professional but sessions with a partner) for me have never been that heavily focused on pure stroking and edging. There was always as twist to it, a game, a challenge, bound body parts, other stimulation, tasks, rules, commands etc.

I can take some liberties with what you can do simulating an online session, since Fury will have more patience for intricate setups than a human might at any given moment, it's just a matter of thinking outside the box for me. I definitely want to build a procedural library of Tasks for Fury (that you would get at the end of a session to do before the next, or you could just log on and ask for some). That was always one of my favorite parts of online sessions, getting left with new instructions for the day and wondering how fucked up they were going to be this time

Sudden hits, orgasm or denial can come at any time.

That's something I've been working out as well, sudden and false endings, to keep that sense of suspense like you actually do have a chance to cum at any given moment regardless of the tease timer, without necessarily always disregarding the tease timer

Fury has some variation to her and I like that but I think she might resemble a few dommes but I have defintely experienced different things.

Fury will keep learning new tricks, and Contact 2 especially drastically changes things up in how she approaches things. I'm looking forward to every time I'm able to expand their repertoire, because I always end up having fun with the result

default chance = 10%
After a session without a theme, chances increase to 15%.
2 sessions without, and the chances increase to 20%. All up to 80% (I don't want to know 100% a theme will show after x sessions, like I dont want to know a theme have 0% chances to show 2 times in a row).

This is pretty much how I've handled Contact sessions for the next patch, so they shouldn't get buried under bad RNG rolls moving forward

Thank you so much! The speed of your work on this is incredible!

Hey, I appreciate it! I've been enjoying the work on Fury a lot, should have the next patch up pretty soon so she'll have a few new tricks as well

[1885]

Hey guys, major new update today available from the OP, just extract and overwrite as usual:

Patch Notes 2-14-2020

This build has undergone extensive changes to incorporate the changes made by markus in the Unofficial Patch, and swift69 in the Sweet Patch. These additions have been made with their permission and assistance, and I want to give a big thank you to both of them.

Additions from markus:

Rebuilt metronome for @Metronome commands
Gifs can be displayed with WMP now
@DommeNameTemp(X)
@DommeNameReset
@DommeAvatarTemp[X] and @DommeAvatarReset
Two dommes in one picture
Improved Random number generator
Improved Images loading from the Web (timeouts)
Pause for metronome, videos and audios
TAI will find also .mkv videofiles now
Focus on the Chat-Textbox
Script Log Generator
Video Log Generator
#CurrentHour
Bug in filter @DayOfWeek

For more information, please visit the Unofficial Patch thread here

Additions from swift69:

Automatic Domme Profile Picture - Added as "Generate Domme AV" under Interface menu
Always start with random Glitter - Added as "Random Contact" under Settings menustrip
@ShowDomRandomImage - Changed so that the random image is pulled from the domme's slideshow directory
@DomTagFirst and @ImageTagFirst
Improved #TagGarment , #TagUnderwear, #TagTatoo, #TagSexToy, #TagFurniture
Improved @SetDomme
Major fix for pictures loading and freezing
Improved Gif rendering
@PlayVideoNoWait
@StopVideo
@PlayAudioNoWait
@CheckPlayVideo
Improved @PlayVideo
New features for @JumpVideo
@JumpVideoUp and @JumpVideoDown
Features added for @PlayRedLightGreenLight and @PlayAvoidTheEdge
@Contact() can now contain multiple Contacts that will be randomly chosen to speak the line
Feature added for @CheckVideo
@MetronomeOn,@MetronomeUp,@MetronomeDown,@MetronomeOff, @Metronome()

For more information, please visit the Sweet Patch thread here

Added "Use WMP to Play Animated Gifs" option to Misc menu - If selected, Tease AI will use WMP to play gif files based on markus's code. If unchecked, gifs will be displayed using swift69's improved gif rendering. Either option will greatly improve the look of animated gifs.

Fixed bug that caused Emote images to not display correctly

Increased chance of starting each session with a Contact instead of a domme if the last session was a domme session

Lowered the amount of time that the "Boobs or Butts Til I Return" module can run

Certain modules are now limited to once per session

Latest Content Pack 2-14-2020

Edges to video clips now have their own module, and should be called more frequently

New module that incorporates the various @Metronome Commands. This module will not appear if the domme is set to never ruin your orgasm

___________________________________________

With this update, the official Tease AI build should be able to run any Personalities created up to this point that may rely on these unofficial patches. (If there are any unofficial patch creators I've overlooked, please let me know). I've tested and bugfixed this build extensively over the last week, but you never know how stable something really is until it's out in the wild, so please let know of any issues you may find. The new Commands have really been inspirational for new content ideas (I've got one new module based around them already in this build), so I'm definitely looking forward to using them to give Fury even more new tricks

[GodDragon]

Bug report for valentines day:
At the start it tells you it's your birthday because it says:
@NotFlag(ValentinesDayBypassFlag) @ValentinesDay @NullResponse @Goto(Sub Birthday Start) in the Start.txt file.
Fixed it myself. When she leaves for her ride however it "ends" the session but after that stroking sound kicks in and the session continues with her starting to post stroking taunts and then going back into the old cycle. I tried this twice and same result. Fixed the leave early thing for that so she won't punish me for it.

[1885]

Bug report for valentines day:
At the start it tells you it's your birthday because it says:
@NotFlag(ValentinesDayBypassFlag) @ValentinesDay @NullResponse @Goto(Sub Birthday Start) in the Start.txt file.

Thank you for reporting this, I have this fixed and replaced in the build in the OP. When I get a little more time tonight I'll take a look at the other issue and try to get a fix for that as well

[mangoman]

Ugh I missed the valentines day thing by an hour. Will it work if I change the clock on my PC so it's Friday the 14th again?

[1885]

When she leaves for her ride however it "ends" the session but after that stroking sound kicks in and the session continues with her starting to post stroking taunts and then going back into the old cycle. I tried this twice and same result. Fixed the leave early thing for that so she won't punish me for it.

This one was an ordeal to track down, but I finally managed to figure out what happened. I fixed this bug and updated the OP with the fixed build. Please let me know if you find any more errors

Ugh I missed the valentines day thing by an hour. Will it work if I change the clock on my PC so it's Friday the 14th again?

Haven't tested it, but I believe it should

[turpenti]

Just did a clean install of your new update. Adding DommeTags does not work:

Spoiler: show

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentException: The path is not of a legal form.
at System.IO.Path.LegacyNormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
at System.IO.Path.InternalGetDirectoryName(String path)
at Tease_AI.Form1.AddDommeTag(String AddDomTag, String AddCustomDomTag) in C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease-AI\Tease AI\Form1.vb:line 20601
at Tease_AI.Form1.SideView_Click(Object sender, EventArgs e) in C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease-AI\Tease AI\Form1.vb:line 20451
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
Tease AI
Assembly Version: 0.59.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Isand/Downloads/Tease%20AI%20Fury%202.14.2020.v3/Tease%20AI.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
metro
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Isand/Downloads/Tease%20AI%20Fury%202.14.2020.v3/metro.DLL
----------------------------------------
System.Speech
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
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:///C:/Users/Isand/Downloads/Tease%20AI%20Fury%202.14.2020.v3/AxInterop.WMPLib.DLL
----------------------------------------
Interop.WMPLib
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Users/Isand/Downloads/Tease%20AI%20Fury%202.14.2020.v3/Interop.WMPLib.DLL
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
Microsoft.GeneratedCode
Assembly Version: 1.0.0.0
Win32 Version: 4.8.3752.0 built by: NET48REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.mshtml
Assembly Version: 7.0.3300.0
Win32 Version: 7.0.3300.0
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.mshtml/7.0.3300.0__b03f5f7f11d50a3a/Microsoft.mshtml.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

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

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[1885]

Just did a clean install of your new update. Adding DommeTags does not work:

Just to help me narrow down the problem, are you trying to add Domme Tags through Settings->Tagging->Domme Tags, or Apps->Domme Tags?

After a couple of quick tests, I'm not replicating the crash through either method. I did notice that adding Domme Tags through Tagging->DommeTags is carrying over tags to the next image, so I'll need to look at that, but Apps->Domme Tags seems to be working normally.

Do you get the same result if you try both methods?

[turpenti]

I was adding them through DommeTags, but it seems to be working in the settings menu

It might work on your computer because it seems to be looking for a file where it would be on your PC.