My personality collection is pretty outdated (I still have House of Tease 3.1.2, current version is 8.Xmarkus wrote: Mon Mar 28, 2022 7:08 pmIf you follow the Awakening announcement thread you'll see that I am very open minded for suggestions, ideas and wishes from scripters (also from users of course), ... I'll try to do my best to support any scripter and their feature- or functionality- wishes.N3R0 wrote: Sun Mar 27, 2022 3:16 pm
You are right, that the chances of the current image being exactly what the scripter wants, are very low. But if @ImageTag() or @DommeTag() can't find any matches for that tag, the original behaviour of @Tag... means the scripter can still respond to the current image (if that has been tagged with anything). With the new behaviour, scripters are forced to use general responses in that case.
In the existing personalities I only found very rare occations where this was used, IIRC only one file with a few lines (correct me if I'm wrong!).
Actually, the probability is 100%. Because they are filters!markus wrote: Mon Mar 28, 2022 7:08 pm That was when I thought that most probably the combination of that such a tagged pic is on the screen AND such a filter-line is (randomly!) drawn from such a file goes close to zero.
At this point of development I try to focus on what is really needed to get this thing working for existing personalities and not on theoretical possibilities which maybe never be used.
So my question is:
Do you actually plan to use these filters for your personality?
(Note to all readers: the tags used in the following code are made-up, they don't [necessarily] exist for real ! They are supposed to represent domme tags.)
If the scripter wants to tell a "story", where it is important to show a particular kind of image, they use @DommeTag(...) to show the image and make a comment about it.
But if the scripter only wants to make things more immersive (which is my plan for my personality) they would use @Tag...
If you have the following line somewhere, e.g. in a module:
Code: Select all
I can see you staring at me #PetName @FollowUp(#CommentImage)Example 1:
Code: Select all
Do you like what you see? #Grin
Do you like the color of my toe nails?
Do you prefer shaven or hairy armpits?
Code: Select all
Do you like what you see? #Grin
@TagToes Do you like the color of my toe nails?
@TagArmpit Do you prefer shaven or hairy armpits?
But in example 2, the chance of the image matching the text is 100%, because every line that refers to a tag that is missing from the current image, will be filtered out.
If the image has no tags at all or if none of the tags of the current image is listed in #CommentImage, then the general response (the first line, in this example) will be used. Using @Tag this way is the whole idea of why 1885 added @Tags to TAI in the first place!
This does make sense for things like @BadMood vs @BadMood(), but I don't think it is a good idea to rename the @Tags.markus wrote: Mon Mar 28, 2022 7:08 pm It wouldn't be that much of a problem to implement, filters for videos are already working (@VideoHardcore and so on) ... these make much more sense IMHO.
If you (or any other scripter) want to have this implemented, it will become a point on my ToDo-list, but, ... and that's for sure, with different names, so that the filters and commands don't have the same name anymore (this is also something on my ToDo-List, to give alternatives for such cases in which a command and a filter have the same name so future scripts could be written and readed a bit more understandable).
All those commands, filters etc. are already confusing enough for new scripters. The more differences there are between the different editions of TAI, the more confusing it becomes, IMO.
I hope this helps to understand my POV.
Have a nice day.
And to anyone who reads this today: don't let people fool you tomorrow!


