Tease AI Bug Report Thread

[N3R0]

Hi,

ok, I give up. I just spend several hours trying to figure this out, but I can't.

Can someone tell me what triggers the #Return_*.txt files to be called? I always believed they get triggered after @CallReturn is done with whatever script was called. But I just tried it with #Return_Stroking.txt and it's not being run.

I read TAI's source code, but could only find the part, where it decides WHICH file to use, but not WHEN.


How does this stuff work???

[markus]

Hi,

ok, I give up. I just spend several hours trying to figure this out, but I can't.

Can someone tell me what triggers the #Return_*.txt files to be called? I always believed they get triggered after @CallReturn is done with whatever script was called. But I just tried it with #Return_Stroking.txt and it's not being run.

I read TAI's source code, but could only find the part, where it decides WHICH file to use, but not WHEN.


How does this stuff work???

That gave me headaches as well.
In Awakening it triggers the #Return_Stroking.txt only if you are in the stroke cycle, if you @CallReturn out of it (from stroke taunts, there are some @CallReturn's), then you come back to the stroke taunts and the metro is not running:
Get back to stroking @StartStroking @PlayAudio[tease\cStroke.mp3]

I've left all other #Return_ ... out, it looks to me like one of the cases in which 1885 did a bit too much hardcoding-specific-cases which would have been better left to the scripter.
I think it's connected to the user state which are also used in the responses (the similarity in the names of the #Return_ is obvious):

[Stroking]

[Stroking End]

[Edging]

[Edging End]

[Holding The Edge]

[Holding The Edge End]

[CBT Cock]

[CBT Cock End]

[CBT Balls]

[CBT Balls End]

[Chastity]

[Chastity End]

I've found this comment in my source I've wrote years ago:

#Return_CBTBalls Used for @CallReturn() when sub was doing ball torture before @CallReturn() was called.

-> Es gibt also automatisierte 'Reaktionen' wohl nach dem return.
Daß das keine so gute Idee war, zeigt sich durch den extra neu eingeführten Befehl @SilentReturn, der genau diese automatisierte 'Reaktionen'
verhindert und grade in Fury sehr häufig zum Einsatz kommt.

@NullResponse @TempFlag(CockDestruction_Punishment) @CallReturn(Custom\CR\Cock Destruction\Crop\MainLoop.txt) @SilentReturn

Even if it's not a 'complete' answer it maybe helps you getting on the right track, ... good luck!
Greetz,
Markus

[TyCaine]

[RESOLVED]

Hey all

Wondering if someone could help?

I'm on 0.55.3.0 and I've just noticed that @ImageTag() doesn't work...

to clarify, if it finds an image matching the tags, it throws an error and in the error message the image local file linked at fault is surrounded by double quotes...
and right before the end quote there's a space..
so the error message spits out something like:
"C:/thisURL/Images/Type/Femdom/thisImage.jpg " <- note the space before the end quote.

if I change out for @ShowFemdomImage it can find the same image in the same folder and it works fine, it just fails on @ImageTag()

Can anyone tell me how to fix this? There's a lot of tagged images in the LocalImageTags.txt file and if they don't work, it'll be a pain in the ass to update all references to @ImageTag...

Thanks in advance!

{EDIT]

The main source of tags I'm relying on is in the file LocalImageTags.txt
Is this not correct?

[EDIT - RESOLUTION]

Ok, it was a conglomeration of issues. First, it was a new install on a new computer and I'd copied everything over from the old, not registering the user name (even though entered the same) had been handled differently, which meant, though subtle, it completely changed the C:\Users\<username> URL that was used in all the image links in LocalImageTags.txt

Secondly, a bunch of the @ImageTag() entries had been entered with 4 params, not 3, which appeared to also cause a break...

Third, the tag names used in the @ImageTag() entries didn't exactly match those entered in LocalImageTages.txt...

So, lot's of issues, but figured out...