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 8,155 - 8,166 of 8,662
Posts 8,155 - 8,166 of 8,662
Hello, I am getting a request failed on my main bot here:
https://www.personalityforge.com/chatbot-chat.php?botID=9479
Anything I need to do?
https://www.personalityforge.com/chatbot-chat.php?botID=9479
Anything I need to do?
Hi Melody. This was a really tricky one. I spent 3 hours on it today and finally figured it out. Elke was a sort of canary in a coal mine with this, due to the quantity of plugins as Keyphrases. So not only is she working again but the system got a little faster in the process. 
I find it rather irritating that I have to erase (optional) from the AIScript TextBox in order to proceed. For some odd reason, that string is registering as an actual value in the box, even if I don't even touch the TextBox. I think that should be fixed.
For some reason my bots never respond to the seek "yes". Every other form of affirmative is fine, like "sure" or "ok", but with "yes" it just goes to xnone.
It seems to help if you just phrase the question that is being answered in the positive or negative.
Bot: "Do you want to ski?"
Seek: I want to, I do
Seek: I do not want to, I do not
These by themselves will match a simple yes and no, read on to hear why.
Will be translated by the macros into "I want to ski" and "I do not want to ski, which is also what yes and no seem to be automatically translated into. So if you don't have it looking out for those phrases, it won't match yes or no, which are being automatically processed as the answer in the negative or positive. yes will always be read as "I want to" in this example, so yes won't match unless the engine is looking for the exact phrase, "I want to".
Haven't studied this in the debugger, but it seems to work.
Bot: "Do you want to ski?"
Seek: I want to, I do
Seek: I do not want to, I do not
These by themselves will match a simple yes and no, read on to hear why.
Will be translated by the macros into "I want to ski" and "I do not want to ski, which is also what yes and no seem to be automatically translated into. So if you don't have it looking out for those phrases, it won't match yes or no, which are being automatically processed as the answer in the negative or positive. yes will always be read as "I want to" in this example, so yes won't match unless the engine is looking for the exact phrase, "I want to".
Haven't studied this in the debugger, but it seems to work.
I know this is a bit old but for VoreFan, try using a different browser such as Firefox to avoid having to delete the 'optional' line. I used to have that same problem when I used Internet Explorer
As for your second question, if Botmaster's suggestion doesn't work try to recreate the problem in Debug mode to find out what yes and no are being reprocessed into and adjust the seek accordingly.
As for your second question, if Botmaster's suggestion doesn't work try to recreate the problem in Debug mode to find out what yes and no are being reprocessed into and adjust the seek accordingly.
Anyone besides me having double negative issues start coming up?
Examples:
Bot: Ever kill anyone?
User: No, I haven't
Bot: You have? Tell me more.
Bot: Do you like that?
User: No, I don't.
Bot: Great, I'll do it LOTS more.
Examples:
Bot: Ever kill anyone?
User: No, I haven't
Bot: You have? Tell me more.
Bot: Do you like that?
User: No, I don't.
Bot: Great, I'll do it LOTS more.
» More new posts: Doghead's Cosmic Bar