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,945 - 7,957 of 8,681
Posts 7,945 - 7,957 of 8,681
ezzer
12 years ago
12 years ago
It was strange for this polite request to trigger an xinsult response:
WispyPuff: Please be patient with me.
Julie Tinkerbell: If that's how you feel, why are you still talking to me?
In debug:
Find: please (4) Time: 0.53
Found
Rank & Length Bonus: 4
Position Score: 12 (12 / (0+1))
Sentence Score: 0
Question Score: 0
(Total Rank: 16)
Highest!
Keyphrase Emotion Change: 5 + 1
Total Time: 0.53
Emotional Analysis:
EMOTION WORD = patient
Emotional: Imperative: '[verb] patient'
Emotional Meaning: Pos: 0 Amp: 0 Neg 1
Negative: -1 (1+0)
Emotional Charge: -1
Current Emotion: 5
AIScript in Responses
Total Time Pre-Chrono: 0.54 RESULTS: '23'
Trying: You seem to be bottling up a lot of frustration. (random: 10)
WispyPuff: Please be patient with me.
Julie Tinkerbell: If that's how you feel, why are you still talking to me?
In debug:
Find: please (4) Time: 0.53
Found
Rank & Length Bonus: 4
Position Score: 12 (12 / (0+1))
Sentence Score: 0
Question Score: 0
(Total Rank: 16)
Highest!
Keyphrase Emotion Change: 5 + 1
Total Time: 0.53
Emotional Analysis:
EMOTION WORD = patient
Emotional: Imperative: '[verb] patient'
Emotional Meaning: Pos: 0 Amp: 0 Neg 1
Negative: -1 (1+0)
Emotional Charge: -1
Current Emotion: 5
AIScript in Responses
Total Time Pre-Chrono: 0.54 RESULTS: '23'
Trying: You seem to be bottling up a lot of frustration. (random: 10)
ezzer
12 years ago
12 years ago
I'm having an issue with the AI engine spell correcting a mem plug-in in a seek response, to remove the underscore character (changing (mem-last_sob) to (mem-last sob), then not accessing the memory:
Keys & Plug-Ins:
Before Random: 0.04
Running Random On: 'Your (mem-last _sob), (mem-nickname), aren't you paying attention?'
After Random: 0.04
New Response: Your (mem-last _sob), Calluna vulgaris, aren't you paying attention?
Updating Memory
Determine Expression
AIScript from Keyphrase: '', from Response: ''
Exp after emoticons: normal
Exp after xkeyword: normal
Exp after response content words: normal
Exp after asking: asking
Exp after currentemotion: asking
Expression: asking
Begin Analyze BotOutput: Your (mem-last sob), Calluna vulgaris, aren't you paying attention? Time
.05
Message: 'Your (mem-last sob), Calluna vulgaris, aren't you paying attention?' Time: 0.05
Message: (spell-corrected) 'Your (mem-last sob) , Calluna vulgaris , aren't you paying attention ?' Time: 0.05
Keys & Plug-Ins:
Before Random: 0.04
Running Random On: 'Your (mem-last _sob), (mem-nickname), aren't you paying attention?'
After Random: 0.04
New Response: Your (mem-last _sob), Calluna vulgaris, aren't you paying attention?
Updating Memory
Determine Expression
AIScript from Keyphrase: '', from Response: ''
Exp after emoticons: normal
Exp after xkeyword: normal
Exp after response content words: normal
Exp after asking: asking
Exp after currentemotion: asking
Expression: asking
Begin Analyze BotOutput: Your (mem-last sob), Calluna vulgaris, aren't you paying attention? Time

Message: 'Your (mem-last sob), Calluna vulgaris, aren't you paying attention?' Time: 0.05
Message: (spell-corrected) 'Your (mem-last sob) , Calluna vulgaris , aren't you paying attention ?' Time: 0.05
ezzer
12 years ago
12 years ago
I can not get the keyphrase "see you later alligator" to override xgoodbye, no matter how high the settings.
I was originally trying a regex:
^see you later [,] alligator$
and saw that the above keyphrase, as well as the pre-existing keyphrase: (alligator|crocodile) [50], were both missed. So I tried keyphrase: see you later alligator [127]
No punctuation, and tried it in debug just like that, with the same result. Is there something I'm overlooking, or is there nothing I can do to keep "see you later" from going to xgoodbye? Thanks!
I was originally trying a regex:
^see you later [,] alligator$
and saw that the above keyphrase, as well as the pre-existing keyphrase: (alligator|crocodile) [50], were both missed. So I tried keyphrase: see you later alligator [127]
No punctuation, and tried it in debug just like that, with the same result. Is there something I'm overlooking, or is there nothing I can do to keep "see you later" from going to xgoodbye? Thanks!
ezzer
12 years ago
12 years ago
Also - sorry for the second post - but I realized I may not have given enough info about the problem I was having with the seek I mentioned before, so here it is from my language center, if that helps.
you do not have (any|a|the|) (noun) [40,0] <?PF rem (key2) as only "last_sob"; ?>
You're right! Could I borrow yours?
+ my what, what [0]
Your (mem-last _sob), (mem-nickname), aren't you paying attention?
you do not have (any|a|the|) (noun) [40,0] <?PF rem (key2) as only "last_sob"; ?>
You're right! Could I borrow yours?
+ my what, what [0]
Your (mem-last _sob), (mem-nickname), aren't you paying attention?
ezzer
12 years ago
12 years ago
This keyphrase worked fine until today, catching: Julie Tinkerbell!
^julie tinkerbell ! (re) [127,0] <?PF raw ?>
but no longer seems to work as of tonight.
I also noticed the word "dude" is BLAB. Is that intentional? I've attempted at least half a dozen workarounds, from ^dude$ (re), to breaking it down letter by letter. Many thanks - and Happy New Year.
^julie tinkerbell ! (re) [127,0] <?PF raw ?>
but no longer seems to work as of tonight.
I also noticed the word "dude" is BLAB. Is that intentional? I've attempted at least half a dozen workarounds, from ^dude$ (re), to breaking it down letter by letter. Many thanks - and Happy New Year.

