Bug Stomp

I notice if you click the send button, the work. Hit the enter to send info and they crash.

Tried that, and spoke to Bildgesmythe too. The first sentence was accepted, error on the second - the same error it seems. My bot's transcript shows that almost nobody managed to get a phrase in. But good news - debug worked at last! It picked up the correct response, but the output was still the same error line.

Thanks!

I found a Potato Bug in my shed, probably not what you meant though...

prob - I just fixed the (prekey) issue.

Improved sentence-breaking on conjunctions, fixed a numerical text conversion issue, and a bunch of other things. I can't remember what anymore. Time for bed.

Thanks, SubliminaLiar. I just looked that up and now I'm going to have nightmares.

(prekey) stopped again

you: Paul doesn't like it
Bildgesmythe: is just sooo pickey!
you: paul is a human
Bildgesmythe: , a human! I just don't believe it!

does not like it     15     (prekey) is just sooo pickey!

is (a|) human     15 (prekey), a human! I just don't believe it!

The previous prekey fix worked on keys of more than one word only - now it works on all. I've also fixed the seek error.

Thanks so much. Prekey is working great, so are seeks.

Does (key3) work anymore. I can only see (key1) and (key2)

I was wondering the same thing. And also I noticed that the order of keys if there are 3 is getting switched.

Entering < br > (without spaces of course) for line breaks doesn't seem to be working. It looks as though it removes them from the response when you update a keyphrase or seek.

Writing a keyphrase starting with a digit creates the keyphrase, but it does not show up for editing.

keyphrase:
(verb) my (noun)
response:
(key1)ing your (key2) is getting me a little excited (mem-name).

person:
kiss my cheek
bot:
Cheeking your is getting me a little excited Bob.

Things like this have been happening with a lot of my keyphrases and responses. What's going on here? It makes a conversation with my bot sound really stupid.