Bug Stomp

Having a Keyphrase saying "take your hoodie off" in debug will trigger hoodie as _Hoodie_ as a female name. "Take off your hoodie" will work just fine. ^-^ Work around is adding _hoodie_ as a trigger, aka "take your _hoodie_ off"

is oxygen breathable is not triggering a response for the lilaith x chatbot

the single word breathable as a keyphrase does not trigger response for lilaith x.

for some reason typing goes to sleep only works for me.
when i type it into one of my chatbots.
what is causing that?

Bobstack, a seek only firing for you and not others implies it's related to memories not set, in my experience, though could be something with happiness. Does your go to sleep seek/KP/response have any memories referenced in the aiscript or the text? Are all of those initialized or certainly set beforehand? I had something similar when I botched initialization of memories due to working offline (why the flip that line has to have no escape characters, but they can be used - and I'm sure at one point had to be - elsewhere is a mystery).

i found out that i had set the responses for a certain time.
so i added more responses to be triggered to the times i did not have responses for.

my scripts for storing long term memories have stopped working.
one of them for the settings is default "blank" as "goodbye"
it is used to change the introductory saying to a different saying.

for hello urt the succubus chatbot says i have too many gotos in a row

That's generally a problem of not having any valid responses. Like when you have a 'if' statement but no memory set to trigger it.

that is supposed to be handled by xhello but it is not anymore.

Having these two keyphrases

Keyphrase 1:
(my name is|call me) *

Response:
"I'll call you (mem-name):
AIscript: rem (postkey) as only "name"

Keyphrase 2:
my * name (is not|isn't) *
AIscript: rem (name) as only "name"

Response:
"Oh, then what should I call you?" (Hanging question)




Normally if a user responds with anything like Lily/Bean/Tom/Jessy ect it'll trigger the 1st keyphrase, though if the 2nd keyphrase's has a number in its response, it'll completely negate the auto pickup to the first keyphrase. ^-^

For example:

"Oh, then what should I call you? :3 "

Registers the number as the hanging question~

Okay, so it turns out that the last part of the message that those seeks were hanging off is what was triggering those responses. My next question is why is that bit matching? I've tweaked the wording and it's no longer matching, but that's literally all I've tweaked.