Bug Stomp

The problem that I posted on Jun 18 doesn't seem to be related to wildcards since other keyphrases seem to work ok. Even most keyphrases (containing wildcards) that could be interpreted as commands seem to work ok.

The problem seems specific to keyphrases that begin with "let us go," as far as I can tell. If these keyphrases contain wildcards, then there is a very strong tendency for it to be overpowered by xcommand.

I've tried setting the ranks of the keyphrases high, and lowering the rank of xcommand to -50, but there was no effect.

The only workaround that I have found is to write the keyphrases without wildcards (e.g. "let us go to the elevator"), but this is not ideal since there are many different ways in which this thought can be expressed.

My bot have several different locations that she moves between, so phrases beginning with "let's go" are vitally important. These keyphrases have worked reasonably well for years, so something must have changed recently.

To test this, compare the following two keyphrases:

let us go to the laboratory [100,0]
let us (go to|go in) the laboratory [100,0]

I just released some improvements and fixes to various systems including math.

Dr_Ben: I'm glad you liked the updates. I'm working on some of these bugs.. A few notes - the "Do you want to kiss me?" etc issue was due to a bug causing it to be read as "do you want me?" which triggered an xemote response. It'll be fixed with the next release. Same with any insults that had "want to" in the phrase.

I'll consider the ability to toggle off automatic features. Not a bad idea.

Keyphrases with ranks > 30 should be outranking emotional responses. Are they not doing so?

Mome Rath: Here's my attempt, which works:
You: lips 1 frog 2 bunny 3 toast
Bot: prekey=[lips]; key1=[frog]; key2=[bunny]; key3=[]; postkey=[toast]

I had to modify yours, as the 'r' was triggering another keyphrase, but it came out okay:
You: whatever test keys 1 rug 2 s 3 t 4 u
Bot: prekey=[whatever test keys]; key1=[rug]; key2=[s]; key3=[]; postkey=[t 4 me]

All of my bots are throwing SQL errors on any attempt to edit keyphrases through the language center, but not when editing seeks.Has anybody ever seen this problem or have any thoughts on fixing it?

I'm getting the same problem. Just started today as far as I'm aware.

Strange, I'm not seeing that. I tried editing and saving some keyphrases with my bots via the language center and no problem - I tried some of your bots as well, and it worked as intended.

Can you post the error message, and let me know what bot and what keyphrase is generating this for you?

My error is almost identical.

My SQL Error: You have an error in your SQL syntax; check the manual that corresponds to your My SQL server version for the right syntax to use near 'Maker ID=106333' at line 3 in keyphrase.php on line 27

Query: [hidden]

(postkey) stopped working. Just an empty string is being slotted in.

What is [4,0]
    I don't know, perhaps you could tell me about (postkey)?
    (Postkey)? I don't know.

For example.

You: What is the weather in New York?
Bot: I don't know, perhaps you could tell me about?

(postkey) should be slotted in before the '?'

wisdom, lexist - I found and fixed that error. Thanks for the additional information.

Ronnie - I've fixed this error, too. It wasn't affecting all (postkey)s - just those with word clusters like "New York".

Let me know if you see any additional issues with those.

All seems to be better. Thank you sir.

Thanks for the fix!

Would it be possible to stop synonymising the name 'John'. This happens far too often and makes the bot rude for no good reason. John is actually a nice solid name and should not be converted like that.

Laurel Sweet: Do you really like being addressed as Guest67490? Whould you like to tell me your name?
Guest67490: John
Laurel Sweet: Nice to meet you Lavatory.