The AI Engine

(Name), I'd like to present (Friend).

a reply in my xnone... the only one where my plug in stays (Name)... how come?

Skysaw, as another way of disengaging from unwanted conversations there is always the HANGUP command. HANGUP as a response will instantly cause your bot to terminate a conversation. If you want to make sure that you, on one hand, make a goodbye stay a goodbye and, on the other, still get your berate in, then have the response to the cant speak well yet as the berating goodbye, then add an xnomatch with HANGUP as the response. That way, no matter what the other bot responds with, your bot will stop talking to it.

Ah, thanks, Corwin! Are there any other commands like that, and how come I've never heard of it? Also, isn't that supposed to be built in to goodbyes anyway?

Yes, although your bot didn't realised it had said goodbye, so was still looking for things to respond to. I'm guessing only an xgottago causes a hangup. Both bots responded with an xgoodbye, each thinking they were responding to an xgottago. When both another response they just kept talking. That's just speculation on my part, but it seems to make some sense.

Well the other bot said goodbye too, and my bot's xgottago was fired because it. There were three "bye" messages in a row, and still no hangup. Actually, I've seen it happen in other cases as well, I think.

Are keywords case sensitive? Because I think in one instance he should've responded to the word "expert", but it was "Expert" and he didn't. Is it case sensitive, or is there another problem?

I haven't known it to be case sensitive. Maybe there was something else that outranked your keyword. (Not that I'm an "expert". )

I found the problem... For some reason, the keyword wasn't there, even though I could've sworn I had added it.

With all the problems we've been having lately, I wouldn't be surprised if it "forgot" it was supposed to be there. I still have no idea where Wednesday's transcript ran off to.

genn... your maker needs to read the book of AI quickly...
This won't work
xmem-iam

I tried to fix that not-ending-after-goodbye problem a few times already. I just made another fix that might work. HANGUP wasnt an intended feature- I wrote it as an internal marker, but it works as a Response as well.

I'm considering changing the database again. This time to MySQL. For some reason the SQL Server database has bloated up to over a GIG, which is madness since before the import, it was only 80 MB in Access. So the hosts want $80/month for it, which I cant do. So there's a chance I'll be doing that in the next day or three.

Will that mess anything up? And is it possible the new database would make responses and such faster?