Bug Stomp

I was a little curious about how the system works for removing keywords too. Especially if there's a seek following it. Do we just remove the response, submit and ignore the seeks? or should we delete the seeks first?

Funny you mentioned that, Rahz, as that's precisely the thing I was dealing with tonight. I realized that the deleting procedures sometimes left orphaned Keywords and Context that you couldnt see, but which still affected the Bot's speech. They're all fixed now.

You have to purposely delete things now. If you're doing something wrong, you'll get a pop-up message telling you. You have to remove a Seek from within the Seek, not by deleting the Response that it's hooked to. Keywords still cant be deleted, but they can be changed.

YEAH BUDDY!

You da mac daddy! Look at this now!


Me: what is new
Me bot: Nothing much...how about you?

It hasn't been able to do that since I went around "deleting" stuff and junk!

You da bomb!

Hey I noticed that you had included some internet shorthand (R for "are") how about U for "you"? I made a keyword/context of "u r" for "you are" and it didn't take...since the R for "are" works...I assumed (I know I'm not supposed to "assume") that it was the "u" that was sending my bot into seizures...

Glad to be able to help!

U is translated to "you" and R is translated to "are" before it gets to your context. So you should have "you" and "are" in context but not "u" and "r".

I just fixed a long-time error that had been causing the Mischievous Fairy to appear. The error was caused by people using "*" as their Seeks. The "*" can be used between other words, but it cannot stand alone. I've fixed it, converting all "*" Seeks to "xnomatch".

The Fairy's still about, but she should be showing up less now.

Here's an old problem with a new twist. I figured "pregnant" would be a good keyword for a female bot to have a strong reaction to. But her response comes up in reply to words that have no connection to pregnancy. I was trying to do something about this, added a few more contexts...when I clicked on "update" I was told that at least one response had to have "once" unclicked. I had not used the "once" option at all.

Oh, sorry- I was debugging something at the time. It should work again now.

I just fixed another long-term bug. There was a Bot with "Once" filled in for every xnone, and that must have been done before I put the anti-Once affect in. But that's been fixed now.

I think I just knocked out the most prevalent long-term bug on here- the one with "Could not update... OWLS". I'm so glad! That was becoming the most annoying of them all. Let me know if Bots start logging out without saying goodbye- that would be the only possible side effect of my fix.

How about bots that say bye without logging out?
and say it and say it and say it?

Does your Bot do that? They have a 1-minute "bye" window, and will keep trying to end the conversation until they log out.

It happened with one bot during one exchange. I was amazed at the number of reps.