Page 103 of 175

Re: Tease AI Open Beta

Posted: Tue Mar 29, 2016 2:49 am
by Notay
pepsifreak is still updating 48.x, you can see changes on his GitHub page: https://github.com/pepsifreak/Tease-AI, he usually posts on this thread when he releases a new version.

Me, q55x8x and kree, are still working on the rewrite, you can see changes on GitHub https://github.com/TeaseAI/TeaseAI-CE. (I also put updates on my Patreon page.)

If you look at times of the commits on the GitHub pages, pepsifreak pushed changes 4 days ago and I pushed changes 2 days ago.

Re: Tease AI Open Beta

Posted: Tue Mar 29, 2016 3:14 pm
by genome231
Notay wrote:pepsifreak is still updating 48.x, you can see changes on his GitHub page: https://github.com/pepsifreak/Tease-AI, he usually posts on this thread when he releases a new version.

Me, q55x8x and kree, are still working on the rewrite, you can see changes on GitHub https://github.com/TeaseAI/TeaseAI-CE. (I also put updates on my Patreon page.)

If you look at times of the commits on the GitHub pages, pepsifreak pushed changes 4 days ago and I pushed changes 2 days ago.
Nice!
Lovely work guys!

Regards
Genome

Re: Tease AI Open Beta

Posted: Wed Mar 30, 2016 6:27 pm
by Sisyphuster
Cool Notay, thanks for the update and all your work!

Re: Tease AI Open Beta

Posted: Wed Apr 06, 2016 10:16 am
by genome231
Hey guys!

Would it be possible to have TEASE-AI upload something to a website or add that feature to the program?
Yes it would be used in my personality as a sort of blackmail.
I know sexscript had a similar tease, where if you didn't do as ordered or failed at something, the program would depending on the level of strictness, might upload a picture of you to a website.

Regards
Genome

Re: Tease AI Open Beta

Posted: Wed Apr 06, 2016 1:00 pm
by Mat
genome231 wrote:Hey guys!

Would it be possible to have TEASE-AI upload something to a website or add that feature to the program?
Yes it would be used in my personality as a sort of blackmail.
I know sexscript had a similar tease, where if you didn't do as ordered or failed at something, the program would depending on the level of strictness, might upload a picture of you to a website.

Regards
Genome
I think that might be going a bit far.. I suppose it depends on how it's implemented and what restrictions are in place to stop misuse of the upload feature.

I could be wrong but I think as well as coding an upload feature the devs would also have to add a server-side php script to receive the data as well.

Personally I'd prefer a blackmail script to delete images instead. I've got a few images I want to keep so there'd still be the motivation to do a task. I guess I like that way as it's still a form of blackmail but without the risk of exposure.

Edit:
I just thought that in addition to or instead of the image deletion, if a simple encryption algorithm was added, you could encrypt an image and use that as blackmail. Although again restrictions would have to be added to stop someone making a cryptolocker style virus/script and encrypting actually important files.

Also an encryption algorithm could be good for chastity devices with a combination lock, take a pic of the lock and have the domme encrypt it.

Re: Tease AI Open Beta

Posted: Thu Apr 07, 2016 8:39 am
by genome231
Mat wrote:
genome231 wrote:Hey guys!

Would it be possible to have TEASE-AI upload something to a website or add that feature to the program?
Yes it would be used in my personality as a sort of blackmail.
I know sexscript had a similar tease, where if you didn't do as ordered or failed at something, the program would depending on the level of strictness, might upload a picture of you to a website.

Regards
Genome
I think that might be going a bit far.. I suppose it depends on how it's implemented and what restrictions are in place to stop misuse of the upload feature.

I could be wrong but I think as well as coding an upload feature the devs would also have to add a server-side php script to receive the data as well.

Personally I'd prefer a blackmail script to delete images instead. I've got a few images I want to keep so there'd still be the motivation to do a task. I guess I like that way as it's still a form of blackmail but without the risk of exposure.

