I've kinda been keeping a low profile on the forum so I wanted to take the time and make a report on how things are going. Despite not being very active in the threads, I have been following them and keeping track of the bugs that have been reported. Some of them are already fixed for the next patch, but the more I work the more it becomes clear to me that I've reached a point I haven't exactly been looking forward to but knew would be necessary sooner or later
To paint a picture for those not coding-inclined, right now the guts of Tease AI is a haphazard mess of wires and bullshit that I lovingly consider a beautiful disaster. It's like an Indiana Jones boulder-sized mass of tangled Christmas lights that bowls over anyone who dares investigate the source code. That ball of Christmas lights needs to be untangled, and those frayed old strands from 1987 really need to fucking go. Basically I need to rip the guts out of Tease AI and replace them with cleaner and more streamlined wires.
There's far too much bloat in the code and in the UI that needs to be addressed. While I'm capable of tracking down and fixing most bugs that get reported, I've discovered that some things are slipping through the cracks in the nature of the code itself. So you would have instances such as Variable-related Commands not getting processed in Multiple Choice branches and stuff like that I never even realized was happening.
So I've already begun the process of streamlining everything, and I mean everything. The UI is getting streamlined, code is getting optimized and I've started going through each Command one by one in order to insure that they work properly, function to their complete potential and have a consistent usage. So far, every single Command I've gone through has been improved in some way. Which does bring me to a potential issue:
While I've been doing my best to improve Commands without affecting any current scripts, there's instances where Commands could be greatly improved if I did. I've only done this in one case so far, and that's with the @CheckFlag() Command. With the current build Patch 47 and below, you can only use one @CheckFlag() per line, but you can check for multiple flags by using commas - @CheckFlag(Flag1, Flag2, etc)
This has been changed in Patch 48. You can now use multiple @CheckFlag() Commands per line (a standard I'm trying to apply to all commands where applicable), but most importantly commas are no longer used to check for multiple Flags. Commas are now used to specify a specific line to go to. It now works like this (These examples assume that all flags being checked exist)
blah blah blah @CheckFlag(Flag1) This would go to (Flag1)
blah blah blah @CheckFlag(Flag1) @CheckFlag(Flag2) This would go to (Flag2)
blah blah blah @CheckFlag(Flag2) @CheckFlag(Flag1) This would go to (Flag1)
blah blah blah @CheckFlag(Flag1) @CheckFlag(Flag2, Domme Ruin Instructions) This would go to (Domme Ruin Instructions)
I made this change because there were too many instances where I wanted to check the same Flag in the same script, but it was useless being forced to go to (FlagName) in every case. Now you can specify a Flag, and then use a comma to specify an entirely different goto line. This change makes Flags much more versatile, but it comes at the cost of any scripts that use the multiple flag check from previous builds. I don't even know if any scripts do, I don't even know if mine do, but this will effectively break those scripts. They can be edited of course, but I'm not gonna start changing things around to a point where everything has to be edited constantly, only in cases like this where I feel the ends are definitely worth it to do so.
As I said, I don't plan on having to do this too much, I'm just curious of everyone's opinion about it.
But other than that, I'll be pretty busy for a while streamlining the code and the interface. I'm documenting everything's function and format as I go, so when I'm finished I'll be able to easily copy that over and provide somewhat of a guide for all Commands. It won't be as pretty as the last one, but it will be informative and up to date. My main concern is that the Commands start working for the scripters as much as possible, rather than the scripters having to get clever to do some basic things.
There won't be any patches while I'm getting all this stuff sorted. I'm not sure when exactly it will be before patches resume, just depends on how long it takes me to strip things down and piece them back together. My guess is probably not before October but easily before November. In any case, the bitbucket build will remain updated every step of the way, and at no point will the program be stripped out or unusable should anything happen and the bitbucket code need to be disseminated.
Please keep making suggestions, providing feedback and reporting bugs. Even if I don't answer for a while I'm still putting suggestions in place and getting bugs fixed. I'm just trying to manage my time with the program while not getting too overloaded, and I don't get a chance to respond to the forum as much as I'd like.
In one of the previous builds, the @Goto() Command was improved so you can now use it like this:CBT wrote:As to the percentages/chance thing. I assumed that there would be a 25% chance of one, and if not then a 25% chance of the next, and so on. Thats why I put the part about going throug the 4 video types again (domme couldnt decide thing), in case they all failed to be selected. I really need to get better with this code...lol. I think I will start with something a bit smaller/easier first.
@Goto(Femdom, General, JOI, Femsub)
In which case each of them would have an even 25% chance of getting called
If PtheV made an AI box with the Avoid The Edge scripts, when you opened them the program would let you save them as Filename_2.txt since they already existMat wrote:Is there a way to run both versions of ATE? It'd be nice if I didn't have to overwrite some of 1885's files, I made a backup just in case though.
Thank you, I really appreciate itPtheV wrote:This being my first post on here I'd like to start by adding to the choir of praise for 1885. You've really done a great job with Tease AI so far and it's getting better all the time! I used to visit Milovana only sporadically, now I find myself checking the forum regularly for updates.
You can do this with Flags to a certain extent already, but I'm working on things to make a lot of this easier and more powerful. Stayed tuned and there will be a lot of new stuff with documentation once Patch 48 does make it outPtheV wrote:I've been trying to do some scripting and I have a couple of questions/requests. Will the Domme at some point: 1) be able to remember what happened last session (i.e. that she could start a session by saying something like: Hey #SubName, last time we made a deal...etc.) Maybe with a kind of pre-session routine so that Tease AI can check if a particular start script should be called? And 2) be able to know how much time has passed since the last session (i.e. Domme: It's been X days since we made a deal...etc.)? One of my scripts has the Domme deny the user for a week with a guaranteed orgasm on day 7, if he does one session every day. With a combination of flags and variables I got it to work, but it's not very practical or elegant...
Patch 48 will have the option to disable them and change their rate, no worries. I just wanted to sneak it in there on everybodyavatarbr wrote: Azureballs wrote:
I found the secret feature! I think!
Spoiler:
Yes,
Spoiler:
It definitely works. And don't forget, you can also copy paste your AI Boxes as text (in a spoiler tag preferably), and people can open the boxes that way as well using Open From Text after copying the text into the text field in the AI Box app, so ity would be like this:avatarbr wrote:Let me see if I understand the AI Box.
In this file, I put:
1 Module
1 Custom Task (2 files)
1 Vocabulary
Let me know if it works.
- Spoiler: show
Thanks for catching it, I've made a note of itdjord wrote:04:55 PM Bryci: 3
04:55 PM djord: please punish me
04:55 PM Bryci: If you want to be punished so bad I'm not gonna stop you djord . Get to the edge Try not to think about how close you just were
04:56 PM Bryci: Get that horny cock on the edge
[quote"CXZman"]Have a question, not just for 1885, but also to the community around Tease AI. Since now the software actually handles content packages (AI Boxes), is there any initiative or forum thread that tries to centralize and map the Box world so that we could share and exchange tipsand tricks about scripting ?[/quote]
Not at the moment, but I imagine once Patch 48 gets released with the up to date documentation there's gonna be more a need for one. I'm still holding out hope for Tease AI to get its own forum, but I don't know how long any final word on that will be.
)
