Spicy [Tease-AI] [Old thread]

[genome231]

Wauv you guys work fast!

@Pepsifreak
Added to the list that I need to change #PetName2 to #SlaveName in the scripts

Think I got them all except for:
"The end of GNMFirstMeeting (line 141) didn't seem to run its setval correctly, a number and a bracket made its way to the chat line"

I made a test:
Setting a level @SetVar[DenialLevelNr]=[5]
#DenialLevel
Now you can go ahead and jerk off... @SetVar[OTimeSet]=[#DenialLevel]
@ShowVar[OTimeSet] @Wait(999)
@End
That produced

Bug1.PNG (5.88 KiB) Viewed 2077 times

I feel like this should work? Looking at the image it is able to correctly choose a number, but when used with @SetVar[] it bugs?
Is it a bug related to Tease-AI?

That is how far I got today.

@Marspank & Daragorn
Sunday I'll be able to properly work through the lists and send out a new version.
Until then the @SetVar[OTimeSet]=[#DenialLevel] is a critical one!
I often call vocabulary files containing #Random(X,Y)

Until Sunday
Genome

[Daragorn]

I already answered you about the problem with the @SetVar[] not working with #Vocab in private, but i just came up with a solution that should work and is pretty easy to implement

Instead of @SetVar[name]=[#Vocab]
And then in the #Vocab having:
@Variable[DenialLevelNr]=[1] #Random(24,72)

You do like this:
In the script you just #Vocab
Ant the #Vocab files become:
@Variable[DenialLevelNr]=[1] @NullRespone @SetVar[name]=[#Random(24,72)]

I just tested it and it works perfectly

[marspank]

When trying to visit the Mistress for the test session on the second day, I am granted access, but then an index out of bounds / invalid index error is thrown around this line:

@Variable[#DateDifference(PDenial, Hours)]<=[PDenial] @NullResponse @Goto(Denial)

And then after the program continues to run, it gives me

"ERROR: Tease AI did not return a valid line while parsing vocabulary file: #DT"

Which seems to have a similar @Variable[#DateDifference(Devotion, Minutes)]

[marspank]

In FirstChoresRun.txt

Line 88

@SystemMessage #VANC #VANP How long would it take to clean the toilet/sink/shower etc. in the bathroom? @InputVar[BathroomSpecial] @CheckFlag(KicthenActive) @Goto(Rooms)

There is a typo. It should be KitchenActive

[marspank]

Another error linked to Chores:

When assigning an alternate chore, the path for the CallReturns are

@CallReturn(CR\BackgroundMode\Chores\ChoreFun.txt)

When they should be

@CallReturn(CR\BackgroundMode\Chores\SecondaryChores\ChoreFun.txt)

[marspank]

In ChoresAlt2.txt

Line 81 @SystemMessage #VANC #VANP I'm gonna show you a position and I want you to take and hold it until you hear my bell @SetFlag(ChoreActive) @Goto(c1,c2,c3,c4,c5,c6,c7,c8,c9,c10,c11,c12,c13,c14,c15,c16) gave me an indexing error

Also, all of the position images are lacking the ".jpg" extension

[Daragorn]

In the gnmChastity1_cinema.txt script you have
@NullResponse @ShowVideo[\GNM_Videos\Modules\CuckoldAndDenied\*.mp4]
But it should be
@NullResponse @PlayVideo[\GNM_Videos\Modules\CuckoldAndDenied\*.mp4]

When going to the desk in the background mode, when you select the busy mode you see a pic of the domme and not the assistant, i don't know if it is intended or not.
The busy modes don't work because you do @Interrupt(xxxMode) but @Interrupt looks for files in the interrupt folder while these are in CR/BackgroundMode/BusyMode so you should @Call or @CallReturn(CR/BackgroundMode/BusyMode/xxxMode.txt) to have them working

SpankChoirBase: if you select 5 minutes for cornertime it doesn't accept it and say you need to select between 5 and 30 minutes..
Change line 66 from:
@NullResponse @If[CornertimeTimeLimit]>[5]AND[CornertimeTimeLimit]<[30]Then(Approved2)
to
@NullResponse @If[CornertimeTimeLimit]>=[5]AND[CornertimeTimeLimit]<[30]Then(Approved2)

GNMLInkChastity:
Lines 53.57 and 61:
#GNMStartStroking @StartStroking @ShowImage
It should be a @StartTaunts since you are in chastity

[marspank]

In the GNMSnack.txt file there is a problem with the #VAN #VANC vocab files...instead of showing a pic (i suppose) of a girl named vivienne, you get pics of the domme and the chat lines are like this:
Vivienne VivienneC bla bla bla

In all of the other scripts, the code is #VANC #VANP. Changing it to this using a mass replace seemed to work.

[marspank]

In GNMStart.txt, Line 5

@Variable[#DateDifference(PDenial, Hours)]<=[PDenial] @NullResponse @Goto(Denial)


There is no (Denial), it should be pointing to (Denial1). I also have a hard time parsing this line. I haven't coded with TeaseAI much, but doesn't the #DateDifference give you a number of hours, but if you use it on PDenial, then that should be a date, so you are then comparing it to PDenial, which is a date, but should be a number of hours? It looks like elsewhere in the code, there is the same problem. But in the Punishment M6.txt, it uses a value called PDenialSet to store the number of hours.

On the same topic, while scanning through for PDenial, In almost every instance you use hours for the denial periods, but in OrgasmRoulette.txt you have

47 @NotFlag(HasChastity) So tomorrow is a no touch day! #DT @ChangeVar[PDenial]=[PDenial]+[1] @Goto(Deny)

So first, that should probably be changing the variable PDenialSet, and it should also be +[24] since it says one day. (This occurs in a few other locations in that script.)

[marspank]

More possible issues related to PDenial / PDenialSet.

In GNMChastityOnVA.txt: Lines 27 and 28 [also in GNMChastityOn, and GNMChastityIsOn]

@Variable[#DateDifference(PDenial,Hours)]>[PDenial] @SystemMessage #VANC #VANP So as a punishment I'm placing you in the #Cage for the next 24 hours.. @SetDate(PDenial, 0 Days) @SetVar[PDenial]=[24]
@Variable[#DateDifference(PDenial,Hours)]<[PDenial] @SystemMessage #VANC #VANP So as a punishment I'm increasing your denial period by 24 hours.. @ChangeVar[PDenial]=[PDenial]+[24]

First, it should be PDenialSet. But I also think you have the inequalities backwards. Line 27 should be if you are not under punishment denial, so <. Or is it too early in the morning for me?

[marspank]

In GNMFirstMeeting if you have a cage, she tells you to lock it up, but the flag for ChastityIsOn is never set, so that is why you are told to start stroking when you reach the link for the first time.

[marspank]

The ShortSession, MediumSession, and LongSession variables are never set correctly. I think in DevotionSet.txt lines 8-12 have @Change instead of @ChangeVar

When I changed this it did set the values, but MediumSession was a smaller number than ShortSession because of

@NullResponse @ChangeVar[SessionLengthFactor2]=[SessionLengthFactor2]*[7]
@NullResponse @ChangeVar[SessionLengthFactor3]=[SessionLengthFactor3]/[10]
@NullResponse @ChangeVar[SessionLengthFactor3]=[SessionLengthFactor3]*[4]

I believe the 4 and 7 should be reversed.

[marspank]

In the code there is a comment that Settings is ready to be implemented, so I am not sure if this is intentional, but if you choose that option (4) on the base menu it does not go anywhere because the SettingsBase files are all in a different folder than the one that code points to

(they are in CR\Settings)

[marspank]

edit: reorganized into other post

[marspank]

Issues with GNMChastityOff.txt, and possibly/probably all of the ChastityOn/Off scripts

1. The Images that are set for ChastityOff and ChastityOn are the old paths. With all of the new pictures they need to be changed to have the \*.* or \*.jpg
2. When you lock images, the #DT vocab that sets the domme tag image fails to work. I fixed this by removing #DT from all lines between when the image is locked, and when unlock images is called.
3. Line 6:
   @RT(Let me know when you're done..,Report to me when it's off,Remember to tell me when it's off) @Timeout(#CPatience,Hurry) has the same problem that Daragorn mentioned earlier. The fix was somthing similar to what he mentioned. In the #Cpatience script I changed the lines to set a variable called CPatience, called that script prior to the @TimeOut and then inside the @Timeout used the variable. But this did not seem to work, it went way faster than normal, almost instant. It also did not recognize my responses of having it off/removed.
4. If you do not take your belt off in time and are instructed to put it back on, the @SetFlag(ChastityIsOn) code is missing.