Tease AI Bug Report Thread

[Trusfrated]

This is very minor game stuff.

The Risky Pick.txt script has a typo in the first line: "@PlayRiskReady" <--Should be a space between Risk & Ready, I think.

With patch 54.1: Under Games, Exchange. If you ask the domme for more tokens and it runs a Token Task script, it does not start a domme slide show. I just got a black screen in the media window for the duration of the script.

[avatarbr]

Just remembered 2 small things:

- Sometimes, the Glitter 1 pic are replaced by the domme pics.
If I change the folder, goes back to normal (if I did not change, every script with Glitter 1 will use domme pics), and not always happens. Just with Glitter 1, never with 2 or 3.

- Not a bug, but every new patch, the first time running take a really long time to launch the program. This is normal?

[Stefaf]

I was using Spicy with Patch 53, and during EdgeATon, the program crashed with a 504 Gateway Timeout error. I hit Continue but the script was frozen. Could we trap this one? I'm not sure what site it was trying to reach, other than maybe Tumblr. But it would be nice to gracefully alert the user (or skip the image), rather than stop completely.

Thanks!

Here is the file the Error Log created:

Spoiler: show

###################################################################
Date/Time: 2016-05-10 22:15:03
Version: 1.0.0.0
BuildDate (UTC): 2015-05-16 00:14:50
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~~~~~~~~~~~~~~~~~~~~~~~~~
at Tease_AI.BackgroundWorkerSyncable.TriggerTimer_Tick(Object sender, EventArgs e) in C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease AI\Tease AI\Classes\BackgroundWorkerSyncable.vb:line 36
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.RunDialog(Form form)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at System.Windows.Forms.Form.ShowDialog()
at System.Windows.Forms.Application.ThreadContext.OnThreadException(Exception t)
at System.Windows.Forms.Timer.TimerNativeWindow.OnThreadException(Exception e)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
at Tease_AI.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 82

This Issue is solved in Version 54.2. Now a the ErrorImage is displayed and a log entry is written.

- Not a bug, but every new patch, the first time running take a really long time to launch the program. This is normal?

A really long time? And on second run it is back to normal?

[avatarbr]

- Not a bug, but every new patch, the first time running take a really long time to launch the program. This is normal?

A really long time? And on second run it is back to normal?

Yes. Not a big problem, just curious.
Can take 1 or 2 minutes to load after a patch. And a few seconds (<5sec) in normal cases.

And now, when you need to import the settings and TeaseAI restart, its fast already.

Another thing: When you change the Personality, TeaseAI keep going back to the previous selected after you restart the program. There is something you can do to stop that (because I already could change), but I cant remember what.

[Stefaf]

Yes. Not a big problem, just curious.
Can take 1 or 2 minutes to load after a patch. And a few seconds (<5sec) in normal cases.

And now, when you need to import the settings and TeaseAI restart, its fast already.

Another thing: When you change the Personality, TeaseAI keep going back to the previous selected after you restart the program. There is something you can do to stop that (because I already could change), but I cant remember what.

That's strange. Before the Splash screen is displayed or before?

That's a problem caused by the settings duplicating (Sorry! ). The saving is alsways 1 minute too late. And on startup it uses this "old" file and replaces the new file in %LocalAppDir%. We've hotfixed this already on github. The primary file is then the file in %LocalAppDir%. As well as the need for importing data when starting a new version from the same folder as the previous folder.

Spoiler: show

Stupid settings... I knew i should leave my fingers from this. But i was curious. ^^

[avatarbr]

Yes. Not a big problem, just curious.
Can take 1 or 2 minutes to load after a patch. And a few seconds (<5sec) in normal cases.

And now, when you need to import the settings and TeaseAI restart, its fast already.

Another thing: When you change the Personality, TeaseAI keep going back to the previous selected after you restart the program. There is something you can do to stop that (because I already could change), but I cant remember what.

That's strange. Before the Splash screen is displayed or before?

That's a problem caused by the settings duplicating (Sorry! ). The saving is alsways 1 minute too late. And on startup it uses this "old" file and replaces the new file in %LocalAppDir%. We've hotfixed this already on github. The primary file is then the file in %LocalAppDir%. As well as the need for importing data when starting a new version from the same folder as the previous folder.

Spoiler: show

Stupid settings... I knew i should leave my fingers from this. But i was curious. ^^

The long loading itsbefore the splash screen...just TeaseAI process running in background.

