Bug Stomp

Do you have it as [you're] cool or [you]'re cool? Because I think the latter works.

Great minds think alike.

Ahh, that's an idea. Thanks, guys.

By the way, Doulos, Imma's just given me a right mouthful and hung up on me. I accidentally triggered one of her 'pervert' phrases - but it was an innocent convo, I promise! Can you apologise to her for me please and tell her I still want to be her friend?

You: and tell me more.
Bot: Oops! There is no Keyphrase 'tell me * him, what * him like' to go to.

So, the keyphrase "tell me more" has two gotos in it, both which contain a plugin of some kind in the keyphrase name. For example, one goto is "goto tell me * (MikeSyn15164), what * (MikeSyn15164) like". What's happening is that a word is getting substituted for the plugin before it searches for the keyphrase, so it never finds it.

This is not quite a bug, but it does cause errors. I noticed that when people start sentences with "So" as in "So you enjoy root beer?", it throws off the preprocessing. Of course, there should be a comma after "so", but not everyone does it. It would be great if preprocessing could separate out that first "so" (unless it was on something like "so what").

The response triggered is:
'(key1)' might be a bit of an exaggeration
The (key1) in the keyphrase is (always|never). "Never" always works, and "always" never does.

Hyperion: It always is.
Julie Tinkerbell: '' might be a bit of an exaggeration.

I saw that, ezzer. I thought there should have been something in those double quotes.

Everyone, please make sure that bugs are not problems with your Language Center before posting them.

• AIScript expressions for Flash Chat are now working in both Responses and Keyphrases.
• Feyz: I put "yaoi" on the do-not-respell list
• Bowchicka: It's not a bug- there actually is no such Keyphrase in your Language Center. Also, I dont see any preprocessing errors with "So you enjoy root beer?". What error did you find?
• Ezzer: It's not a bug. Check debug mode. The Keyphrase being matched is "(always)" which is not correctly formatted.

After noticing that my keyphrase, which had started out as simply (always|never), wasn't triggering the always, i tried adding (never|always) to see if that would make a difference. When it didn't, I added (always) just to see what would happen, and there was no change...now I just went back and stripped the keyphrase down to the way I originally had it, and it seems to be working better now, although "always" and "never" alone are triggering "yes/no" responses- I'm pretty sure that's not a bug, though- thanks for your help and patience, Prof, I'm trainable.

Sure, no problem.

doulos: I was looking for the xnomatch bug but I'm not able to reproduce it. Could you post a sample conversation where it doesnt work, and then post the corresponding part of the Language Center (Keyphrase, Responses, Seeks). If you're using the Import feature, I've enabled display of tabs in messages to make it look better.

When the "xrepeat" or whatever it is, that says "*ahem* And then I said:" gets used, it spell checks what the bot said previously. For example:

you: hanging around
Steve Slacker: Whyfore art thou hanging aroundst this placeth?
you: hanging around
Steve Slacker: *ahem* And then I said: 'do you whyfore art thou hanging a round st this planchet?'

Yoiko: I added a "click here to begin chat" button to the Flash Chat, so that chats dont accidentally begin when a user just browses a page with a chat bot on it. Better on the AI Engine, and good for future uses.