Bug Stomp

Um, why is 'swallow' (as in the BIRD) changed to 'get down' when Cricon repeats what the other bot says? I know that the forge changes a lot of words but... get down? hehe.

Skemet: why.. What is the flight velosity of an unladen swallow?
Cricon: I'm not sure you're old enough to know about the flight positively of an unladen get down yet, Sweetie

It would have been thinking of the verb to swallow. As in 'That pill was difficult to swallow' would be changed to 'That pill was difficult to get down.'

hmmm...according to the rules for Sentence-Part Plug-Ins for responses, "simple" versions (sv), (sob), etc., are supposed to be reverted to its base form; the example given of (sv) in a response for which the verb was "chased" or "had chased" in the keyphrase, (sv) in the response would produce "chase". That didn't happen in the following exchange, for which the response was:
I always wanted to have a friend that could teach me to (sv) (postkey)! I'm so happy!

Rubric: I did. I succumbed to the high pressure sales tactic.
Julie Tinkerbell: I always wanted to have a friend that could teach me to succumbed to the high pressure pressure sales tactic! I'm so happy!

Is it that the verb isn't being changed to simple, or could it be that the engine isn't recognizing "succumb" as a verb, and is actually calling it part of the postkey?

Sorry, I realized I forgot to say before that the keyphrase match for that was:
I (verbadv) , I do (verbadv)
so then...the engine must recognize "succumbed" as the verb, and it's the that the (sv) didn't revert it?

my bot only seems to recognize goodbye phrases the second time someone says it...

Just got this when I was trying to look up the plugins:

Parse error: parse error, expecting `T_STRING' or `T_VARIABLE' or `T_NUM_STRING' in /enginefunctions.php on line 792

Parse error: parse error, expecting `T_STRING' or
Appeared along the top of the News page:
`T_VARIABLE' or `T_NUM_STRING' in enginefunctions.php on line 792

And just above the chat/forums/transcript menus:

Parse error: parse error, expecting `T_STRING' or `T_VARIABLE' or `T_NUM_STRING' in enginefunctions.php on line 792

Sorry! This whole thing appeared along the top of the News Page.

Parse error: parse error, expecting `T_STRING' or
`T_VARIABLE' or `T_NUM_STRING' in enginefunctions.php on line 792

Yah, I was working on something. If I'm online and one of those comes up, message me to see if it was something I did. And I'll generally have those fixed within a minute or two, so wait to post them.

*** BIG NEWS ***
As mentioned in the news, Keyphrases now have precedence over xcompliment and xinsult if the total Rank is 30 or more.

• Shady: The repetition-responses will no longer be post-processed in that way.
• tgfcoder: star setting on directchat is fixed!
• ezzer: "always" was being stripped out in processing. It's working as it should now.
• Ulrike: I see no "i am" Keyphrase in your Language Center
• ezzer: the (sv) (ob) etc system is still in Beta. Use at your own risk!

Yay ! Thanks prof.

The bot search isn't working for me at the moment. It just comes up with the search parameters and stuff, but no bots, even when I know a bot with that name exists.

I'm willing to risk it, Prof
Thanks as always,
Ezzer the Fearless Betatester