@DayOfWeek(Monday) @SystemMessage #VANC #VANP Today it is Monday meaning your exercise cycle runs from Monday to Sunday
@DayOfWeek(Tuesday) @SystemMessage #VANC #VANP Today it is Tuesday meaning your exercise cycle runs from Tuesday to Monday
@DayOfWeek(Wednesday) @SystemMessage #VANC #VANP Today it is Wednesday meaning your exercise cycle runs from Wednesday to Tuesday
@DayOfWeek(Thursday) @SystemMessage #VANC #VANP Today it is Thursday meaning your exercise cycle runs from Thursday to Wednesday
@DayOfWeek(Friday) @SystemMessage #VANC #VANP Today it is Friday meaning your exercise cycle runs from Friday to Thursday
@DayOfWeek(Saturday) @SystemMessage #VANC #VANP Today it is Saturday meaning your exercise cycle runs from Saturday to Friday
@DayOfWeek(Sunday) @SystemMessage #VANC #VANP Today it is Sunday meaning your exercise cycle runs from Sunday to Saturday
But when I run it with the german word it run but says today is Saturday but it is Friday
@DayOfWeek(Montag) @SystemMessage #VANC #VANP Today it is Monday meaning your exercise cycle runs from Monday to Sunday
@DayOfWeek(Dienstag) @SystemMessage #VANC #VANP Today it is Tuesday meaning your exercise cycle runs from Tuesday to Monday
@DayOfWeek(Mittwoch) @SystemMessage #VANC #VANP Today it is Wednesday meaning your exercise cycle runs from Wednesday to Tuesday
@DayOfWeek(Donnerstag) @SystemMessage #VANC #VANP Today it is Thursday meaning your exercise cycle runs from Thursday to Wednesday
@DayOfWeek(Freitag) @SystemMessage #VANC #VANP Today it is Friday meaning your exercise cycle runs from Friday to Thursday
@DayOfWeek(Samstag) @SystemMessage #VANC #VANP Today it is Saturday meaning your exercise cycle runs from Saturday to Friday
@DayOfWeek(Sonntag) @SystemMessage #VANC #VANP Today it is Sunday meaning your exercise cycle runs from Sunday to Saturday
@Day(<Number>) checks for the day of the month. Today a line would be valid if @Day(25)
@DayOfWeek(<localized Day String>) This is an error in the localization. There are countries starting their weeks with Sunday and some with Monday (ISO-standard). And since you need to enter a German weekday name it uses a Monday as first day of week, but then it uses the Sunday as first day of the week to validate... techno blah.
It's easy fixable. But i wasn't present for a long time and currently there are three versions of TAI. I'll merge them down to a single one and implement that fix. It could take a while, to put all those loose ends together.
Included in upcoming Patch 0.55.4.0: Fixed issue where @DayOfWeek was a day off. Added the additional possibility to use numbers as parameter, since localized day strings are useless for script exchange. The first day of week is Monday.
Last edited by Stefaf on Sun Nov 05, 2017 5:21 pm, edited 3 times in total.
avatarbr wrote: Sun Oct 29, 2017 2:52 am
It's a minor bug, I don't know if worth it messing with a (now) stable version to fix that, but...
It's simple to fix the wrong day issue, as well as using numbers instead or localized day names. It's a single line and i'm 99% sure it won't affect stability.About using numbers instead of strings: I just thought it would enhance exchanging scripts, from people different languages. Now every user has to change that day names to it's own language, to make a script, using this filter, working.
avatarbr wrote: Sun Oct 29, 2017 2:52 amIf you include a Glitter in the stroke/module/link circle, only the Glitter taunts are called when in the stroking part.
I'd love to fiddle around with that circle, but that will most likely affect stability. But for what i remember, it used glitter taunts if there were contacts in the chat. Is it broken now?
avatarbr wrote: Sun Oct 29, 2017 2:52 am
It's a minor bug, I don't know if worth it messing with a (now) stable version to fix that, but...
It's simple to fix the wrong day issue, as well as using numbers instead or localized day names. It's a single line and i'm 99% sure it won't affect stability.About using numbers instead of strings: I just thought it would enhance exchanging scripts, from people different languages. Now every user has to change that day names to it's own language, to make a script, using this filter, working.
avatarbr wrote: Sun Oct 29, 2017 2:52 amIf you include a Glitter in the stroke/module/link circle, only the Glitter taunts are called when in the stroking part.
I'd love to fiddle around with that circle, but that will most likely affect stability. But for what i remember, it used glitter taunts if there were contacts in the chat. Is it broken now?
The minor bug I was talking is the Glitter one I found, not the other
And yes, if you include a glitter in the circle, will use the glitter taunts, but you stop getting the Domme taunts (with her in chat yet). I think TeaseAI think all the domme taunts are @Group(D)
But if this have a chance to affect the stability, let away. It's a specific case, and really not a big deal.
avatarbr wrote: Sun Oct 29, 2017 9:52 pm
The minor bug I was talking is the Glitter one I found, not the other
And yes, if you include a glitter in the circle, will use the glitter taunts, but you stop getting the Domme taunts (with her in chat yet). I think TeaseAI think all the domme taunts are @Group(D)
But if this have a chance to affect the stability, let away. It's a specific case, and really not a big deal.
That's is no bug, that is meant that way. If the domme is alone all StrokeTaunt-Files are used. If somebody has joined the chat it uses GlitterTaunts -> Even if there are no lines available for the given group combination -> "ERROR: Tease AI did not return a valid Taunt from file:" -> That's your problem i guess?
avatarbr wrote: Sun Oct 29, 2017 9:52 pm
I think TeaseAI think all the domme taunts are @Group(D)
Logically yes - technically no. @Group is a pretty new command. Taunts use a "flag" which is set, as soon any contact has been added to the chat. If this flag is set, it uses GlitterTaunts_0-9999.txt, otherwise StrokeTaunts_0-9999.txt.
avatarbr wrote: Sun Oct 29, 2017 9:52 pm
The minor bug I was talking is the Glitter one I found, not the other
And yes, if you include a glitter in the circle, will use the glitter taunts, but you stop getting the Domme taunts (with her in chat yet). I think TeaseAI think all the domme taunts are @Group(D)
But if this have a chance to affect the stability, let away. It's a specific case, and really not a big deal.
That's is no bug, that is meant that way. If the domme is alone all StrokeTaunt-Files are used. If somebody has joined the chat it uses GlitterTaunts -> Even if there are no lines available for the given group combination -> "ERROR: Tease AI did not return a valid Taunt from file:" -> That's your problem i guess?
avatarbr wrote: Sun Oct 29, 2017 9:52 pm
I think TeaseAI think all the domme taunts are @Group(D)
Logically yes - technically no. @Group is a pretty new command. Taunts use a "flag" which is set, as soon any contact has been added to the chat. If this flag is set, it uses GlitterTaunts_0-9999.txt, otherwise StrokeTaunts_0-9999.txt.
Oh, I didn't know that. So, if I want the Domme talk, I need to add some lines without @Contact in the GlitterTaunts files, right?
avatarbr wrote: Wed Nov 01, 2017 12:17 am
Oh, I didn't know that. So, if I want the Domme talk, I need to add some lines without @Contact in the GlitterTaunts files, right?
Yes.
In multiline taunts none of the lines is allowed to have a @Contact. If a single line of a taunt group contains a @Contact, the hole taunt is filtered out - Or it's broken again.
avatarbr wrote: Wed Nov 01, 2017 12:17 am
Oh, I didn't know that. So, if I want the Domme talk, I need to add some lines without @Contact in the GlitterTaunts files, right?
Yes.
In multiline taunts none of the lines is allowed to have a @Contact. If a single line of a taunt group contains a @Contact, the hole taunt is filtered out - Or it's broken again.
Hm...I have @Contact in all the lines of GlitterTaunts_2 and 3 (you need to put in all lines) and works.
Hi!
I was doing some tests for a script I'm writing but there's a problem with a command I'd like to use. Can you help me, please?
The problem is this line:
@Variable[#DateDifference(SYS_LastOrgasm, Hours)]>[48] You had your last orgasm on @ShowVar[SYS_LastOrgasm]
I had my last orgasm on August 27, so it's more than 48 hours away from now, still it doesn't work.
I did a simple test using @ShowVar[SYS_LastOrgasm] and the result was 0! So I checked my variables folder and there was no variable SYS_LastOrgasm.
tigrotto wrote: Sun Nov 05, 2017 3:29 pm
@Variable[#DateDifference(SYS_LastOrgasm, Hours)]>[48] You had your last orgasm on @ShowVar[SYS_LastOrgasm]
There are 2 reasons why it doesn't work.
- SYS_LastOrgasm: There is no such variable/keyword. At least I can't find any sign of it in the source code.
- #DateDifference returns a number. Then @Variable would search for a variable named like that returned number.
tigrotto wrote: Sun Nov 05, 2017 3:29 pm
I did a simple test using @ShowVar[SYS_LastOrgasm] and the result was 0! So I checked my variables folder and there was no variable SYS_LastOrgasm.
That's correct. All non existing variables return zero.
I know why it's not working, but i've no currently working solution for you, since i only write debugging scripts. Maybe some of the scripters can help you out.
tigrotto wrote: Sun Nov 05, 2017 3:29 pm
@Variable[#DateDifference(SYS_LastOrgasm, Hours)]>[48] You had your last orgasm on @ShowVar[SYS_LastOrgasm]
There are 2 reasons why it doesn't work.
- SYS_LastOrgasm: There is no such variable/keyword. At least I can't find any sign of it in the source code.
- #DateDifference returns a number. Then @Variable would search for a variable named like that returned number.
tigrotto wrote: Sun Nov 05, 2017 3:29 pm
I did a simple test using @ShowVar[SYS_LastOrgasm] and the result was 0! So I checked my variables folder and there was no variable SYS_LastOrgasm.
That's correct. All non existing variables return zero.
I know why it's not working, but i've no currently working solution for you, since i only write debugging scripts. Maybe some of the scripters can help you out.
Thanks Stefaf.
I found variable SYS_LastOrgasm in the TeaseAI Language Guide while reading about @CheckDate. I know that this guide is not up to date, so probably(if it ever existed...) it has been deleted in a previous version of the code.
Is there a filter, or similar solution(if such thing is possible), that allows to do something if you had your last orgasm more than XX minutes, hours, days ago?
Something like this for example:
tigrotto wrote: Sun Nov 05, 2017 3:29 pm
Hi!
I was doing some tests for a script I'm writing but there's a problem with a command I'd like to use. Can you help me, please?
The problem is this line:
@Variable[#DateDifference(SYS_LastOrgasm, Hours)]>[48] You had your last orgasm on @ShowVar[SYS_LastOrgasm]
I had my last orgasm on August 27, so it's more than 48 hours away from now, still it doesn't work.
I did a simple test using @ShowVar[SYS_LastOrgasm] and the result was 0! So I checked my variables folder and there was no variable SYS_LastOrgasm.
Any suggestion? Thanks.
Bye
Funny, yesterday I created (for the first time) something with that too. I don't think worked too.
Since Stefaf said this was not implemented, I think the only solution is to create you own variable to check the last orgasm (I don't remember the code for that, but I just started using this to keep track of the session time), and remember to reset when the user get a orgasm.
avatarbr wrote: Sun Nov 05, 2017 10:48 pm
Since Stefaf said this was not implemented, I think the only solution is to create you own variable to check the last orgasm (I don't remember the code for that, but I just started using this to keep track of the session time), and remember to reset when the user get a orgasm.
Thanks avatarbr, but I think that this solution would only work for you because you work on your personality.
My problem is different; since I'm working on scripts to add to an existing personality, what I need is something more "universal", that could work on HoT, MissBlue... without making changes. That's why a variable like SYS_LastOrgasm would have been perfect.
Ok I've come to the decision to implement SYS_LastOrgasm and SYS_LastRuined. When it's in the documentation (Which is pretty up to date btw.) and it's already stored in the settings, 1885 simply forgot about it. Or this was one of the reasons, why he hid that label in the first place.
Never the less: How are we going to treat it, if we restore a session?
Currently all vars and flags are stored on suspending a session and restored on resuming. Do we set the value stored in that session or do we set the "real" value?
