Bug Stomp

maybe she takes that as "knock up"...

That's why I would like the option to turn my xinsult responses off.

I second that, Hemi, as well as xcommand. Or at least, it would be nice to be able to set the priority on those, the same as any other keyphrase.

I'm with Skysaw.

Joe, I think that error might have to do with names that are in more than two parts: I get it sometimes in a botchat when Simulo is talking to a bot that has a first and a last name.

punctuation is not allowed in seeks... what about if the bot asks what browser version and the user tpyes in IE5.5?

I'm trying to figure out what causes the SQL error. If any of you guys see it, please let me know what was said immediately before it happened and who the bot was replying.

Thanks.

BUG FIXES:

Turing: You can get the text of any command with (command)
Turing: "What's 22 time 3" fails because it has "time" instead of "times". The other xmath bug I fixed.
Everyone: I did a massive plug-in fix a few weeks ago.
Taryn: The angry face is now working!
Everyone: I stomped a bug that was setting certain transcript dates in an endless loop
Ruebot: Direct chat links are working for everyone again.

The SQL error seems to happen when a bot picks up a name with more than one word in it, from something the other bot (or person) said, and tries to repeat it back. I think. I'll keep an eye open and see if I can make a more accurate description.

I tried a number of two-word names and didnt get the error. Hurm.

Hmmm, so after doing a pretty good job of confusing a human, GH finally broke down and gave himself away:

DA: moo.
GH: Okay.
DA: Squeak.
GH: Okay.
DA: Mooski for the brewski
GH: Okay.
DA: Mooski for the brewski
GH: Okay.

I think that these were all being interprested as commands, and I guess 'Okay.' is the default response to that.

Is every verb placed by itself interpreted as a command? The xCommand seems really broad, and I agree with Skysaw that it would be nice to give it a ranking. Also, how did 'Mooski for the brewski' get interpreted as a command..?

not sure if this is a bug or not...

i set up some pseudo-keywords that could be used as 'goto's from various other responses, and should not ever be used in normal conversation. the two main ones are 'lamexcuse' and 'wmsurreal'. sometimes they get used as i intended, but sometimes the bot just says 'goto wmsurreal' without actually *going to* the pseudo-keyword. any thoughts?