[Tease AI] Sweet Patch 56.3.0

[FAddict]

I cant find a download link for the 56.12 version anywhere. I have problems with the 56.22 patch and would like to try the older one.

Can you tell me about your problem ? I guess I can still fix some bug if needed.

my problem is that after a few sessions with Miss Blue i am starting to get the Error Message:
A forced Event-Triggering in the BackGroundWorker was accomplished. Make sure to trigger the event, when you start the BackgroundWorker, with option manual Event-Triggering.

This happens 1 to 3 times each session and only with the Miss Blue personality. HoT works fine and without errors.

The Logs read this:

Errorlog.txt

Spoiler: show

###################################################################
Date/Time: 2020-07-29 11:48:35
Version: 0.56.22.0
Title: Forced-RunWorkerCompleted Trigger
Message: A forced Event-Triggering in the BackGroundWorker was accomplished. Make sure to trigger the event, when you start the BackgroundWorker, with option manual Event-Triggering.
Exceptions:
================================== Exception =====================================
Message: A forced Event-Triggering in the BackGroundWorker was accomplished. Make sure to trigger the event, when you start the BackgroundWorker, with option manual Event-Triggering.
Typ: System.TimeoutException
StackTrace:



~~~~~~~~~~~~~~~~~~~~Application.StackTrace~~~~~~~~~~~~~~~~~~~~~~~~~
bei Tease_AI.BackgroundWorkerSyncable.TriggerTimer_Tick(Object sender, EventArgs e) in W:\Tease\TeaseAIsource\Tease AI\Classes\BackgroundWorkerSyncable.vb:Zeile 37.
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)
bei System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
bei System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
bei System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
bei System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
bei System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
bei Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
bei Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
bei Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
bei Tease_AI.My.MyApplication.Main(String[] Args) in :Zeile 82.

log.txt

Spoiler: show

29.07.2020 11:48:30 TxtCache: Loading cached Text-File: F:\Games\Desktop\TeaseAI(NEW)\Scripts\MissBlue\Stroke\Start\StartScript.txt
29.07.2020 11:48:30 TxtCache: Loading cached Text-File: F:\Games\Desktop\TeaseAI(NEW)\Scripts\MissBlue\System\Variables\SYS_WakeUp
29.07.2020 11:48:31 TxtCache: Loading cached Text-File: F:\Games\Desktop\TeaseAI(NEW)\Scripts\MissBlue\System\Variables\SYS_WakeUp
29.07.2020 11:48:32 TxtCache: Loading cached Text-File: F:\Games\Desktop\TeaseAI(NEW)\Scripts\MissBlue\System\Variables\SYS_WakeUp
29.07.2020 11:48:33 TxtCache: Loading cached Text-File: F:\Games\Desktop\TeaseAI(NEW)\Scripts\MissBlue\System\Variables\SYS_WakeUp
29.07.2020 11:48:34 TxtCache: Loading cached Text-File: F:\Games\Desktop\TeaseAI(NEW)\Scripts\MissBlue\System\Variables\SYS_WakeUp
29.07.2020 11:48:35 TxtCache: Loading cached Text-File: F:\Games\Desktop\TeaseAI(NEW)\Scripts\MissBlue\Stroke\Start\StartScript.txt
29.07.2020 11:48:35 Exception occured: A forced Event-Triggering in the BackGroundWorker was accomplished. Make sure to trigger the event, when you start the BackgroundWorker, with option manual Event-Triggering.
29.07.2020 11:48:35 TxtCache: Loading cached Text-File: F:\Games\Desktop\TeaseAI(NEW)\Scripts\MissBlue\System\Variables\SYS_WakeUp
29.07.2020 11:48:36 TxtCache: Loading cached Text-File: F:\Games\Desktop\TeaseAI(NEW)\Scripts\MissBlue\System\Variables\SYS_WakeUp
29.07.2020 11:48:37 TxtCache: Loading cached Text-File: F:\Games\Desktop\TeaseAI(NEW)\Scripts\MissBlue\System\Variables\SYS_WakeUp
29.07.2020 11:48:38 TxtCache: Loading cached Text-File: F:\Games\Desktop\TeaseAI(NEW)\Scripts\MissBlue\System\Variables\SYS_WakeUp
29.07.2020 11:48:39 TxtCache: Loading cached Text-File: F:\Games\Desktop\TeaseAI(NEW)\Scripts\MissBlue\Stroke\Start\StartScript.txt
29.07.2020 11:48:39 TxtCache: Loading cached Text-File: F:\Games\Desktop\TeaseAI(NEW)\Scripts\MissBlue\System\Variables\SYS_WakeUp