Edit:
I just thought that in addition to or instead of the image deletion, if a simple encryption algorithm was added, you could encrypt an image and use that as blackmail. Although again restrictions would have to be added to stop someone making a cryptolocker style virus/script and encrypting actually important files.

Also an encryption algorithm could be good for chastity devices with a combination lock, take a pic of the lock and have the domme encrypt it.
Hi I totally agree that "real" blackmail can quickly get out of hand!
I just thought it might be okay if it was sort of out in the open, like everyone can go and read into the scripts, see that it isn't dangerous, beyond the obvious :P. That being said! I had forgotten the delete image feature! :-D
An encryption algorithm would be awesome! :D

Re: Tease AI Open Beta

Posted: Thu Apr 07, 2016 5:54 pm
by mr-max
I'm into blackmail fantasies, but I dont think sending stuff out is the best idea. It is a fantasy after all (that'S why I never tried mandy or jennifer at sex scripts). BUT it would be good to have some more severe consequences. I for example set the hentai picture folder to my dommes folder, cause I dont give a heck about hentai and if it came to it I would bail out of anything cause the pictures dont interest me. With my dommes immages however it is a different thing. It took me a very long time to get them together and missing out some would be bad. Maybe we can find some other ideas that make you think twice if you reject the task. For example you could loose all advances in the script (like a reset). I would love to get something really bad that is contollable, but I have no idea what else would work ;)

Re: Tease AI Open Beta

Posted: Fri Apr 08, 2016 8:20 am
by 1885
Hey everyone.

First of all, please allow me to apologize for my latest absence. I would rather not get too deep in the explanations, but suffice it to say that it was caused by more of the same from last time. I had a series of stressful things to deal with over the last few months, and I suffer from severe anxiety and essentially zero coping skills. Tonight was the first time I've been able to bring myself to log onto Milo, and so far I've been able to catch up from here to where the three month cutoff began in January. I just want to say thank you for everyone's concern - as self-conscious as I am for causing it in the first place, and for everybody who did their part to keep Tease AI moving forward.

I haven't had a chance to check out any of the community versions, writing this is literally the first thing I'm doing after catching up on the thread. For my own end, I wasn't even able to work on Tease AI in private until about a month ago. When I picked it back up again, it was basically to see if I could still code it (well, as I ever could code anyway). I didn't have any difficulty getting back into it and I've basically been spending my free time trying to get back on my feet not only with the program but with my Total Brat personality. I've basically been working on them in tandem, adding code to suit my needs in order to make the experience more and more in line with what I would expect to find in a real session. I don't want to get into the details of all that right this moment, but since it may be relevant moving forward here's a (non-detailed) list of the patch notes I've kept since resuming work:
Spoiler: show
Added @MiniScript() Command

Tease AI now keeps track of where the user left the splitter between sessions

Added Interface to main menu strip. Added or relocated the following functions to "Interface": Switch Sides, Side Chat, Lazy Sub AV, Themese, Maximize Image and Webtease Mode

Added Commands @MoodBest and @MoodWorst

Added Commands @DecreaseOrgasmChance, @IncreaseOrgasmChance, @DecreaseRuinChance and @IncreaseRuinChance

Added options to the main picture right-click menu to go to the first image of the current domme slideshow, go to the last image of the current domme slideshow, and load a new random domme slideshow from the directory set in the General Settings tab

Fixed bug where #Keywords would return a "not found" error if adjacent to a ")"

Fixed bug where Next Image and Previous Image buttons were not always unlocked when @LockImages was disabled by system events rather than the @UnlockImages Command

Fixed major bug where the @ChanceXX Command was not processed correctly, resulting in chunks of the domme's dialogue and Commands being deleted before they could be parsed

Fixed bug where certain @Command() functions would break other @Command() functions in the same line. This includes @CheckFlag(), @SetFlag(), @TempFlag, @DeleteFlag(), @SetDate(), @CheckDate() and @DeleteVar[]

Added Command Filters @AssWorship, @BoobWorship and @PussyWorship

Added Commands @Worship() and @ClearWorship

Added Command Filters @LongHold and @ExtremeHold

