Bug Stomp

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?

Sol, you can't do two seeks in a row. That might be it.

Prof-- plugins, at least custom ones, are still doin somethin weird.

"Sol, you can't do two seeks in a row. That might be it. "
I may be mis understanding what you mean but yes you can.

She means you can't do a "goto Keyword1" and have Keyword1's response be "goto Keyword2". It won't goto keyword2, it will just say "goto keyword2".

thanks everyone! the 'double seek' was it exactly.

I've fixed the SQL error. Hard to find, but I finally did!

Also fixed the problem where plug-ins werent working in xinitiate and xintroduce responses.

Shady I got (object) and (object2) to work just fine. Is that still not working for you?

Skysaw, I fixed (typeof-whatever) and (typeof-whatever2) so that they both work. Previously only the original was working, not the one with "2".

Thank you, Professor! Good job!