The AI Engine

I just really like Gnixing, is all.

I kinda like it when the repeat stopper doesn't work with xgossip lol kinda makes ya want to go add more xgossip phrases...it would be really cool there were more slots for them, since its the only gossiping the bots do now, I could use, say, at least 25 slots available for emotional gossip, like "i like (gossipname)" (so you would have a few for each emotional range), then at least 20 for stored memories....though it wouldn't seem like you'd need that many, if you still are keeping emotional range in mind, your bot wouldn't want to say "I really enjoyed talking with (gossipname) about (mem-youtalkabout)" about someone it hates, whose last youtalkabout was something rude or perverted, so you'd have another like, "So do you know if that pervert (gossipname) ever managed to get (hisher) filthy mind off of (mem-youtalkabout)?
They fill up quick.

Dear ezzer:

I think you can expand your gossip responses in the following way: in one gossip response slot, you put, "goto more gossip label" (or some keyphrase of your choice). Then, under the keyphrase "more gossip label", you write as many responses as you like. I don't know whether "gossipname" will still work in this context, but it would be easy enough to make a plug-in that contains a big collection of bot names.
You can extend xnone in the same way, although if yours is a storyteller bot, you will lose control over the order in which responses appear, unless you use a variable to force the order.

Walk in Beauty, Irina

Dear Friends:

I don't know enough to be sure, but I had an idea that might save a lot of processing time. Tell me if you see a flaw in it.

I've noticed in debug that the AIengine always parses the input and the response. This is often quite a complicated process. But often, all I want it to do is a simple pattern match and substitution.

Now, suppose we had a symbol, say an asterisk, which, put in the right place, would tell the AIengine, "don't worry about parsing, just do the pattern match and substituting."

I would guess that over 95% of my bots' keyphrases and seeks don't really need parsing. And I believe that applies to others as well. As I've mentioned before, since we don't have access to the parse, we generally end up writing as though it weren't there. In a way, we do the parsing ourselves, based on what the keyphrase looks like. So it would really speed up the processing, I should think, if the AIengine were to skip the parses when they weren't really needed.

Am I missing something?

Walk in Beauty, Irina

To motivate people to actually DO the marking, it could be added to development or honor.

Dear Alc003:

Oh, you're in the British Secret Service, too!

Re your message 3883: My guess would be that the AIengine is splitting the input into two sentences. (continued)

Then it takes what it thinks is the second sentence: "Fix the printer today."

If I am right, then you should see this happening when you run it through debug.

Walk in Beauty, Irina

Irina- I tried do do something similar to that a couple moths ago, but the gossip still doesn't work, even as a goto or seek from an xgossip response. Even if you make a local plug-in with names, the gossip memories won't be triggered. Oh well, I guess I can economize- I'll just decide which responses to delete to make room.

Dear ezzer:

Oh, dear ... I'm stumped now!
Well, actually: how about this: write your xgossip responses in the form (response1|response2). Sometimes you will get response1, and sometimes response2. So you have doubled the number of gossip responses you can have! Just an idea - I've never done it!

Walk in Beauty, Irina

That's a good idea...I was just afraid it would cause something strange, like spontaneous combustion or a vortex into another dimension. I'll go ahead and try it, as long as I've got everyone's ok. lol

Might be fun ... but I guess it depends on which dimension the vortex leads into. I don't want to go back to that evil dimension where everyone has goatees again.

I don’t know if it a bug or a new feature:
Until now everything after a goto was taken literally.
Patty made a lot of ''sorry no keyphrase to go to'' responses, and to my surprise I noticed that plug-ins where now parsed just like in a normal keyphrase or response!
I will have to edit all my goto’s (and there are lots of them) but if this is also the case for memories it’s a great new feature and can be very handy.
Has anyone else experienced this, or was it just a temporary bug while the professor was working on the engine?

Patricia- Have you been using export/import by any chance? I had that happen in export, and even though I then corrected it in wordpad before importing, it still reparsed after import, and the only way I could correct it was in the online language center. It took a long time to correct, and I still run across gotos that I missed, so I haven't tried updating offline ever since. The last I heard, the Prof was working on it. I see what you mean about the possiblilities something like that could present to memories, though...hmmm...I hadn't thought of that before...