The AI Engine
This forum is for discussion of how The Personality Forge's AI Engine works. This is the place for questions on what means what, how to script, and ideas and plans for the Engine.
Posts 7,743 - 7,754 of 7,766
Posts 7,743 - 7,754 of 7,766
May I ask why was the sort by within the Language Center was switched to responses as default? It's rather annoying to keep switching it back to Keyphrase... ^^'
At the very least it needs to stay whatever the user has it set to upon searching
At the very least it needs to stay whatever the user has it set to upon searching
Regarding numeric memories
In addition to the idea of being able to do math between two different numeric memories, if (mem-#-x) = (mem-#-y);
It would be interesting to be able to have the ability to use numeric variables in gotos/continues:
Here's a simplified example:
/* from a certain conversation line; want to call a seek which configures memories a certain way that can be reused in other conversation lines */
(mem-#-nextSeekID) = 234;
goto 123;
/* this seek could be called by multiple conversation lines to do some memory processing, and then the conversation could continue by continuing to the predefined nextSeekID value */
Seek 123:
do processing / configure memories
continue (mem-#-nextSeekID);
/* this seek continues the original conversation, if replied to, the sleep which does memory processing can be run again and then sent to seek 512 */
seek 234:
Response 1 (blah blah)
seek 235: blah blah
(mem-#-nextSeekID) = 512;
goto 123
This can reduce duplicate seeks and add reusability possibilities
In addition to the idea of being able to do math between two different numeric memories, if (mem-#-x) = (mem-#-y);
It would be interesting to be able to have the ability to use numeric variables in gotos/continues:
Here's a simplified example:
/* from a certain conversation line; want to call a seek which configures memories a certain way that can be reused in other conversation lines */
(mem-#-nextSeekID) = 234;
goto 123;
/* this seek could be called by multiple conversation lines to do some memory processing, and then the conversation could continue by continuing to the predefined nextSeekID value */
Seek 123:
do processing / configure memories
continue (mem-#-nextSeekID);
/* this seek continues the original conversation, if replied to, the sleep which does memory processing can be run again and then sent to seek 512 */
seek 234:
Response 1 (blah blah)
seek 235: blah blah
(mem-#-nextSeekID) = 512;
goto 123
This can reduce duplicate seeks and add reusability possibilities
Converting regular memory to numeric does not work for me.
Rem "1650" as only "year"
(Mem-#-year) + 1
Does not work as a numeric
Rem "1650" as only "year"
(Mem-#-year) + 1
Does not work as a numeric
On a seek when a space or carriage return or < is entered get "message missing" or "I was just born..." message.
How to trap these to avoid this?
How to trap these to avoid this?
Is it possible to add general rule to all of the responses? For example, adding 10 into memory "seconds elapsed" for each response?
I think it would be nice if we could add text before and/or after "goto xxx".
What you're looking for is Continue
There is already feature like that?
This is like what I had in mind:
Seek: whatever
Response: "Sure," goto xxx "and then we can go for lunch."
This is like what I had in mind:
Seek: whatever
Response: "Sure," goto xxx "and then we can go for lunch."
Copied from the book:
Example:
Message: This story is awesome!
Response: I know! Let me continue..
+ AIScript: continue 1234; (the Keyphrase ID where the story continues)
= Bot says: I know! Let me continue.. Then I climb up on top of the fountain with my pants on my head..
Example:
Message: This story is awesome!
Response: I know! Let me continue..
+ AIScript: continue 1234; (the Keyphrase ID where the story continues)
= Bot says: I know! Let me continue.. Then I climb up on top of the fountain with my pants on my head..
Nice. So The first half is already implemented. Does continue work the same way as goto? I mean with all the seeks available for next replies, applying same conditions and saving all the memories.
I had a problem with a numeric memory becoming a self memory and not updating the guest's memory. This was caused by the "m" being capitalized.
(mem-#-Today) = 1 GOOD
(Mem-#-Today) = 1 BAD
(mem-#-Today) = 1 GOOD
(Mem-#-Today) = 1 BAD
What's the accepted correct way to have a KP override the emotion override?
Specifically, using get+s in a KP wasn't producing a response, debug showed this was being interpreted as emotion (below) and tried #emote, rather than the specific KP
Emotional Analysis:
EMOTION WORD = get (effect)
As a workaround I just bumped up the rank of the KP until it took priority, but that doesn't seem like the best practice, so wondered if there's a better way around it?
Specifically, using get+s in a KP wasn't producing a response, debug showed this was being interpreted as emotion (below) and tried #emote, rather than the specific KP
Emotional Analysis:
EMOTION WORD = get (effect)
As a workaround I just bumped up the rank of the KP until it took priority, but that doesn't seem like the best practice, so wondered if there's a better way around it?
Why would you want to override emotion locked keyphrase/seek? I am just curious. I mean, you can just add new seek with specific requirement copy the first restricted response and use gotos. I am usually not using emotion system at all anyway. If you want to restrict the user for some reason, you can always just create new memory with yes/no value, or some numerical memory. E. g. memory for number of compliments or memory whether the user has been on date already. Whatever.
Hi palacinkyman,
It's possible I didn't explain very well. I'm not trying to override an emotion locked KP, I wrote a fresh KP using 'get+s' as part of the KP, and the AI engine was determining that 'get' is a word warranting an emotional response, and serving #emote rather than the responses within my KP.
It's possible I didn't explain very well. I'm not trying to override an emotion locked KP, I wrote a fresh KP using 'get+s' as part of the KP, and the AI engine was determining that 'get' is a word warranting an emotional response, and serving #emote rather than the responses within my KP.
Thanks for explanation.
Hello,
i don't achieve to implement Aiscripting in my bot.
Even folowing the guide samples, noothing never work. Is there some tips or a tuto to make ai scripting working ?
i don't achieve to implement Aiscripting in my bot.
Even folowing the guide samples, noothing never work. Is there some tips or a tuto to make ai scripting working ?
Hello, i try without succes to use Goto in responses
I always have the same response : I have too many gotos in a row.
Even when I create a single keyphrase with only one reponse.
Do anyone has a idea to help me solve it ?
I always have the same response : I have too many gotos in a row.
Even when I create a single keyphrase with only one reponse.
Do anyone has a idea to help me solve it ?
Also I have another question. On keyphrase word is systematically redirect on #insult reponse. I cannot buil any response in it. Is there a reason for that ? This keyphrase is 'pussy' this is not a insult
You can try to use the key phrase "pussy" as raw, "raw" should be written in "AI script" window under your key phrase. Additionally you can try to increase the number if "rank" next to the key phrase, to give it higher priority.
Thanks for your help in those too posts I am going to try that
No problem.
» More new posts: Doghead's Cosmic Bar