Chat:

Spoiler: show

11:42 Name: Hello Mistress
Miss Blue version 2.07
Connecting... please wait...
Ready
11:42 Katherine: Good morning Name
11:42 Katherine: Back so soon, pet?
11:43 Katherine: Maybe you should allow yourself some time to regain your strength
11:43 Name: good morning
11:43 Katherine: Too much torture and that cock of mine might break...
11:43 Katherine: Do you really want to continue this session?
11:43 Name: Yes Mistress
11:43 Katherine: Well... game on then *grins*
11:43 Katherine: I do enjoy seeing you so eager for more
11:43 Name: can i tell you something?
11:43 Katherine: Start stroking that dick for me Name
11:44 Name: i dont want to cum
11:44 Katherine: Breasts are seen as a symbol of nourishment
11:44 Katherine: I'll keep that in mind, Name
11:45 Katherine: Stroke it like you're fucking Rachel again
11:45 Katherine: Like your hand is the inside of her pussy... try to remember what it was like to be inside her...
11:46 Katherine: You're not here to worship this body with your tongue slave
11:46 Katherine: So you're just gonna have to worship it with your strokes *wicked grin*
11:47 Katherine: Don't stop stroking that beautiful cock
11:47 Name: youre hot
11:47 Katherine: Thank you, Name *giggles*
ERROR: A forced Event-Triggering in the BackGroundWorker was accomplished. Make sure to trigger the event, when you start the BackgroundWorker, with option manual Event-Triggering.
11:48 Katherine: You're lucky I even let you masturbate at all, Name
11:49 Name: Let me speed up
11:49 Katherine: This is the warm up slave, I think you need to stay stroking just as you are
11:50 Katherine: I adore this outfit
11:57 Name: your outfit is beautiful
11:57 Katherine: Amazing how just the sight of me turns you into a drooling idiot hehe
11:57 Katherine: It's so easy to masturbate
11:57 Katherine: It comes so naturally to you...
11:57 Katherine: The motion of your hand sliding up and down that shaft
11:57 Katherine: This must be your ultimate safe space
11:57 Katherine: When you gaze at me or some porn, the world just fades away
11:58 Katherine: Your only focus is on how good that cock feels in your hand
11:58 Katherine: Have you noticed how being focussed on that cock and on me have become the same thing?
11:58 Katherine: After all, I tell you when you can stroke your cock and when to stop
11:58 Katherine: You have to concentrate on what I'm saying while that hand moves up and down
11:58 Katherine: Because if you didn't, you might miss a command
11:58 Katherine: And you want to make sure that don't miss a single thing I say
11:58 Katherine: How can you obey my commands if you don't know the command, right?
11:58 Katherine: Don't lose your focus, sexy
11:59 Katherine: A top stroking
11:59 Katherine: *Stop
11:59 Katherine: It's funny how things go, Name

Any help would be much appreciated because i like Miss Blue the most.

[swit69]

my problem is that after a few sessions with Miss Blue i am starting to get the Error Message:
A forced Event-Triggering in the BackGroundWorker was accomplished. Make sure to trigger the event, when you start the BackgroundWorker, with option manual Event-Triggering.

This happens 1 to 3 times each session and only with the Miss Blue personality. HoT works fine and without errors.

Your bug isn't easy to understand and make it happen. I don't have this one with my version.

By the way, I've worked on a new version which fixes some bugs. I'm going to release it soon. Maybe it will fix your issue.

[swit69]

By the way, I've worked on a new version which fixes some bugs. I'm going to release it soon. Maybe it will fix your issue.

Here it is : sweet patch 56.23 .

You can download it , just let me know if you still have your bug

Also in this version :
- Some bug fixes
- Some new commands for scripting (@PauseVideo, @UnpauseVideo ,@JumpAudio....

I will talk about these new commands later. but I've add one I like much who makes TAI counts the strokes (it counts the metronome ticks) . Imo , it's very convenient ! :) . I haven't updated the main post for now => the download link is just here for testing now.

NB : This version is still compatible with Miss Blue 2.07

[leezer3]

Here it is : sweet patch 56.23 .

You can download it , just let me know if you still have your bug

