Interested in a small update? The last example for "Miss Tutorial" goes smoothly so far...
In this example I will showcase how to "imitate" the
Tease AI dialogue system within Pilgrim Quest. It works basically the same as in Tease AI and uses similar structured .txt files for #vocabulary, @tags, taunts, instructions... Most files from Tease AI could be even compatible if you use the same @tags. Like Tease AI it creates more "natural" responses with randomization including #vocabulary and @tags instead of fixed and static dialogue lines. You have full control over this flexible and modular system and you should be able to easy adapt it for your own encounters. So every encounter or sex demon can have her own unique taunts, instructions, @tags and #vocabulary if wanted. You could even use different sets of taunts, instructions, @tags and #vocabulary within a single encounter. This way you could "simulate" different moods for the sex demon, for example depending on the player energy or just the current date (not a summer person, eh?).
I also will integrate a
flexible image tag editor to edit tags to images directly within Pilgrim Quest. With tagged images the dialogue system will exactly know what the current image shows and in result create dialogue responses fitting to that specific content. Tagging is - like in Tease AI - optional as long as you also write some "generic" taunts or instructions (without specific @tag requirements). But with tagged images, the dialogue will be greatly enhanced.
Here some screenshots from my Tag Editor within Pilgrim Quest. The list of available tags is dynamically created from a tags.txt file, which you can easily customize. If you already had saved tags for this image, the editor will remember this and pre-fill the check boxes accordingly. The system is very robust. You can delete or add new images while you're in the tag editor and even change the tags. One click on refresh and the Editor automatically adjusts to these changes:
Here a more detailed example:
The script randomly chooses the following image. In the folder of this image is already a "_tagged.save" which has an entry for this image including the following @tags (previously added with the tag editor - see screenshot):
Code: Select all
@Solo, @LookAtMe, @Beauty, @Face, @Eyes, @Lips, @Tits, @Nipple, @BrownHair, @Teen
In this example also the following #vocabulary is active. So in a randomly selected line of dialogue all #vocabulary terms will be replaced with a randomly selected synonym from the corresponding #vocabulary file (i.e. #Cock.txt). Be aware: #UserName will be automatically created (no #UserName.txt needed).
Code: Select all
#Ass, #Balls, #Cock, #Cum, #Pussy, #NickName, #Tits, #UserName
And here some eligible example taunts for this image from my used taunts.txt:
Code: Select all
I'm gonna make sure that #Cock remembers every single stroke!
Code: Select all
We both know you like them young! Does this make your #Cock and #Balls ache already? @Teen
Code: Select all
Worship her beauty with every stroke! I want to see firm and full strokes, #UserName! @Beauty
Code: Select all
I bet you would love to play with these nipples, licking and twirling them until they're hard? Keep going! @Tits @Nipple
Code: Select all
Look her into the eyes! No glancing at her #Tits while you stroke your hard #Cock! @Solo @LookAtMe @Eyes @Tits
Code: Select all
Imagine her lips wrapped all around your #Cock, while she looks right into your soul with her beautiful eyes. How long could you resist if she really wanted to suck you empty? @Solo @LookAtMe @Eyes @Lips
Code: Select all
Where would you blow your load? Cover her face with your #Cum or spray it all over her #Tits? @Solo @Face @Tits
And how far is all of this? The tag editor and the system for #vocabulary is in place and tested... I already tagged the default images which i will include in the example using the tag editor. For the next step i will copy my system for the taunts and instructions from my old Hearts Club Revisited script. After that i only need to write or import some taunts and instructions to get the example going. Because of that, i'm still optimistic to get v0.5 out before monday.
What do you think? Do you like that system?