Oh, so I just need to wait >1min to work? Maybe this is what happened to work before, because now I was testing closing and opening the program all the time

[SkyHimeros]

(I moved this post here from the other topic.)

I just installed the latest patch and couldn't open TeaseAI any more. I tried a fresh install from the first page and that didn't work either. I've reverted back to patch 54.2 and now it work's again.

[chefboyrdee]

I'm experiencing some problems with the pictures. If I try to load a certain slideshow form the dropdown menu, it'll eventually crash the images completely and I'm left with a large red X on the screen. I think this happened after the upgrade to 54.2, but it's continued in 54.3. When I let the images load normally through the domme and all that I haven't experienced this issue at all.

[curiousSK]

I'm experiencing some problems with the pictures. If I try to load a certain slideshow form the dropdown menu, it'll eventually crash the images completely and I'm left with a large red X on the screen. I think this happened after the upgrade to 54.2, but it's continued in 54.3. When I let the images load normally through the domme and all that I haven't experienced this issue at all.

I also posted this in the TeaseAI Beta post, but will put it here to ensure it's spotted:

Hi all, well done for the great work you continue to put into this project.

BUG REPORT
-------------
I keep getting an error with the new patches (since 54 i think) where TeaseAI will try to display an imagine (i'm not sure if this is one downloaded, but I have a feeling it's from one of the online resources) when I get the following error:

Spoiler: show

Title: Error loading image. Performing fallback to errorimage.
Message: Error loading Image:
Exceptions:
================================== Exception =====================================
Message: The path is not of a legal form.
Typ: System.ArgumentException
StackTrace:
at System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength)
at System.IO.Path.GetFullPathInternal(String path)
at System.IO.Path.GetFullPath(String path)
at System.Drawing.IntSecurity.UnsafeGetFullPath(String fileName)
at System.Drawing.IntSecurity.DemandReadFileIO(String fileName)
at System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement)
at Tease_AI.Form1.BWimageFetcher_DoWork(Object sender, DoWorkEventArgs e) in C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease AI\Tease AI\Form1\ImageFuctions.vb:line 715


~~~~~~~~~~~~~~~~~~~~Application.StackTrace~~~~~~~~~~~~~~~~~~~~~~~~~
at Tease_AI.Form1.BWimageFetcher_DoWork(Object sender, DoWorkEventArgs e) in C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease AI\Tease AI\Form1\ImageFuctions.vb:line 731
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at Tease_AI.BackgroundWorkerSyncable.OnDoWork(DoWorkEventArgs e) in C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease AI\Tease AI\Classes\BackgroundWorkerSyncable.vb:line 90
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.DoAsyncCall()
at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(Object o)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Essentially, I think the URL to an image is too long, is this even possible?

I managed to replicate how this looks by crashing the UI with another bug (more on that in a minute), which then make all of the UI blank out with white boxes with red crosses through (Image attached)

The second bug, which is one i've personally encountered since the early TeaseAI is when an online resource or downloaded GIF doesn't start, so the gif goes through the different slides and then stops, this causes TeaseAI to crash and some sort of image exception. When I recreated this I just clicked images and viewed one of tumblr resources which I know used lots of gifs and kept skipping until one crashed it (took about 15 gifs). As I was viewing this in preview, it through up another but which I think relates to scalling of the iamge some how (this is a guess), errorlog in spoiler below.

Spoiler: show

************** Exception Text **************
System.Runtime.InteropServices.ExternalException (0x80004005): A generic error occurred in GDI+.
at System.Drawing.Image.SelectActiveFrame(FrameDimension dimension, Int32 frameIndex)
at System.Drawing.ImageAnimator.ImageInfo.UpdateFrame()
at System.Drawing.ImageAnimator.UpdateFrames()
at System.Windows.Forms.ButtonBase.OnPaint(PaintEventArgs pevent)
at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

I hope this report makes sense and is something that is fixable as unless i inspect each gif i download individually and deselect the URL links then I will continue to have teaseAI crash mid-session.

If anyone has any info, it would be really great if you could share it. I'm running XP on bootcamp on my macbook.

Thanks in advance

[avatarbr]

So, yesterday I got 2 crashes at the Stroke taunts (something about the lenght to long)...going back to 54.2 solved the problem.
Today, I installed 54.3 again to replicate and copy the error log, and no crash


PS: I am the worst beta tester ever

[Stefaf]

(I moved this post here from the other topic.)

