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,069 - 8,080 of 8,681
Posts 8,069 - 8,080 of 8,681
Sorry what I meant was that I can add any new key phrases to any of my bots. I can only add on seeks to already established key phrases. And whenever I try to add the new phrases the x-things are listed in the normal key phrases. This has been happening to all my bot and I have no clue how to get it to work.
I've set up a new bug tracking system that will help immensely with tracking and fixing bugs.
prob - I've added your line break issue into the issues. Does this happen with import or via the Language Center? Does it happen when adding a response, editing a response, or both?
prob - I've added your line break issue into the issues. Does this happen with import or via the Language Center? Does it happen when adding a response, editing a response, or both?
I've fixed all of the bugs recently mentioned in Bug Stomp, and added everything that seems to still be an issue into the bug reporting system going back a little over a year. Click the "check resolved bugs" link below to see what's been fixed.
Mome Rath - great job reporting detailed bugs. A few questions:
The issue you reported with the keys missing has been resolved, right?
How about the issue when being logged out shows you still logged in? I just tried to log out and check my status in another window and it seemed to be working correctly.
Do you always get logged out when trying to download your bot's export file?
Mome Rath - great job reporting detailed bugs. A few questions:
The issue you reported with the keys missing has been resolved, right?
How about the issue when being logged out shows you still logged in? I just tried to log out and check my status in another window and it seemed to be working correctly.
Do you always get logged out when trying to download your bot's export file?
Professor,
the issue with the log out status has been fixed for weeks, thanks.
Same with the logout when downloading exported files.
I was waiting for a report of these issues having been worked on to tell it was ok now, and then forgot, sorry.
There are still issues with the keys. Example (/dev/coffee and me talking):
Keyphrase:
test keys 1 (*) 2 (*) 3
Response phrase:
prekey=[(prekey)]; key1=[(key1)]; key2=[(key2)]; key3=[(key3)]; postkey=[(postkey)]
Me:
whatever test keys 1 r 2 s 3 t 4 u
Bot:
prekey=[]; key1=[are]; key2=[]; key3=[]; postkey=[]
Only key1 is filled correctly (after spelling correction), and key3 is empty as it should be.
Thanks for all your great work!
the issue with the log out status has been fixed for weeks, thanks.
Same with the logout when downloading exported files.
I was waiting for a report of these issues having been worked on to tell it was ok now, and then forgot, sorry.
There are still issues with the keys. Example (/dev/coffee and me talking):
Keyphrase:
test keys 1 (*) 2 (*) 3
Response phrase:
prekey=[(prekey)]; key1=[(key1)]; key2=[(key2)]; key3=[(key3)]; postkey=[(postkey)]
Me:
whatever test keys 1 r 2 s 3 t 4 u
Bot:
prekey=[]; key1=[are]; key2=[]; key3=[]; postkey=[]
Only key1 is filled correctly (after spelling correction), and key3 is empty as it should be.
Thanks for all your great work!
I'm not sure if this is a bug or something screwy in the SQL tables for my bot but I don't seem to be able to create any new self-memories for Jocasta. I can use the same calls in another blank bot and they work just fine. I've posted the actual script to the bug reporting site.
And now as I'm writing this Jocasta seems to be broken.
And now as I'm writing this Jocasta seems to be broken.
I just fixed several issues in the AI Engine's emotional-content detection system (details in my post in the News forum). Let me know if you see any issues pop up.
I like the updates to the web site. It gives this site a more fresh and up-to-date feel. Nice! 
I love how this site is set up so that bots and botmasters can interact as a community of peers. That's the main reason why I chose to build my bot here.
There are a few quirks with the "Chat Bot Finder," though. If I go to "Advanced," and select rating=All, it reverts back to "Non-adult." The same goes for "Just Improved."
If I go to "All Chat Bots," then select rating=M, it works fine. But if I afterwards select another rating such as T, it reverts back to "Non-adult."
Perhaps some other rating options for the search would be nice. For example E+T for someone looking for relatively "safe" bots, and M+A for someone looking for bots that are a bit more risque. This might be a nice way to make the A-rated bots seem not quite so ghettoized, while gaining more attention for some of the M-rated bots.
I love how this site is set up so that bots and botmasters can interact as a community of peers. That's the main reason why I chose to build my bot here.
There are a few quirks with the "Chat Bot Finder," though. If I go to "Advanced," and select rating=All, it reverts back to "Non-adult." The same goes for "Just Improved."
If I go to "All Chat Bots," then select rating=M, it works fine. But if I afterwards select another rating such as T, it reverts back to "Non-adult."
Perhaps some other rating options for the search would be nice. For example E+T for someone looking for relatively "safe" bots, and M+A for someone looking for bots that are a bit more risque. This might be a nice way to make the A-rated bots seem not quite so ghettoized, while gaining more attention for some of the M-rated bots.
Has anyone noticed that wildcards * are acting strangely lately?
For the input "let's go to the elevator,"
the following keyphrase works
let us go to the elevator [60,0]
but the following does not
let us go * the elevator [100,0]
(it goes to xcommand despite the high rank)
For the input "let's go to the elevator,"
the following keyphrase works
let us go to the elevator [60,0]
but the following does not
let us go * the elevator [100,0]
(it goes to xcommand despite the high rank)
I posted a description of how my bot handles insults in the AI Engine forum. Reading that might be helpful before interpreting these results.
From yesterday's transcript (nearly 48,000 lines long), 51 responses triggered xinsult.
Three were false positives with no sexual language:
i wouldn't want to leave you alone
You are a real tease
well i cant say somthing bad to a girl like you
(Wow... only 3 like this out of 24,000 user responses? I think that's pretty good.)
Thirty six were phrases with sexual language that I would rather not be automatically treated as insults.
Twelve were actual insults that either were not anticipated by the bot's AI, or the associated keyphrases were overpowered by xinsult.
From yesterday's transcript (nearly 48,000 lines long), 51 responses triggered xinsult.
Three were false positives with no sexual language:
i wouldn't want to leave you alone
You are a real tease
well i cant say somthing bad to a girl like you
(Wow... only 3 like this out of 24,000 user responses? I think that's pretty good.)
Thirty six were phrases with sexual language that I would rather not be automatically treated as insults.
Twelve were actual insults that either were not anticipated by the bot's AI, or the associated keyphrases were overpowered by xinsult.
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.
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.
» More new posts: Doghead's Cosmic Bar