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"

@VioletGhost

yep, it was finally resolved a few months ago. also, welcome back! your bot was one of my favorites back in 2017. really good work.

Thanks @getcy I am happy you like my bot a lot! I will work on her some more as it has been some time since I last updated her

my AI actually increased the day after it was only because the site went down at midnight

can somebody help me with this "I have to many gotos in a row"

Everything, it happens sometimes with gotos. It will always happen if there's a goto pointing to another goto (even with the secondary goto being in another reponse, I think); sometimes it happens on other gotos, though, and I'm not 100% sure why. It's never happened on any of my more complex series of gotos for me, so I've always sorted it by just duplicating the goto'd branch and using gotos from the seeks instead.

it is fixed I had the wrong emotion set for it lol

I've been trying to talk to tessy, keep getting a "request failed" and losing progress. Anyone know what's up with that?

keyphrases trigger for me and not for people talking to lilaith x

RRRRRRRRREEEEEEEEEEEEEEEEEEEEEEEEEEEEEE

Bobstack, do they trigger if you chat without being logged in? I suspect you've got similar issues to the ones I had - bad initalization of memories. Might be one or two places where you've typoed the memory name, but niitialization is my suspicion.

what do you mean by initialization?

I mean the area in the settings - or the top of the file - where you initialize memories. Settings page, about halfway down, AIScript initialization. Stuff like def "21" as "playedAge" or similar; I'd been working offline and using escape chars on the initialization, so def \"21\" as \"playedAge\", for example, which doesn't work in that segment, though it works for the rest (but is optional these days). That being wrong would lead to the AIScript being fine for you if you've been running through other stuff that would set it, or had it remembered from before anything broke, but broken for new or not logged in people, and if AIScript isn't set, it won't trigger responses.