I got your bug report, Adez, but I just sat down to my desk, and haven’t had a chance to read it yet. The current version of Program O isn’t quite as “newbie friendly” as I had hoped for, I’m afraid, and I’ve been seeing a pattern where certain settings have been “left out” during the install process, which causes the chatbot to fail to respond. This will be corrected in the future, where the install script will simply insert certain “default” values automatically, without requiring user input, but that can be changed in the admin interface. For now, though, let’s see what we can do to help.
First off, is your chatbot publicly available? It doesn’t have to be, but if it is, then I can usually see for myself what’s happening, and suggest solutions that are most likely to help. If you don’t wish to publicly release the URL, that’s fine, too. You can just use the “E-mail Dave” link below my avatar image, and send the URL to me, so I can investigate.
Anyway, here are some common settings that will affect the chatbot’s responses:
1.) Error Response Message: If this is left blank, and the chatbot encounters an internal error, it won’t return a response. The chatbot also uses this response if it fails to find a suitable reply in the database. I recommend using something like “I just don’t know how to respond to that!”
2.) Default Pickup Line Pattern: This is the category that the chatbot uses as a “fallback” if nothing else fits. The 2 most common patterns are “RANDOM PICKUP LINE” or “*” (without the quotes, of course). If you’re using any of the ALICE AIML sets as a “starting point” for your chatbot, then use “RANDOM PICKUP LINE”.
3.) Chat Lines To Display: This is probably the most common misconfiguration. If this value is left unset during the install process, it defaults to zero (0), which causes the chatbot to completely fail to respond. This value needs to be at least one (1).
Now, some settings that can help to make tracing problems with your chatbot a lot easier:
1.) Debug Output: Set this to “file” while working on your chatbot to create a “breadcrumb trail” that stores debugging information for each user. Once the chatbot is working the way you want it, this can be set to a different value.
2.) Debug Mode: This setting tells the script how much information to log. While troubleshooting your chatbot, set it to “show everything”, but be warned that this generates a LOT of information, so should never be used in a production environment.
Once all of these settings have been checked (and changed, if necessary), try your chatbot out again, and let me know what you find. I see that you’ve registered for the Program O forums while I was writing this post, so I’ll activate your account once I’m done here.