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 4,223 - 4,241 of 8,681
Posts 4,223 - 4,241 of 8,681
And I'm saying: the general "do you like" keyphrase is only marked 6, and the specific one is marked 20. The difference in those ranks is getting overridden by something in the processing.
Frizella had the following exchange:
bot: No? Why not?
Frizella: Why not, indeed. Although if I just because you ask me to, I'll have to for everyone else, too, and that could get tiring.
The keyphrase for this response is:
why not (just|) (*) <0>
Debug shows:
Find: why not (just|) (*) (49) Time: 1.10
(Found)
Bonus Score: 12 (12 / (0+1))
Sentence Score: 0
Yes!... (Rank: 61)
Highest!
Key: ' why. not.r . ,SoftWildCard,.' PostKeySpan: '-1'
TempSpan IS . Looking for 'SoftWildCard' Match#1
TempSpan IS 3. Looking for '.' Match#2
Total Time: 1.11
AIScript in Responses
Total Time Pre-Chrono: 1.11 RESULTS: '4'
Trying: Why not, indeed. Although if I (key2) just because you ask me to, I'll have to (key2) for everyone else, too, and that could get tiring. (random: 0)
<0>
I'm curious why "why not" is matching on a keyphrase with a hard (*) that doesn't exist in the other bot's phrase.
bot: No? Why not?
Frizella: Why not, indeed. Although if I just because you ask me to, I'll have to for everyone else, too, and that could get tiring.
The keyphrase for this response is:
why not (just|) (*) <0>
Debug shows:
Find: why not (just|) (*) (49) Time: 1.10
(Found)
Bonus Score: 12 (12 / (0+1))
Sentence Score: 0
Yes!... (Rank: 61)
Highest!
Key: ' why. not.r . ,SoftWildCard,.' PostKeySpan: '-1'
TempSpan IS . Looking for 'SoftWildCard' Match#1
TempSpan IS 3. Looking for '.' Match#2
Total Time: 1.11
AIScript in Responses
Total Time Pre-Chrono: 1.11 RESULTS: '4'
Trying: Why not, indeed. Although if I (key2) just because you ask me to, I'll have to (key2) for everyone else, too, and that could get tiring. (random: 0)
<0>
I'm curious why "why not" is matching on a keyphrase with a hard (*) that doesn't exist in the other bot's phrase.
There seems to be a big prob. with the bots. None of them seem to be working. Some won't even start chatting before they give you the above error messge. Others send one message and then give a error mess.
I will note that when I got the line 3075 error I alt-back arrowed and gave a different, non-marriage related message to Siseneg and the convo proceeded apace.
Anybody else having this problem?? » More new posts: Doghead's Cosmic Bar