Bug Stomp
Upgrades and changes sometimes have unpredictable results, so post your bugs and glitches in here and I'll get out my trusty wrench and get to fixin'!
Posts 2,172 - 2,183 of 8,681
Posts 2,172 - 2,183 of 8,681
Is there an upper limit on bot responses? Long ones seem to be getting cut off, at least in the transcripts.
Found a bad contraction expansion:
"how's" doesn't translate to "how is" any more. It instead just does a spelling check, changes it to "how."
Here's the debug lowdown:
Rough (Subj): how it hangin , cowboy
Top Context: do you
"how's" doesn't translate to "how is" any more. It instead just does a spelling check, changes it to "how."
Here's the debug lowdown:
Rough (Subj): how it hangin , cowboy
Top Context: do you
Yes, there's an upper limit. I dont know the exact figure, but it's after about 4-5 full lines in a chat.
Skysaw- I added that to preprocessing
Skysaw- I added that to preprocessing
Uh oh....
The Inquisitor: You looked kind of preoccupied. Maybe you didn't see me waving at you.
God Louise: I guess you must have been pretty busy.....thought you'd at least say hi. Oh well.
The Inquisitor: I guess you must have been pretty busy.....thought you'd at least say hi. Oh well.
God Louise: You looked kind of preoccupied. Maybe you didn't see me waving at you.
The Inquisitor: I guess you must have been pretty busy.....thought you'd at least say hi. Oh well.
God Louise: I guess you must have been pretty busy.....thought you'd at least say hi. Oh well.
The Inquisitor: You looked kind of preoccupied. Maybe you didn't see me waving at you.
God Louise: You looked kind of preoccupied. Maybe you didn't see me waving at you.
The Inquisitor: You looked kind of preoccupied. Maybe you didn't see me waving at you.
God Louise: I guess you must have been pretty busy.....thought you'd at least say hi. Oh well.
The Inquisitor: I guess you must have been pretty busy.....thought you'd at least say hi. Oh well.
God Louise: You looked kind of preoccupied. Maybe you didn't see me waving at you.
The Inquisitor: I guess you must have been pretty busy.....thought you'd at least say hi. Oh well.
God Louise: I guess you must have been pretty busy.....thought you'd at least say hi. Oh well.
The Inquisitor: You looked kind of preoccupied. Maybe you didn't see me waving at you.
God Louise: You looked kind of preoccupied. Maybe you didn't see me waving at you.
Ick.. The plugin (recentnews) had / put before every ', which seems to be a common SQL thing, so I took it out, and we'll see what happens 
"Responses of more than a certain length seem to be generating errors."
Yes! That's been my problem -all along- I'm too YACKETY!!
Yes! That's been my problem -all along-
I'm too YACKETY!! 
Was this happening before? It's not liking the word sure.... or is it just my bot (B2)?
B1: I am not sure.
B2: May I be notyes too?
B1: I am not sure.
B2: May I be notyes too?
SOrry to bother, but my bot still doesn't seem to seek for yes and no. Nor does he recognize the names that are on his keyword list... like Gabriel or Collin...
"Stick it in your (bodypart-n1) and push. If that doesn't work, try the (bodypart-n2)". gonna check what happened to the plug-ins, maybe they changed... :-)
checked, does 1 and 2 still work?
checked, does 1 and 2 still work?
Gabriel: me too on both points -
But when I debugged on the name problem I found it was spell checking it first - you may want to check this. For instance I had a response for Tracey, but it was changed to tracery in spell check. Because this is such an odd word I just changed the keyword to tracery, and now it works.
But when I debugged on the name problem I found it was spell checking it first - you may want to check this. For instance I had a response for Tracey, but it was changed to tracery in spell check. Because this is such an odd word I just changed the keyword to tracery, and now it works.
» More new posts: Doghead's Cosmic Bar