Code: Select all
@RandomText(Cum for me, Hurry and cum for me, I want you to explode, Give me that cum, I want all that cum, Cum for me #SubName, Give me that cum #SubName, I want that cum #PetName, Make it feel so good for me) @Wait(20) @Goto(Allow Cum Loop)Code: Select all
@RandomText(Cum for me! @Goto(SecondOrgasm), I want you to hurry up and cum! @Chance40(OrgasmTorture))You can't use Commands that use parentheses such as @Goto() or @ChanceXX(), but you can use anything else (#Keywords, @Commands without () like @ShowBlogImage and bracketed Commands like @ShowImage[])genome231 wrote:Is it possible to add @Commands within @RandomText?
I imagine it would look something like this:
That example wouldn't work. If I had to do the exact thing as the above example, I would do it like thisgenome231 wrote:@RandomText(Cum for me! @Goto(SecondOrgasm), I want you to hurry up and cum! @Chance40(OrgasmTorture))
Do the old commands (@SometimesAllowOrgasm, etc.) still work? Or do I have to replace all?1885 wrote:
Added @AllowsOrgasm() Command Filter - will only display a line if the domme's "Allows Orgasms" settings matches what's in parentheses. You may enter as many options as you want. You may also use "Not" as a modifier. For example:
@AllowsOrgasm(Never) - Will only display if the domme never allows orgasm
@AllowsOrgasm(Often, Sometimes) - Will only display if the domme often or sometimes allows orgasm
@AllowsOrgasm(Not, Always) - Will only display if the domme does not always allow orgasm
@AllowsOrgasm(Always, Never, Not) - Will only display if the domme does not always allow orgasm and does not never allow orgasm
@AllowsOrgasm() replaces the Command Filters @AlwaysAllowsOrgasm, @OftenAllowsOrgasm, @SometimesAllowsOrgasm, @RarelyAllowsOrgasm, @NeverAllowsOrgasm, @NotAlwaysAllowsOrgasm and @NotNeverAllowsOrgasm. These are now legacy commands which will continue to function.
Everything that works now will continue to work, I don't want anybody to have to go back and change work they've already done. Those legacy Commands will remain in and remain functional, so you don't have to worry about that. The Command overhaul is just to simplify things for everyone (and myselfschefflera wrote:Does the old commands (@SometimesAllowOrgasm, etc.) still work? Or do I have to replace all?
) going forward.I cannot speak for everyone, but I don't have these problems. I 'play' the wicked personality with some self created modules and it runs perfect. Just sometimes it crashes at the beginning, when it tries to load a local image or so.meaculpa_uk wrote:Hi folks,
Gripe alert!!!
Can something please sit still for a while.. say a month or so.. for those of us trying to create an erotic tease to be enjoyed by others, all of this new stuff and all of the errors it's throwing up is making it become a really thankless and un-enjoyable task. I used to rate my work by how turned on it made me feel to do.. at the moment I'm suffering a serious flop-on! Or.. alternatively let writers (not developers, not people who care about the intricacies of the programme per se) know when it's safe to start work.
I've spent days upon days trying to make Spicy viable (I love you genome.. but she's seriously broken still!) I had her to the point where she would run smoothly 80% of the time and now she'll make a successful run-through maybe 1 in 10 times and is totally un-publishable. I feel like I'm fighting a tide but at the same time time I don't want to be another passive member of the community. For me, success is about creating a stable tease, with enough kink and 100% continuity from day to day that actually turns people on.
I know this sounds like a QQ and it's not meant to be.. I love all of the new possibilities and 1885, I'm so happy that you're back, but at the moment I'm resorting to using alternative means for actual stimulation.. doesn't this defeat the entire purpose? I'm sure I'm not the only one who feels this way.
Mea
Code: Select all
COMMAND: It's going to feel so good when you finally get to cum @FollowUp50(If you are lucky)
CHAT:
07:37 Rachel: It's going to feel so good when you finally get to cum you are lucky)
07:37 Rachel: If you are lucky
Don't worry, I won't put you on any pressure1885 wrote:The domme tag App that currently exists in Tease AI is tied to the domme's slideshow in the main window. When you want to tag something that appears in the current image of the domme, click the button in the app. It will then be highlighted in green to show you that domme tag exists. You can remove a domme tag by clicking it and it will turn back to its normal color. This was an interim solution I came up with when integrating the old apps into the main form. The domme and image tag system needs an overhaul, and it's on my to do list. I hope the final system will be as versatile as possible and provide a lot of feedback, but I can't really take a look at it until my immediate work has been finished so please bear with merayray77 wrote:How does the new Domme tags App work? In Patch 47 it opened a seperat window, in which all images of one folder were displayed. Now I dont know how to get this back since Patch 48... I don't want to use the old system and with the new one I can only work on 1 image at a time (and this is worse than with the old one, because every tag is deselecting itself with the next image) :D
Just wanted to ask in case I was missing something (wouldn't be the first time).
Just a tip, you can use @NewDommeSlideshow at any point in the scripts to change that.Mat wrote:Just a quick suggestion/request..
Could you make it so that if the domme sideshow gets to the end it automatically chooses a new one?
Normally it's not a problem but sometimes it randomly selects a set with only a few images in.
@CallReturn() stops everything you're doing and runs a new script. When that sc4ript ends, it tried to remember what you were doing, and put you back in that state where you left off. It's a Command I was working on right before the hiatus and I never could get it to work right. It seems like the community was able to fix that Command in my absence, which is awesome, but I wanted to be able to do the same thing without interrupting what you were doing in the transition.PtheV wrote:Sorry if this already came up somewhere and I missed it, but could you explain the difference between @CallReturn and @Miniscript? From the description in the patch notes they seem very similar to me. In what context would you use one and not the other?
I'm sorry to hear that you're having trouble mea. I know that's really frustrating, and not the kind of frustrating we're looking for here.meaculpa_uk wrote:Can something please sit still for a while.. say a month or so.. for those of us trying to create an erotic tease to be enjoyed by others, all of this new stuff and all of the errors it's throwing up is making it become a really thankless and un-enjoyable task. I used to rate my work by how turned on it made me feel to do.. at the moment I'm suffering a serious flop-on! Or.. alternatively let writers (not developers, not people who care about the intricacies of the programme per se) know when it's safe to start work.
I've spent days upon days trying to make Spicy viable (I love you genome.. but she's seriously broken still!) I had her to the point where she would run smoothly 80% of the time and now she'll make a successful run-through maybe 1 in 10 times and is totally un-publishable. I feel like I'm fighting a tide but at the same time time I don't want to be another passive member of the community. For me, success is about creating a stable tease, with enough kink and 100% continuity from day to day that actually turns people on.
I know this sounds like a QQ and it's not meant to be.. I love all of the new possibilities and 1885, I'm so happy that you're back, but at the moment I'm resorting to using alternative means for actual stimulation.. doesn't this defeat the entire purpose? I'm sure I'm not the only one who feels this way.
Thanks for reporting this, this will be sorted for Patch 52. In the meantime, SensEx's fix will work. Sorry about thatHarry2stroke wrote:hmmm
thats what i get when i just try to open Tease AI with Patch 51
avatarbr wrote:- when you use @MultipleEdges with a Glitter contact (like @Contact3 #Edge @EdgeNoHold @MultipleEdges(8, 5, 100)), TeaseAI use Domme images. Its possible to change that?
- when TeaseAI dont find a Vocabulary file, instead of a popup message, would be possible to just show the #File in the chat? Maybe in other color. Its a little distract to get that popup in the middle of the session.
- Not sure if something with my configuration, but ShowBoobsImage shows Butt images
- When using @FollowUpXX() command, I got this:
Done, added the option in Patch 52 as a Slideshow Option settingMat wrote:Could you make it so that if the domme sideshow gets to the end it automatically chooses a new one?
Normally it's not a problem but sometimes it randomly selects a set with only a few images in.
This is how the command looks: ... @FollowUp40(@RandomText(and let the inherent truth of these words seep in, and don't forget it, and let the message seep in, and let the message sink in, and let it sink in, and learn it, and say it passionately))03:17 Domme Name: Repeat that a few times let the message sink in
03:17 Domme Name: And let the message sink in