Triple Alfa wrote:Hey 1885! It's great to have you back with us again.

Now that you're back I can pick some of my work back up. Assuming I can find the time and inspiration.
Either way, welcome back.
Thanks man, it's good to see you again
If you've got the time and inspiration to do anything, always happy to work with you. I'm going try to catch up with you as soon as I really get a chance, I hope you've been doing good
genome231 wrote:One question regarding the @Increase(Orgasm/Ruin)Chance + the @Decrease.
Are the changes these make permanent or temporary, like they only effect the current session with TeaseAI?
Hoping for temporary :P
They're permanent, but I can try to get you some temp ones in there
SkyHimeros wrote:Using one RandomText per line works fine. When I use more than one, the first one works too, but with every other one, the program shows everything in the brackets including the ")", except for whatever the first word was. So for example "@RandomText(if Random-Text works, if Random-Text does work)" becomes: "Random Text works, if Random Text does work)". Everything except "(if" is shown. And for some reason it erases the "-", but that's not really that big a problem.
I gotcha. A lot of times I just don't think about multiple instances per line when I'm coding Commands, so I always end up having to go back and do this

I'll fix @RandomText() in the patch so you can use more than one per line.
SkyHimeros wrote:Regarding StrokeTaunts I also have a question (doesn't have anything to do with the bug): How does TeaseAI choose from StrokeTaunts_1, StrokeTaunts_2 and StrokeTaunts_3? Are all the taunts thrown into a "pool" and then randomly selected? Or is every file called at a 33% chance. It would be important for me to know, because I want to make the taunts more diverse by using lots of RandomText-, MiniScript, FollowUpXX- and ResponseYes/No-Commands. For now I want to focus on using mostly StrokeTaunts_1 for that. If I only have a couple of taunts in StrokeTaunts_2 and StrokeTaunts_3, could that mean that they get shown disproportionately often?
Okay good news and bad news here, although the good may be exactly what you're looking for.
The way StrokeTaunts works is like this. When the program is getting a new Taunt, first there's a 45% chance that it's a one-line Taunt. If if doesn't hit that 45%, then it moves on to 33% chance of 1 line, 33% chance of 2 line, 33% chance of 3 line. So if you had StrokeTaunts_2 and StrokeTaunts_3 with only a couple of Taunts, you would hit them a disproportionate number of times, yes. That's the bad news.
The good news though, is that the code isn't checking for the files themselves, it's checking for the numbers after "StrokeTaunts_", and puts those numbers in an even pool. So if you take StrokeTaunts_2.txt and StrokeTaunts_3.txt just completely out of the Stroke folder, then the program will still work fine, it will just call StrokeTaunts_1 100% of the time. So if that's what you are actually looking to do, that's the way to go. (For what it's worth, you could write out as many StrokeTaunts_ files as you wanted (_4.txt, _5.txt, etc) as long as each of them contined Taunts that were 4 lines a piece, 5 lines a piece, etc. I just never saw the need to go above _3.)
genome231 wrote:The command list within TEASE-AI 49+50 <-- GREAT JOB!
Just 1 request that I think would increase its useability. Would it be possible to have the commands categorized?
Like [Video commands], [Picture commands], [Edge commands], etc. Hope you get what I mean.
I think I'm just about good to go with getting the new github set up, so if anybody wanted to tackle a better Command Guide, I'll help them any way I can. I'm actually going through a list of all the Commands now for Stefaf's work with the Auditing Scripts feature, so up to date information will be available.
I'd love to have a more organized system in place for the Command Guide, but it's not something I can prioritize with my own workload at the moment. I'll be doing good just to get it updated, which is definitely something I don't need to slack on