Also in this version :
- Some bug fixes
- Some new commands for scripting (@PauseVideo, @UnpauseVideo ,@JumpAudio....

I will talk about these new commands later. but I've add one I like much who makes TAI counts the strokes (it counts the metronome ticks) . Imo , it's very convenient ! :) . I haven't updated the main post for now => the download link is just here for testing now.

NB : This version is still compatible with Miss Blue 2.07

Gets stuck at the start of stroking, complains that the Min is greater than the Max in a Random statement.
No source, so I haven't bothered to debug properly, but it looks to me as if it's probably the metronome speed randomisation from the last called script lines.

[swit69]

Gets stuck at the start of stroking, complains that the Min is greater than the Max in a Random statement.
No source, so I haven't bothered to debug properly, but it looks to me as if it's probably the metronome speed randomisation from the last called script lines.

Ok thx for feedback

I think I can solve this issue easily

To get going through this problem before my fix, I think you should pick a higher number for the min value of the metronome speed (or a smaller number for the max if possible)

[swit69]

Gets stuck at the start of stroking, complains that the Min is greater than the Max in a Random statement.
No source, so I haven't bothered to debug properly, but it looks to me as if it's probably the metronome speed randomisation from the last called script lines.

Ok thx for feedback

I think I can solve this issue easily

Here is a new patch 56.24. I guess it solves the problem. Just let me know.

NB : 56.23 is no more available

[Zoran]

Hi!
First of all, let me thank you for your work, and continued support of this software!
It's thanks to people like you that such tools can continue to thrive :)

Now, I would have a small question/request if possible.
Lately I started writing some files for a new personality. One of the functions I wanted to implement was the program, choosing a random hour from the given pool and setting it as the time for the next session.

For example:
The domme asks you, at what hours are you available for a session. You tell her that you are free between, let's say 20:00 and 24:00. The program then proceeds to choose a random hour (could be just the whole hour, could be hour with minutes) between 20 and 24 and writes that time to a variable, much like @SetDate does. You can later call a check on that time, to see if the current hour is higher than the one in the variable, much like @CheckDate does.

Here is the problem: From what I gather, the program only works on time intervals in relation to current time and date. What I mean is that, I can't choose a specific date and time, I can only mark a date as [X minutes/hours/days etc. from this moment]. So I can tell the program "Mark a date 3 days from now", but I can't tell it to "Set a mark on 12th of September at 01:00". I tried doing this using #CurrentTime as variable, but AFAIU (I am not a programmer) that is being written as a string, not an integer, so I can't for example write a code that says "If the current hour is between 01:00 and 02:00, do X", only "If the current hour is exactly 01:00, then do X". Considering #CurrentTime uses a 12-hour clock with 60 minutes each, I would have to write 720 lines of code, just to inform the program that I want something done at a specific time. Similarly, I can't for example add +2 hours to a written time variable, as in "Take variable [A]=[15:00] and add +[02:00] to make it [A]=[17:00]".

So here's my question/request: Would it be possible to implement a separate set of commands that mark down current hour, minute, day, month and I guess year (though year can be currently bypassed using #CurrentYear, as that's just a numerical value, so it's not necessary) as separate integer variables, not as a conjoined date? Making a separate @SetTime and @CheckTime for hour/minutes only as well as @SetDate and @CheckDate for day and month only (i.e. making @SetDate a) read and write current date as integer value (so the same as the current one, except with no hours) and b) be able to mark specific day and month, not just a time period counting from the moment the command was used) would also be nice (but as long as I can output current month, day, hour and minute as a numerical value I think I can manage without it - though having an option to output time as e.g. [1700] instead of [17] and [00] would definitely lower the workload). And just to add to this, to make the internal clock optional between 12hr clock and 24hr clock, as 12hr clock kind of limits your options.

Sorry if it's too much.

[markus]

@ swit69:
I hope you don't mind if I answer here in your thread!

You tell her that you are free between, let's say 20:00 and 24:00. The program then proceeds to choose a random hour

That is why I've implemented #CurrentHour in the unofficial patch, should also be in the Fury patch, ... if swit69 does not have it implemented yet, this is done in a minute.
But a #CurrentMinute isn't there yet, ... will add it.

Usage:

Code: Select all

