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 7,781 - 7,795 of 8,681
Posts 7,781 - 7,795 of 8,681
When the bots start chats with each other they only use endless x-initiate statements like "Hi, How are you?" "Hi Wanna chat?" "Welcome, nice to see you again ..." Their entire conversation is made up with statements like that. I always end up killing their talk when the box pops up ...out of mercy.
(Sometimes they say "I have too many gotos in a row" too in a bot-to-bot chat.)
Seeks don't work; they run into BLAB.
xmemory is triggered sometimes even if no memory is set. (ok, you could say, then give your bot a default response for this case, which is probably the best advice here.) (And bots with the default xmemory response seem to say "I remember you. You're." without filling in the (mem-youare).)
Number parsing still doesn't work. "three hundred one thousand" is transformed to "1300". (Maybe it would be better to deactivate this feature until it is fixed.)
In the transcripts, the names of the chat partners are missing.
Seeks don't work; they run into BLAB.
xmemory is triggered sometimes even if no memory is set. (ok, you could say, then give your bot a default response for this case, which is probably the best advice here.) (And bots with the default xmemory response seem to say "I remember you. You're." without filling in the (mem-youare).)
Number parsing still doesn't work. "three hundred one thousand" is transformed to "1300". (Maybe it would be better to deactivate this feature until it is fixed.)
In the transcripts, the names of the chat partners are missing.
I have a plugin of Mayan gods in one of my replies, and decided to add their names seperately in the keyphrases with appropriate explanation. For some reason, one of the names, "yum kaax", always triggers the xnone.
XXXX: What else does it have to show me?
Madame von Scam: Not very much. Oh, maybe this. You will meet a interior decorator with a cueball who will reveal himself to be a descendant of Yum Kaax.
XXX: Kinda farfetched. Who is Yum Kaax?
Madame von Scam: *stirs her cup and arrogantly ignores you*
I tested without the capitals as well, and also tried to insert the key phrase in raw mode.
XXXX: What else does it have to show me?
Madame von Scam: Not very much. Oh, maybe this. You will meet a interior decorator with a cueball who will reveal himself to be a descendant of Yum Kaax.
XXX: Kinda farfetched. Who is Yum Kaax?
Madame von Scam: *stirs her cup and arrogantly ignores you*
I tested without the capitals as well, and also tried to insert the key phrase in raw mode.
I'd advise to try a debug, but the debug feature seems to be broken too. Only about the first third of the page loads; it stops at
Found Stored Response Object
PreSerialize: 0.05
PostSerialize: 0.05
Total Time: 0.05
-------------------------------------
chrono: hour has a problem with time spans where the beginning and the end have the same hour number.
(I've inserted spaces after the colons between hours and numbers to prevent character seqences to be transformed into smileys.)
<?PF chrono: hour(23: 00-23: 59); ?>
is rejected with the message:
ERROR: The second number in the hour span should be more than the first. Use 24-hour time notation. 4PM would be 16: 00.
I can use (22: 59-24: 59) in this case, but what about (19: 15-19: 45)?
Found Stored Response Object
PreSerialize: 0.05
PostSerialize: 0.05
Total Time: 0.05
-------------------------------------
chrono: hour has a problem with time spans where the beginning and the end have the same hour number.
(I've inserted spaces after the colons between hours and numbers to prevent character seqences to be transformed into smileys.)
<?PF chrono: hour(23: 00-23: 59); ?>
is rejected with the message:
ERROR: The second number in the hour span should be more than the first. Use 24-hour time notation. 4PM would be 16: 00.
I can use (22: 59-24: 59) in this case, but what about (19: 15-19: 45)?
Keyphrases starting with a caret (^) (used in many Regular Expressions) are still not shown in the language center. (In a search, the caret is sorted in after the letters.)
After a search, the last clicked link to a keyphrase group is still inactive.
RomulusKesher:
I've given my bots a test keyphrase for spelling correction; the spelling correction and preprocessing transforms 'Yum Kaax' to 'Kaax'. Either use this in the keyphrase, or use a Regular Expression.
(A Regular Expression might look like this:
(who|what).*yum kaax(re)
)
After a search, the last clicked link to a keyphrase group is still inactive.
RomulusKesher:
I've given my bots a test keyphrase for spelling correction; the spelling correction and preprocessing transforms 'Yum Kaax' to 'Kaax'. Either use this in the keyphrase, or use a Regular Expression.
(A Regular Expression might look like this:
(who|what).*yum kaax(re)
)
Don't forget to use the raw with the regular expression. If all else fails try
[y][u][m] [k][a][a][x] (re) [45,0] <?PF raw ?>
[y][u][m] [k][a][a][x] (re) [45,0] <?PF raw ?>
What Mome Rath said - look in Debug for how it is spell corrected, i was able to make Sublimunse respond to a few sentences in Dutch by taking the spell corrected gibberish and using these as the KPs.
Sorry for the issues this week. There are two things behind it - first, the big reworking of the AI Engine I did basically touched every bit of it, and so some issues I didn't catch, and the other is that I'm working on a Turing Test Booth for an expo on Consciousness. I'll post more on that in a few days. In the meantime:
* Debug - working again
* Direct chat - working again
* I fixed an issue with word-type wildcards in Keyphrases
* Seeks - working again
* Fixed an issue where the special keyphrase "haha" wasn't working
* Now the special keyphrases "yes", "no", and "haha" can work when in a Keyphrase list.
* Removed the post bar from post editing page
* Bot-to-Bot Chats - working again, no xinitiate problems
* Flash face chat - working again, no xnoneitis
* Transcripts seem to be recording names correctly now
* Keyphrases starting with the following regex characters now appear on the screen that contains the parenthesis: ([^.*. Alphabetically, the carat appears at the end of the list.
* After searching the language center, all top nav sections to keyphrase groups are available now
* I see all the keys working - prob if you run into another issue of a missing (key2), let me know and post the keyphrase and conversation example here.
I'll update this post as I fix the rest.
* Debug - working again
* Direct chat - working again
* I fixed an issue with word-type wildcards in Keyphrases
* Seeks - working again
* Fixed an issue where the special keyphrase "haha" wasn't working
* Now the special keyphrases "yes", "no", and "haha" can work when in a Keyphrase list.
* Removed the post bar from post editing page
* Bot-to-Bot Chats - working again, no xinitiate problems
* Flash face chat - working again, no xnoneitis
* Transcripts seem to be recording names correctly now
* Keyphrases starting with the following regex characters now appear on the screen that contains the parenthesis: ([^.*. Alphabetically, the carat appears at the end of the list.
* After searching the language center, all top nav sections to keyphrase groups are available now
* I see all the keys working - prob if you run into another issue of a missing (key2), let me know and post the keyphrase and conversation example here.
I'll update this post as I fix the rest.
Mome Rath - I always have heard "three hundred and one thousand" rather than "three hundred one thousand". Is that a regional thing to leave out the "and" in larger numbers? I've never heard it that way.
» More new posts: Doghead's Cosmic Bar