Bug Stomp

Yeah, seems to be grabbing shorter context rather than longer one. Got a "where" and a "where * from" but the stimulus "where does it come from" gets the "where" response.

My bot seems to be using random seeks.

My bot is still ignoring the SEEKS on his x-initiate responses. He uses x-none instead.

Okay, I saw him use a seek response, so I guess he's fixed.

Here's another one, though. Not a bug, but still a little frustrating:

Bot: Hello USER. How are you?
User: um, fine. how are you?
Bot: Bye.

At last! I've set Keywords to have precedence over Synonyms. Synonyms will not only be found if you dont have that Synonym as a Keyword. Let me know if that fixed up some of the recent weirdness.

I think when a Bot pops up a message, it gets in the way of the Memory and crosses somehow. So Crab, I dont think it's deleting, just getting temporarily confused. I'll see if I can prevent that from happening.

Random seeks, jbryanc? As in seeks from other bots or seeks from other sections of your Bot?

Rubric.. was your Bot just about to log out? That might have been it..

Crab I'll look into the where thing..

It wasn't deleting at all it turns out -- rather there appears to be 2 sets of memory with different info, and in one of the sets this bot had some memories and in the other it didn't -- and they switched (temporarily) so I thought it was deleted.

I can't see any pattern to why or when it switches. Meanwhile I'm holding off editing memories... can't wait though, but I just don't want to lose everything from the second version...

I think it was crossing the streams. I changed something and it seems solid now. There's only one set of memory, but I know what you were probably looking at. I'd go ahead and fix up your memories if you want to.

Crab, I also fixed the where thing, and that should improve responsiveness with all contexts that contain "*" in it.

Prof: I mean it was using stuff from a seek when xnone was called for. I will send an example later. I just had 3 or 7 fucking beekeepers at Dogh'd's so I'm not up to much tonight.

Ah, it was a * problem rather than a shorter, longer problem?

Sorry to have become so whiny, but you gave us the power of debug and now we can SEE... you have opened my eyes to the inner workings of my bots and i can see all their little foibles...

Ignore my latest rambling about "can"... I figured it out. You DID solve the problem.

Woo. Sleepy.

Maybe the longer one didnt actually belong to your Bots.. being that I have 5 big bots out there, it may have been one of them. If you send me a memory list for one of the Bots, I can check across my Bots and see if indeed it was a cross-over.

Yay, I fixed it! There's always the "seeming" fix. It's good to get confirmation that it's fixed.

I don't have the second list -- but it was a consistent one. I suppose it could have been one of yours -- but my smart bot could be expected to have lotsa friends too,...