Added Commands @LongHold, @LongHold(), @ExtremeHold and @ExtremeHold()

Added Sub Settings for Long Hold Min/Max and Extreme Hold Min/Max

Added Command Filters @SubWorshipping and @SubNotWorshipping

Added Commands @WorshipOn and @WorshipOff

Added Commands @FollowUp() and @FollowUpXX

Response Files will no longer include lines in the [All] category if the session has yet to enter the first Taunt Cycle, or the session has passed the orgasm decision.

Domme recognizes requests to have an orgasm through new keyphrases: "I cum", "me cum", "I have an orgasm", "me have an orgasm"

Added System Keywords #LocalImageCount, #HardcoreImageCount, #SoftcoreImageCount, #LesbianImageCount, #BlowjobImageCount, #FemdomImageCount, #LezdomImageCount, #HentaiImageCount, #GayImageCount, #MaledomImageCount, #CaptionsImageCount and #GeneralImageCount

Fixed bug with @DeleteLocalImage Command that caused the program to stop responding

Added @RestrictOrgasm() and @RestrictOrgasm Commands

"Domme is typing..." timer length is now capped at 6 seconds. This is to ensure that lines get delivered in a timely manner, even if they contain lengthy sets of Commands in the script.

Added @RandomText() Command

Added @SetModule() and @SetLink() Commands

Added @ResponseYes() and @ResponseNo() Commands

Added custom button options to Lazy Sub

Fixed bug that caused Tease AI to crash during videos when domme typed a new message

Improved Tease AI's parsing ability when matching Response Files
The main issue I've always had with coding is that I understand code on a basic level only. There's a lot of things going on that dictate how the software relates to the machine running it, and I usually just get a mind full of fuck when it comes to that stuff. This thread has produced a lot of people much more skilled than me in this area, and it looks like they've been able to fix things I would not have noticed or known how to at all.

So I would like to ask the community, and especially those working on unofficial patches or a CE re-write how they would like to move forward from here. I do still want to work on Tease AI, and I'm in a place where I'm able to, but I know there's other people here laying a new foundation that's much more solid than I could do on my own. Ideally I would like to find some way to integrate the work I've done in the last month with the work that's been going on here, but I'm not sure the best way to go about that. I'm not sure if I should just start pumping out patches again and let people integrate them into the more solid CE edition, I don't know if I should enlist help to get the parts of my own code smoothed out based on what's been done, I honestly don't know.

If we're able to reach a consensus, I'm pretty open to whatever options are out there. I'm going to keep working regardless, I would just prefer to work alongside any other work being done so we don't end up with multiple programs that parse things differently. I'm willing to keep coding, and I'm willing to keep improving. I just know that my strengths have always been in writing and content creation. My UI has steadily improved, my code has (marginally) improved, but where I've shined the most I think is with Total Brat. I want to keep moving in a direction that gets her to the completely fleshed out personality I've pictured in my head for so long.

So for everyone working on this, please give me your input on how you would like to move forward.

Again I want to apologize for anyone I've caused concern to, and say thank you to everyone who's kept this going. It really does mean a lot to me and I appreciate it greatly.

- 1885

Re: Tease AI Open Beta

Posted: Fri Apr 08, 2016 9:04 am
by Harry2stroke
Welcome back :wave:

Re: Tease AI Open Beta

Posted: Fri Apr 08, 2016 9:29 am
by schefflera
hey, welcome back 1885! :w00t:
I couldn't thank you for all your flashteases and the teaseAI so far. But now I can: Thank you. Your story's are the best!
1885 wrote:If we're able to reach a consensus, I'm pretty open to whatever options are out there. I'm going to keep working regardless, I would just prefer to work alongside any other work being done so we don't end up with multiple programs that parse things differently. I'm willing to keep coding, and I'm willing to keep improving. I just know that my strengths have always been in writing and content creation. My UI has steadily improved, my code has (marginally) improved, but where I've shined the most I think is with Total Brat. I want to keep moving in a direction that gets her to the completely fleshed out personality I've pictured in my head for so long.
I think it's the best working together, so there wont be different programs, as you said.