I just installed the latest patch and couldn't open TeaseAI any more. I tried a fresh install from the first page and that didn't work either. I've reverted back to patch 54.2 and now it work's again.

I'll simply copy my post from the other thread:
Maybe you are a casualty of this above bug. have you started patch 54.2 and 54.3 from the same directory? If so, try the following. Go to your "%LocalAppData%\Tease_AI" directory and open the folder where the 0.54.0.2 directory is in and Create a Folder named "0.52.3.0". But this applies only if you start 52.2 and 52.3 from the same directory.

Could you please try this?

(I moved this post here from the other topic.)

I just installed the latest patch and couldn't open TeaseAI any more. I tried a fresh install from the first page and that didn't work either. I've reverted back to patch 54.2 and now it work's again.

At the moment we are reworking all image-related Code. This part is using the old code in the current release, which may interfere with the new one. Actually the rework of exact this part is on the workbench.
Sorry for your trouble right now, but i think in the next release this problem is solved - or at least worse. No i'm just kidding.

So, yesterday I got 2 crashes at the Stroke taunts (something about the lenght to long)...going back to 54.2 solved the problem.
Today, I installed 54.3 again to replicate and copy the error log, and no crash

Hmmm. Was it image related? In the other post a too long URL was mentioned. This kind of error would be logged to the ErrorLogs. Maybe you can take a look there.

PS: I am the worst beta tester ever

Not at all. The worst case is if somebody encounters a problem and doesn't say anything. Not all things can be solved right away, because Tease-AI is a really huge intertwined project. But the things we can fix - we will fix!

[SkyHimeros]

Maybe you are a casualty of this above bug. have you started patch 54.2 and 54.3 from the same directory? If so, try the following. Go to your "%LocalAppData%\Tease_AI" directory and open the folder where the 0.54.0.2 directory is in and Create a Folder named "0.52.3.0". But this applies only if you start 52.2 and 52.3 from the same directory.

Thank you! I tried it and it works now!

[avatarbr]

So, yesterday I got 2 crashes at the Stroke taunts (something about the lenght to long)...going back to 54.2 solved the problem.
Today, I installed 54.3 again to replicate and copy the error log, and no crash

Hmmm. Was it image related? In the other post a too long URL was mentioned. This kind of error would be logged to the ErrorLogs. Maybe you can take a look there.

I have a few of this errors:

Code: Select all

###################################################################
Date/Time: 2016-05-23 22:25:59
Version: 0.54.0.2
BuildDate (UTC): 2016-05-19 17:23:53
Title: Error loading image. Performing fallback to errorimage.
Message: Error loading Image: 
Exceptions: 
	================================== Exception =====================================
	Message: O caminho tem um formato inválido.
	Typ:     System.ArgumentException
	StackTrace:
	   em System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
	   em System.IO.Path.GetFullPathInternal(String path)
	   em System.IO.Path.GetFullPath(String path)
	   em System.Drawing.IntSecurity.UnsafeGetFullPath(String fileName)
	   em System.Drawing.IntSecurity.DemandReadFileIO(String fileName)
	   em System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement)
	   em Tease_AI.Form1.BWimageFetcher_DoWork(Object sender, DoWorkEventArgs e) na C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease AI\Tease AI\Form1\ImageFuctions.vb:linha 715


~~~~~~~~~~~~~~~~~~~~Application.StackTrace~~~~~~~~~~~~~~~~~~~~~~~~~
   em Tease_AI.Form1.BWimageFetcher_DoWork(Object sender, DoWorkEventArgs e) na C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease AI\Tease AI\Form1\ImageFuctions.vb:linha 731
   em System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   em Tease_AI.BackgroundWorkerSyncable.OnDoWork(DoWorkEventArgs e) na C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease AI\Tease AI\Classes\BackgroundWorkerSyncable.vb:linha 90
   em System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
   em System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   em System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
   em System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(Object o)
   em System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
   em System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   em System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   em System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   em System.Threading.ThreadPoolWorkQueue.Dispatch()
   em System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

But I am now sure if the time its correct. 22:25h I was probably testing some scripts, not the time I got the error in the taunts part.

[Stefaf]

So, yesterday I got 2 crashes at the Stroke taunts (something about the lenght to long)...going back to 54.2 solved the problem.
Today, I installed 54.3 again to replicate and copy the error log, and no crash

Hmmm. Was it image related? In the other post a too long URL was mentioned. This kind of error would be logged to the ErrorLogs. Maybe you can take a look there.