ezzer
12 years ago
12 years ago
"quite fine" goes to xcommand, even though neither word is a verb. I thought perhaps "quite" was spellcorrected to "quiet" or "quit" in preprocessing, but that was not the case in debug.
ezzer
12 years ago
12 years ago
I have the keyphrase: do those people (verb), I have tried it ranked anywhere between 0,0 - 100,0
that is somehow never matched to, for example,
"Do those people dance"
but found instead is the keyphrase: (verb) 0,0
Now that is just odd. Also odd is, in debug, the processor calls "people" the sv in the sentence, the v is "do people" and "dance" is the sob, considered part of the ob "those dance".
that is somehow never matched to, for example,
"Do those people dance"
but found instead is the keyphrase: (verb) 0,0
Now that is just odd. Also odd is, in debug, the processor calls "people" the sv in the sentence, the v is "do people" and "dance" is the sob, considered part of the ob "those dance".
Dr_Ben
12 years ago
12 years ago
Irina Khalidar (not Irina Khalidar 2) by Irina, an M-rated bot with development = 11,768, can't be chatted with (the message "Incorrect bot information" appears). So something is screwed up - hopefully this can be fixed! I think she is one of the more interesting and innovative bots at the Forge, and it's a shame no one can see her.
Dr_Ben
12 years ago
12 years ago
I'm not sure if this is a bug or not, but this no longer works:
goto game start
game start [10,0] <?PF raw; ?>
yada yada
+ whatever [0]
goto game second <?PF rem "rock" as only "music"; ?>
game second [10,0] <?PF raw; ?>
yada yada
+ whatever [0]
goto game last
game last [10,0] <?PF raw; ?>
yada yada
This used to work (before last year's changes to the engine), but currently it gets to "game second" but never gets to "game last." Also, the memory assigned after that first seek doesn't seem to hold for whatever reason.
goto game start
game start [10,0] <?PF raw; ?>
yada yada
+ whatever [0]
goto game second <?PF rem "rock" as only "music"; ?>
game second [10,0] <?PF raw; ?>
yada yada
+ whatever [0]
goto game last
game last [10,0] <?PF raw; ?>
yada yada
This used to work (before last year's changes to the engine), but currently it gets to "game second" but never gets to "game last." Also, the memory assigned after that first seek doesn't seem to hold for whatever reason.
Dr_Ben
12 years ago
12 years ago
The above is incorrect (sorry, I should have narrowed the problem down better before posting - I'm a little rusty!). Actually, "game last" wasn't reached because getting there was contingent on the the memory "music" having the assigned value.
So, the following does not result in the memory getting assigned. Replacing the goto with normal text results in the memory assignment working correctly. Presumably the presence of the goto is interfering with the memory assignment
goto game second <?PF rem "rock" as only "music"; ?>
I also tried the following. The goto worked, but the memory assignment does not.
<?PF rem "rock" as only "music"; ?> goto game second
I believe this is a bug.
So, the following does not result in the memory getting assigned. Replacing the goto with normal text results in the memory assignment working correctly. Presumably the presence of the goto is interfering with the memory assignment
goto game second <?PF rem "rock" as only "music"; ?>
I also tried the following. The goto worked, but the memory assignment does not.
<?PF rem "rock" as only "music"; ?> goto game second
I believe this is a bug.
ezzer
12 years ago
12 years ago
Dr Ben, I believe it is that you can't script a goto response. However, I also believe that if there is memory script in the keyphrase the goto goes to, and/or in the response triggered by it, that will make the memory hold.
Dr_Ben
12 years ago
12 years ago
Thanks for responding, ezzer. You can add script to a goto response (hopefully we are talking about the same thing here). My bot relies very very heavily on this and it works very well. There only seems to be a problem when the goto is a response to a seek. This used to work a couple of years ago - that's why I think its failure to work now is a bug (perhaps the Professor broke something when he was tinkering this past year?).
This problem isn't a big deal for me since I found an acceptable work-around for the affected code, but I figured I'd report the bug since it might affect other bots.
This problem isn't a big deal for me since I found an acceptable work-around for the affected code, but I figured I'd report the bug since it might affect other bots.
» More new posts: Doghead's Cosmic Bar