@NullResponse @If[#CurrentHour]==[TheHourToBeHere]Then(theStartIsHere)

Or:

Code: Select all

Type the early hour of the day! @InputVar[earlyHour]
Type the late hour of the day! @InputVar[lateHour]
@NullResponse @RapidCodeOn @If[#CurrentHour]>=[earlyHour]And[#CurrentHour]<[lateHour]Then(theStartIsHere)
(NotInTime)
You are not supposed to be here @EndTease
@End
(theStartIsHere)
Good, you've made it in time...
...

Or (here is the random hour included):

Code: Select all

Type the early hour of the day! @InputVar[earlyHour]
Type the late hour of the day! @InputVar[lateHour]
@NullResponse @RapidCodeOn @SetVar[YourRandomHour]=[#Random(#Var[earlyHour],#Var[lateHour])]
@NullResponse @If[#CurrentHour]>=[YourRandomHour]And[#CurrentHour]<=[YourRandomHour]Then(theStartIsHere)
(NotInTime)
You are not supposed to be here @EndTease
@End
(theStartIsHere)
Good, you've made it in time...
...

From what I gather, the program only works on time intervals in relation to current time and date. What I mean is that, I can't choose a specific date and time,

I will add #CurrentDayOfMonth and #CurrentMonthOfYear and a @SetSpecificDate in my next patch as well, thanks for your input!

And just to add to this, to make the internal clock optional between 12hr clock and 24hr clock, as 12hr clock kind of limits your options.

The clock that is displayed in TAI on the left side has nothing to do with how dates are handled, internal it's using a 24 hour system.

Best Greetings,
Markus

[Zoran]

@markus
Thanks for your reply!

I either don't have your patch (honestly, it's been years since I've installed TAI, at this point I don't remember which patch I have or have not installed >_<) or you must have not added the commands documentation to the command guide (not a criticism, mind you, just stating my observations), as I've spent the last few days, looking through them and I haven't seen the #CurrentHour. Will check it immediately!

In my defence I will say that I used MissBlue exclusively up until now, so I must have missed some of this functionality you've mentioned.

I know that the @SetDate uses 24 hour clock, I just tested #CurrentTime and saw it uses the application's 12hr one, this is why I wanted an option to output current time in 24hr setting. If #CurrentHour uses a 24hr clock, then I am pretty much set, as this was the main problem I was facing. Will still gladly accept the month/day functions, as they can definitely help me set specific dates for orgasm control and such.

Hope I didn't make too much of a mess posting this then. Thank you again!

EDIT: OK, the problem was - as you might have deduced from what I said earlier - that I was using the old version, apparently.
I did download the Fury version of TeaseAI previously, but after briefly skimming through the first session files, I decided that it's not really my cup of tea, so I deleted the entire zip file, without checking for any new functionality inside the software. My bad. I understand that for any follow-up patches, I should check the Fury thread?

Thanks once more!

[markus]

or you must have not added the commands documentation to the command guide

Got me!

That command guide is absolutly not up to date,... I guess no one who works on patches worked on updating that,... not 1885 with his official Fury Patch (which has some new commands, not a sinle one is documented anywhere, not in that guide or anywhere else),...
At least you can find those additional commands which came with the sweet-patch in the first post of this thread, and mine are in the 'patch55_7_release_notes.txt' or also in the release thread of it.
So, if you want to have a complete overview, you might check these 3 resources.

Hope I didn't make too much of a mess posting this then.

This forum lacks in activity, ... it's a forum,... use it as such!
If you have questions, ask!
If you have something you wanna share, share!
If you are in the need of a new command for TAI, describe it, and we will see what we can do!

Best greetings,
Markus

[Zoran]

Sure

You know, I am from the, whatchacallit, old school of forum users and netiquette. So I am used to mods being angry about stuff like constant spelling errors, double posting, posting multiple threads regarding the same topic, off-topic posting, useless posting (e.g. threads which by their very nature warrant little more than a single reply) and so on and so forth, so I can be a little twitchy when it comes to making a mess on any forums.

Will surely check all those!
Thanks for the help again, will look out for those addons you promised ;)

[sexybastardo]

Hello
After years I found my way back here and I'm glad to see that Tease AI still exists.
Just tried your Sweet Patch 56.24 and I must say its really great! You did a great job. Especially the video function, that's something I wanted to have way back when I was using Tease AI a lot.

But I found a small problem, I noticed that TA crashes every time if I activate the honorific settings before I say Hello.
Is it possible to get a fix for this?

EDIT: The crashes are gone after I deleted my very old setting file and reconfigured TeaseAI, seems to be sth old in the xml file.

Best,
sexybastardo

[fusiontermite]

That command guide is absolutly not up to date,... I guess no one who works on patches worked on updating that,... not 1885 with his official Fury Patch (which has some new commands, not a sinle one is documented anywhere, not in that guide or anywhere else),...
At least you can find those additional commands which came with the sweet-patch in the first post of this thread, and mine are in the 'patch55_7_release_notes.txt' or also in the release thread of it.
So, if you want to have a complete overview, you might check these 3 resources.

This forum lacks in activity, ... it's a forum,... use it as such!

If you are in the need of a new command for TAI, describe it, and we will see what we can do!

You are speaking (writing) a lot of truth here...

In my opinion, the lack of a comprehensive list with all commands is one of the reasons for the inactivity in this forum (also compared to other forums on Milovana).

In my view, what needs to be done is the following:

1. create a version of TAI that includes all features and commands from the unofficial patches and the Sweet Patch

I'm not sure, if the newest version by 1885 already includes all features and commands from these versions. If it does not, having ONE version of TAI that supports ALL scripts and personalities is the top priority if we want to avoid people spending their time on scripts that are not compatible with each other. There should be one version "to rule them all".

2. create a documentation on how to write scripts for TAI

This includes having a list of all commands, command filters and system keywords. There should be both an alphabetic list (or a search function) and a list/explanation on how to use commands based on topics, so that all commands relating to e.g. edging, stroking, showing pictures and slideshows, variables (e.g. @SetVar, @ChangeVar, @ShowVar, @Variable, #Var) etc. are grouped together. Ideally, the Command Guide would be an online database that allows entrys to be changed and provides the possibility to comment and ask questions.

What is also important is that some commands can have multiple arguments, i.e. different forms. The guide should show all ways of using the existing commands so that users really see what is already possible with TAI (because TAI can do a lot of things, but many users don't know about it or don't know how to use it). Also see: viewtopic.php?p=286550#p286550

3. give users more possibilities by adding new features and eliminating restrictions

I have many suggestions for new features and I am planning on bringing them up here in the future.

4. coordinate future development

Coordination can take place on all levels of development. Of course, having coordination between those people who further develop TAI is key in order to avoid having incompatible version. But it doesn't have to end there. There are many talented and interesting people on this platform and we all have different strenghts. Some may have really good (general) ideas on what the domme could do, but don't know how to implement them (e.g. because they are not native English speakers and don't know how to phrase it). Some may be really good with languages, but may lack ideas. Some people know how to scripts efficiently and without causing TeaseAI to break down. Possible roles include programmer, script writer, domme lines writer, idea-giver, english-checker, tester.

For example, there could be a thread where people can post domme lines and have them checked for spelling and grammar. Another thread could be for people to come up with domme lines: viewtopic.php?f=26&t=19540&start=15

Conclusions

I think that there are many people here who have good ideas and would also like to write and share scripts. Therefore, the goal should be to make writing scripts as easy as possible, so that everyone can benefit from it. Not having a rule-them-all-version of TAI and an include-them-all documentation is probably one of the main obstacles that keeps people from contributing. That means that steps 1 and 2 are the most important ones and the basis for future development.

[meaculpa_uk]

You are speaking (writing) a lot of truth here...

In my opinion, the lack of a comprehensive list with all commands is one of the reasons for the inactivity in this forum (also compared to other forums on Milovana).

In my view, what needs to be done is the following:

1. create a version of TAI that includes all features and commands from the unofficial patches and the Sweet Patch

I'm not sure, if the newest version by 1885 already includes all features and commands from these versions. If it does not, having ONE version of TAI that supports ALL scripts and personalities is the top priority if we want to avoid people spending their time on scripts that are not compatible with each other. There should be one version "to rule them all".

2. create a documentation on how to write scripts for TAI

This includes having a list of all commands, command filters and system keywords. There should be both an alphabetic list (or a search function) and a list/explanation on how to use commands based on topics, so that all commands relating to e.g. edging, stroking, showing pictures and slideshows, variables (e.g. @SetVar, @ChangeVar, @ShowVar, @Variable, #Var) etc. are grouped together. Ideally, the Command Guide would be an online database that allows entrys to be changed and provides the possibility to comment and ask questions.

What is also important is that some commands can have multiple arguments, i.e. different forms. The guide should show all ways of using the existing commands so that users really see what is already possible with TAI (because TAI can do a lot of things, but many users don't know about it or don't know how to use it). Also see: viewtopic.php?p=286550#p286550

3. give users more possibilities by adding new features and eliminating restrictions

I have many suggestions for new features and I am planning on bringing them up here in the future.

4. coordinate future development

Coordination can take place on all levels of development. Of course, having coordination between those people who further develop TAI is key in order to avoid having incompatible version. But it doesn't have to end there. There are many talented and interesting people on this platform and we all have different strenghts. Some may have really good (general) ideas on what the domme could do, but don't know how to implement them (e.g. because they are not native English speakers and don't know how to phrase it). Some may be really good with languages, but may lack ideas. Some people know how to scripts efficiently and without causing TeaseAI to break down. Possible roles include programmer, script writer, domme lines writer, idea-giver, english-checker, tester.

For example, there could be a thread where people can post domme lines and have them checked for spelling and grammar. Another thread could be for people to come up with domme lines: viewtopic.php?f=26&t=19540&start=15

Conclusions

I think that there are many people here who have good ideas and would also like to write and share scripts. Therefore, the goal should be to make writing scripts as easy as possible, so that everyone can benefit from it. Not having a rule-them-all-version of TAI and an include-them-all documentation is probably one of the main obstacles that keeps people from contributing. That means that steps 1 and 2 are the most important ones and the basis for future development.

@fusiontermite

Excellent post!! I completely agree with you. I think another obstacle has been the development of TAI Java, which seems to be the natural successor to TAI, but is MUCH harder to write scripts for. Personally, I tried the Java version and I just don't like it.

Maybe start a new thread called "The future of TAI?" and copy paste this post to see what others think?

Mea

[swit69]

Spoiler: show

You are speaking (writing) a lot of truth here...

In my opinion, the lack of a comprehensive list with all commands is one of the reasons for the inactivity in this forum (also compared to other forums on Milovana).

In my view, what needs to be done is the following:

1. create a version of TAI that includes all features and commands from the unofficial patches and the Sweet Patch

I'm not sure, if the newest version by 1885 already includes all features and commands from these versions. If it does not, having ONE version of TAI that supports ALL scripts and personalities is the top priority if we want to avoid people spending their time on scripts that are not compatible with each other. There should be one version "to rule them all".

2. create a documentation on how to write scripts for TAI

This includes having a list of all commands, command filters and system keywords. There should be both an alphabetic list (or a search function) and a list/explanation on how to use commands based on topics, so that all commands relating to e.g. edging, stroking, showing pictures and slideshows, variables (e.g. @SetVar, @ChangeVar, @ShowVar, @Variable, #Var) etc. are grouped together. Ideally, the Command Guide would be an online database that allows entrys to be changed and provides the possibility to comment and ask questions.

What is also important is that some commands can have multiple arguments, i.e. different forms. The guide should show all ways of using the existing commands so that users really see what is already possible with TAI (because TAI can do a lot of things, but many users don't know about it or don't know how to use it). Also see: viewtopic.php?p=286550#p286550

3. give users more possibilities by adding new features and eliminating restrictions

I have many suggestions for new features and I am planning on bringing them up here in the future.

4. coordinate future development

Coordination can take place on all levels of development. Of course, having coordination between those people who further develop TAI is key in order to avoid having incompatible version. But it doesn't have to end there. There are many talented and interesting people on this platform and we all have different strenghts. Some may have really good (general) ideas on what the domme could do, but don't know how to implement them (e.g. because they are not native English speakers and don't know how to phrase it). Some may be really good with languages, but may lack ideas. Some people know how to scripts efficiently and without causing TeaseAI to break down. Possible roles include programmer, script writer, domme lines writer, idea-giver, english-checker, tester.

For example, there could be a thread where people can post domme lines and have them checked for spelling and grammar. Another thread could be for people to come up with domme lines: viewtopic.php?f=26&t=19540&start=15

Conclusions

I think that there are many people here who have good ideas and would also like to write and share scripts. Therefore, the goal should be to make writing scripts as easy as possible, so that everyone can benefit from it. Not having a rule-them-all-version of TAI and an include-them-all documentation is probably one of the main obstacles that keeps people from contributing. That means that steps 1 and 2 are the most important ones and the basis for future development.

These ideas are indeed good ones. But it takes some time to merge all the versions and document all the commands and filters.
Nonetheless, I think it could be not so hard to complete the command guide available in TAI. I can't promise anything but I'm going to look at it for a future version of Sweet Patch.