Re: Tease AI Open Beta

Posted: Fri Apr 08, 2016 10:35 am
by VanHellsing
Hey 1885, good to see you again! :wave:
1885 wrote:So I would like to ask the community, and especially those working on unofficial patches or a CE re-write how they would like to move forward from here. I do still want to work on Tease AI, and I'm in a place where I'm able to, but I know there's other people here laying a new foundation that's much more solid than I could do on my own. Ideally I would like to find some way to integrate the work I've done in the last month with the work that's been going on here, but I'm not sure the best way to go about that. I'm not sure if I should just start pumping out patches again and let people integrate them into the more solid CE edition, I don't know if I should enlist help to get the parts of my own code smoothed out based on what's been done, I honestly don't know.

If we're able to reach a consensus, I'm pretty open to whatever options are out there. I'm going to keep working regardless, I would just prefer to work alongside any other work being done so we don't end up with multiple programs that parse things differently. I'm willing to keep coding, and I'm willing to keep improving. I just know that my strengths have always been in writing and content creation. My UI has steadily improved, my code has (marginally) improved, but where I've shined the most I think is with Total Brat. I want to keep moving in a direction that gets her to the completely fleshed out personality I've pictured in my head for so long.
I'd say, work together, Notay's team is good at writing code, but I think not much have changed in the contet of Wicked personality. You say, you are good at writing scripts and content creation, so you fulfill each other. Basically, you have ideas, which Notay's team can implement without thinking hours or days about the way to write the code and I bet writing the code or repairing bugs all the time, inestead of focusing on what you really want to do (writing scripts, improving personalities) can burn out a person very fast. With such projects, working as a groups is always better than working alone, you can divide the work between people, as a group, you have more ideas, different points of view, development doesn't stop when one person burns out etc.

Re: Tease AI Open Beta

Posted: Fri Apr 08, 2016 5:27 pm
by CBT
Welcome back 1885!!! :yay: :mbounce: :happy2:
mr-max wrote:I'm into blackmail fantasies, but I dont think sending stuff out is the best idea. It is a fantasy after all (that'S why I never tried mandy or jennifer at sex scripts). BUT it would be good to have some more severe consequences. I for example set the hentai picture folder to my dommes folder, cause I dont give a heck about hentai and if it came to it I would bail out of anything cause the pictures dont interest me. With my dommes immages however it is a different thing. It took me a very long time to get them together and missing out some would be bad. Maybe we can find some other ideas that make you think twice if you reject the task. For example you could loose all advances in the script (like a reset). I would love to get something really bad that is contollable, but I have no idea what else would work ;)
What I think would be a good idea/consequence, would be to have a whole folder of images or possibly a large number of images deleted instead of one. I have about 12 different collections of images of my domme (diff outfits etc) and it would be a real threat if there was a possibility of losing one of the sets.

Re: Tease AI Open Beta

Posted: Fri Apr 08, 2016 9:09 pm
by CXZman
Welcome back 1885 ! Great news that you're still around. Sorry to hear last months were tough for you. Wish you the best !

Re: Tease AI Open Beta

Posted: Fri Apr 08, 2016 9:34 pm
by Lestat
Welcome back 1885 :smile:

I'm glad to see you back and wish you the best for your health and everything else in your life

Re: Tease AI Open Beta

Posted: Fri Apr 08, 2016 11:54 pm
by Notay
Welcome back! :-D

As far as integrating your changes, have a look at pepsifreak's 48.x updates. Using Git you may be able to create a fork and merge your changes with his. Although for stability reasons that's not likely the best option.

The rewrite code is completely different, and still has a ways to go before it is close to 47. Id recommend waiting until the code is more mature, right now it's mostly just the scripting foundation, no tease specific stuff.
The past few weeks I have been redesigning the variable system in the rewrite, so we don't need as many functions to do simple things. For example getting the hour form a date variable. "@self.myvar.hour" instead of "@hour(self.myvar)"