I have a few of this errors:

Code: Select all

###################################################################
Date/Time: 2016-05-23 22:25:59
Version: 0.54.0.2
BuildDate (UTC): 2016-05-19 17:23:53
Title: Error loading image. Performing fallback to errorimage.
Message: Error loading Image: 
Exceptions: 
	================================== Exception =====================================
	Message: O caminho tem um formato inválido.
	Typ:     System.ArgumentException
	StackTrace:
	   em System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength, Boolean expandShortPaths)
	   em System.IO.Path.GetFullPathInternal(String path)
	   em System.IO.Path.GetFullPath(String path)
	   em System.Drawing.IntSecurity.UnsafeGetFullPath(String fileName)
	   em System.Drawing.IntSecurity.DemandReadFileIO(String fileName)
	   em System.Drawing.Image.FromFile(String filename, Boolean useEmbeddedColorManagement)
	   em Tease_AI.Form1.BWimageFetcher_DoWork(Object sender, DoWorkEventArgs e) na C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease AI\Tease AI\Form1\ImageFuctions.vb:linha 715


~~~~~~~~~~~~~~~~~~~~Application.StackTrace~~~~~~~~~~~~~~~~~~~~~~~~~
   em Tease_AI.Form1.BWimageFetcher_DoWork(Object sender, DoWorkEventArgs e) na C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease AI\Tease AI\Form1\ImageFuctions.vb:linha 731
   em System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   em Tease_AI.BackgroundWorkerSyncable.OnDoWork(DoWorkEventArgs e) na C:\Users\Elijah\Documents\Visual Studio 2010\Projects\Tease AI\Tease AI\Classes\BackgroundWorkerSyncable.vb:linha 90
   em System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
   em System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   em System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
   em System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(Object o)
   em System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
   em System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   em System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   em System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   em System.Threading.ThreadPoolWorkQueue.Dispatch()
   em System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

But I am now sure if the time its correct. 22:25h I was probably testing some scripts, not the time I got the error in the taunts part.

The Filepath is not too long... It is too short. If not better said empty.
Unfortunately the Stacktrace doesn't provide enough information's to see why the filepath is empty. In the next release there will be a check before the backgroundthread is started. This way we an say where the error occurs and eliminate it. I also replaced all times with local times. It was UTC to identify the version of TeaseAI. But now we use Version numbers and this is useless.
Thank you for your information!

Maybe you are a casualty of this above bug. have you started patch 54.2 and 54.3 from the same directory? If so, try the following. Go to your "%LocalAppData%\Tease_AI" directory and open the folder where the 0.54.0.2 directory is in and Create a Folder named "0.52.3.0". But this applies only if you start 52.2 and 52.3 from the same directory.

Thank you! I tried it and it works now!

No problem - You're welcome. In the next release this problem should be solved.

[avatarbr]

I dont know if everybody is aware of this, but....

Some time ago, I found a way to continue sessions after TeaseAI get a error. Did not work if TeaseAI crashes, but works if you click the continue buttom in the popup message or if get stuck after some script error.

You just need to create a file in the Response folder with this:

Code: Select all

[fix]
try to type your safeword after the tasks in the CBT @CBT
[Before Tease]
try to type your safeword after the tasks in the CBT @CBT
[Before Tease End]
[First Round]
try to type your safeword after the tasks in the CBT @CBT
[First Round End]
[Stroking]
try to type your safeword after the tasks in the CBT @CBT
[Stroking End]
[Not Stroking]
try to type your safeword after the tasks in the CBT @CBT
[Not Stroking End]
[Edging]
try to type your safeword after the tasks in the CBT @CBT
[Edging End]
[Holding The Edge]
try to type your safeword after the tasks in the CBT @CBT
[Holding The Edge End]
[CBT Cock]
try to type your safeword after the tasks in the CBT @CBT
[CBT Cock End]
[CBT Balls]
try to type your safeword after the tasks in the CBT @CBT
[CBT Balls End]
[Chastity]
try to type your safeword after the tasks in the CBT @CBT
[Chastity End]
[After Tease]
try to type your safeword after the tasks in the CBT @CBT
[After Tease End]

Or use this file:

Fix.zip

(332 Bytes) Downloaded 746 times

I dont know why, but the @CBT command works when all the others stoped. Just type "fix" (without quotation marks) and after the CBT routine, you can type your safeword and the script will start working again.