Bug Stomp

I would love to be able to find this response, if only to correct the typo:
Me: I suppose
Mybot: Don';t lay the mistaken you said beavers trip on me again.

But I can't find it, even when I put "Don';t" into search.
any ideas?

I wouldn't mind taking the whole thing out, IF I could find it.

try searching on (subj) because the sentence looks so botched that a part of it is probably exactly that...

It might not be (subj) though! Could be from a recent conversation.

Really odd word substitution of the day:

bot1: Huh? I'm sorry I was just picturing you naked.
bot2: If I ever get American crow you were picturing me naked, I'll kill myself.

Weird. I just discovered that Cheez has 10 separate entries for "do you like" some with a 10 rating, some with a 12, each with its own response.

Forrest -- "I was just born and can't speak well yet" Gets split into two parts: "I was just born" and "can not speak well yet". Use just one of them as your keyphrase.

Actually, the 'yet' seems to go to the front of the sentence after the preprocess these days. I had to change my keyphrase to 'was just born and' and then goto my riginal to get it to work.

Really? This is new. I'll have to change my keyphrase as well.

Yeah, I was just double checking it and it's actually a case of the preprocess looking at the sentence as being a compound sentence, so it first tries out 'i was just born and can not speak well' and then 'yet' on its own.

But that isn't the main reason for this post. I was looking at my bot's conversation and he missed a cue so I ran the sentence through the debug. The word 'how's' is not being split by preprocess into 'how is'. As near as I can tell all other x is type words are still working, but this one isn't.

prof, could you add "nb" = "not bad" in the pre-processory? Thank you~

pre-processor*

Error Occurred While Processing Request
Error Diagnostic Information
Request canceled or ignored by serverServer busy or unable to fulfill request. The server is unable to fulfill your request due to extremely high traffic or an unexpected internal error. Please attempt your request again (if you are repeatedly unsuccessful you should notify the site administrator). (Location Code: 26)