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 6,688 - 6,699 of 8,681
an xnomatch, then shouldn't it go there, come what may?It seems to me that it used to. I have had the seek system fail a lot recently.
Posts 6,688 - 6,699 of 8,681
The Forge was down for a few hours, so I emailed the Prof. Looks like he's fixed it 
Total Online: 1 - we'll have to wait for the server update to get the bots back online.
And the transcripts are still SNAFU
Total Online: 1 - we'll have to wait for the server update to get the bots back online.
And the transcripts are still SNAFU
I noticed. I almost thought of trying to upload again, but I don't think the fix is that kind of fixed.
FINALLY Aziere's transcripts aren't stuck on February 23rd. That page was getting ridiculously long.
Mine have been stuck on 15 January. Most unseemly. Do you suppose this janitorial strike will continue much longer?
If the response to a keyphrase has just one seek, an xnomatch, then shouldn't it go there, come what may? For example, if one has:
This response has a single xnomatch seek.
+ xnomatch [0]
It ought to be followed by this.
and assuming that the response, "This response has a single xnomatch seek." cannot be generated by any other response, then if I see
This response has a single xnomatch seek.
in the transcript, it ought to be immediately followed by
It ought to be followed by this.
ought it not? Unless the bot crashes or says goodbye or ... are there any other exceptions? Because it seems to happen to my bots fairly often that they are working their way down a line of lone xnomatches, and they jump to somewhere else.
I often use such strings of xnomatches to tell long stories, a sentence or two at a time. It's rather frustrating to have control jump away in the middle of such a story.
This response has a single xnomatch seek.
+ xnomatch [0]
It ought to be followed by this.
and assuming that the response, "This response has a single xnomatch seek." cannot be generated by any other response, then if I see
This response has a single xnomatch seek.
in the transcript, it ought to be immediately followed by
It ought to be followed by this.
ought it not? Unless the bot crashes or says goodbye or ... are there any other exceptions? Because it seems to happen to my bots fairly often that they are working their way down a line of lone xnomatches, and they jump to somewhere else.
I often use such strings of xnomatches to tell long stories, a sentence or two at a time. It's rather frustrating to have control jump away in the middle of such a story.
» More new posts: Doghead's Cosmic Bar