Re: Tease AI Open Beta
Posted: Fri Feb 05, 2016 5:51 pm
Best of luck to the rewrite team!
This is actually already doable with the current TeaseAi (even if it is a bit clumsy to set up).Mat wrote: [*]Better task implementation, so the domme remebers what she asked you to do and asks if you did them
I believe Notay was thinking of making a script converter, which should cut out most of the work..Daragorn wrote:No way in hell i will ever go and rewrite all of them to work with the new program....it would take weeks/months of work....and it would end in me keeping using teaseAI despite of the potentially better new version, just to avoid having to spend months rewriting all scripts (and i bet most of us would not rewrite all their modules from scratch)
Yes I am worried about having too many symbols, having a single symbol is probably the way to go, it means more typing but I think it is clearer.Mat wrote:But anyway, I would say to be careful of making the scripting overly complicated, having to use symbols to denote things means a scripter will have to learn what each symbol is for, so I'd maybe change it to be something like:
$ is #Script(script)
% is #List(item1, item2, item3)
@ is #PrintVar(var) and #PrintVar(var + 10) could still work
_ is #tmp_varName
_local is #local_varName
Basically have the # mean that it runs things through the program rather than output as text.. if that makes sense.
I don't mind at all. Lets try adding requests to the issue tracker then people can see other requests and provide input all in one place.Mat wrote:I hope you don't mind my input on the scripting, I just thought it could be a way to make it easier for scripters and to make reading through them easier.
Secondly, is there somewhere to add feature requests, I keep coming up with ideas on things that could have been improved from 1885's Tease AI.
Having the ability to split videos(or crop images) is a good idea. That changes some of how I was thinking of implementing it, witch is good.Mat wrote:Rather than a directory for short CH vids, you could have a file with the file path, round start and round end. That way the domme could play your favourite rounds without you needing to split the videos
The whole media system needs a redesign, I plan to write up some of my thoughts at some point.Mat wrote:* Multiple folder paths for local images categories
* Multiple URL files for online categories
* Possible support for reddit threads as well as URL Images
This is actually a security issue with how the current chat system is implemented. But yes that's a good feature that needs some thought to be implemented properly.Mat wrote:URL's in chat, although the user should still have to click something, that way scripters could potentially incorporate flash games into the program, without needing hard coded stuff
Not sure how many I will make, but I do plan on making a fairly simple system for other coders to make games.Mat wrote:Will you be implementing the games like "censorship sucks", or the slots/memory games.
That was part of the discussion about a rewrite vs a overhaul. A rewrite would basically be Tease AI 47/48 plus stability. A overhaul would be a complete redesign of the whole program, with the idea being making it simpler for new users and scripters, and better stability/speed/future additions.Daragorn wrote:i'd suggest people working on it to try to keep the module writing part as close as the current teaseAI for retrocompatibility (apart for new/modified functionalities obviously).
Writing scripts with TeaseAI is not that difficult, imho, it just takes a bit of practice...it seems more complicated than it is because it lacks a wiki/repository to learn it, but once you get the grasps, it is pretty straightofrward.
I don't know if we want to use the builtin settings system, sense there is no good way to control where they get saved to. (would be nice if it could be 100% portable.)kree wrote:Thanks for putting it on Github!
I pulled NotayStart and started on the settings part, adding most of the settings and separated by tabs (General, Domme, Sub etc.). Skipping some settings less related to teasing for now, like Domm typing style and font settings.
Hope my contribution is okay, first version of it should be ready in a few days.
Are you talking about Responses or Vocabulary? From what I can tell # is used for general vocabulary not responses.Mat wrote:It might be best to change the # something else with the old response files using it, I'm not sure how you were handling responses though..
Then in "Vocabulary\#Gonna.txt" and "Vocabulary\#Grin" is a list of possible ways to respond.Modules\AssOrTitsMan.txt wrote:I'm #Gonna remember that #SubName #Grin
I'm #print(List.Gonna) remember that #print(SubName) #print(List.Grin)
To summarize, each flag must have its own @CheckFlag, as the comma now denotes a go-to point. @CheckFlag(flag1, flag2) from 47 now becomes @CheckFlag(flag1) @CheckFlag(flag2) or the script will skip over it.The @CheckFlag() Command checks to see if a Flag has previously been created by @SetFlag or @TempFlag, and goes to the appropriate line if it has.
If you use @CheckFlag() with just the name of the flag itself, such as @CheckFlag(FlagName) , then Tease AI will move to the line (FlagName) if that Flag exists.
However, you can also specify a line to go to if that Flag is found by using a comma, such as @CheckFlag(FlagName, Domme Instructions).
In this case, Tease AI would move to the line (Domme Instructions) if the Flag "FlagName" exists.
You can use as many @CheckFlag() Commands per line that you wish.
When specifiying a line to go to in a @CheckFlag Command, never put it in its own parentheses (For example, @CheckFlag(FlagName, Domme Instructions) is correct, @CheckFlag(FlagName, (Domme Instructions)) is incorrect.
I could contribute a settings manager I am writing as part of a personal framework I use in many of my projects. It basically serializes a class which acts as a data holder. That way you have full control and type-safety where what gets saved. If you want to have a look at it @kree (or anyone else :D) I am currently doing some work on it but will be done probably today; just PM me.Notay wrote:I don't know if we want to use the builtin settings system, sense there is no good way to control where they get saved to. (would be nice if it could be 100% portable.)kree wrote: Thanks for putting it on Github!
I pulled NotayStart and started on the settings part, adding most of the settings and separated by tabs (General, Domme, Sub etc.). Skipping some settings less related to teasing for now, like Domm typing style and font settings.
Hope my contribution is okay, first version of it should be ready in a few days.
Building the UI is good, I look forward to seeing it!
No problem but which version? 47 or 48? As both have their advantages and disadvantages atm.pepez wrote: Can someone upload own Tease AI folder where´s modules/scripts working :) NO pics or videos only modules/Scripts/Tags :) ..![]()
I hate it its everything i try ti do there is always same errors or some module doesn´t work etc...![]()
![]()
I´m not so good these codes/Programming etc... :/ + i´m so bad this english languange :)![]()
![]()
thank you again for all your wonderful work!!pepsifreak wrote:I think all the reported issues have been solved, so I'm going to leave this here.
I dont know.. which has more working modules :)q55x8x wrote:Notay wrote:No problem but which version? 47 or 48? As both have their advantages and disadvantages atm.pepez wrote: Can someone upload own Tease AI folder where´s modules/scripts working :) NO pics or videos only modules/Scripts/Tags :) ..![]()
I hate it its everything i try ti do there is always same errors or some module doesn´t work etc...![]()
![]()
I´m not so good these codes/Programming etc... :/ + i´m so bad this english languange :)![]()
![]()
Found a new bug.....the @SetDate() and @CheckDate() commands always give errors and crash the program....they were working fine in 48.2 (minor annoyance i know...i'll live them out for now but it would be nice to have back if possible :D)pepsifreak wrote: So please continue to report any issues you may come across and I will take a look when I can.
Ah those commands stripped out their closing bracket which was needed for one of the fixes I added. Seems to be working now :)Daragorn wrote:Found a new bug.....the @SetDate() and @CheckDate() commands always give errors and crash the program....they were working fine in 48.2 (minor annoyance i know...i'll live them out for now but it would be nice to have back if possible :D)pepsifreak wrote: So please continue to report any issues you may come across and I will take a look when I can.