Bug Stomp

How do I get my bot to recognise a name then to use in a sentence? Im sure ive seen it done before, but cant figure out how.

Roob - under your bots settings, in the box next to AIScript Initialization, put the following:
default (name) as "name"
Then anytime you want to refer to the chatter by name, use
(mem-name).. such as

I remember you, you're (mem-name).

Doesn't he have to do a keyphrase "my name is, call me, refer to me as" with AI script:

If you use the AIScript Initialization, you don't have to wait - it will automatically assign the 'name' memory if it doesn't already exist.

I always thought it would redo it each time a chat started, but apparently it doesn't overwrite anything that's already there.

Darn, more trials with debug show that "Howdy" itself wasn't the problem (re: Message 4677).
It seems to be a combination of at least a couple things:
"Welcome", even with keyphrase: ^welcome$ (re)[50], is considered blab, and goes to xnone.
It also seems like if there is any blab at the beginning of the sentence, like "Howdy!" or "Welcome!" it makes "Have a seat" trigger xcommand. Otherwise, it triggers the "have a (noun)" keyphrase just fine.
I would have put examples, but transcripts from debug don't show up...didn't they used to?

By the way, is anyone else still having trouble with seeks not working?

Well, I have a problem importing and having seek responses maintain any AIScript after them if the response itself also has a seek. Some do and some don't and once I import, the ones that lost the AIScript in the import won't save any AIScript if I go back to the language center and try to add it. I type it, I click update, it goes through without any errors, but when I check it's gone again. And it's nothing fancy, just basic if male or female script. Then to complicate matters I tried to delete the seek and add it again in the language center with the script, but nope, that didn't work either. Ahh, well, que' sera' sera'.

Oh, and I also noticed yesterday that a yes seek does not reply to the word "sure" or "yea". I kind of thought it would and should...but what do I know.

I had trouble with AIscript disappearing on import yesterday when I hadn't structured it right. It looked right - but I'd put extra spaces in it that shouldn't have been there. I got no errors on import - but then I haven't tested it since then with the right stucture either...

Well, I feel terrible for bugging everyone so much, but does anyone else have a problem with the multi-word wildcards (such as adjnoun) not working? I could have sworn they worked before...

I've been having a problem with (adjartnounprep). When I have a keyphrase, for instance, "I like (adjartnounprep)" and the person says "I like a yellow lemon", the adjartnounprep only picks up "a" not "a yellow lemon". I haven't had a problem with (adjnoun) so far, so I've been switching (adjartnounprep) to (a|an|) (adjnoun)

Hmm...I haven't tested the multi-word wildcards in the keyphrase, but I do know in the response it doesn't come up. For instance, I just triggered a test keyphrase and the response I got was: Bot: I like a (adjnoun).

When you want to use it in a response, use (key1), assuming (adjnoun) is the first wildcard/phrase in parentheses. Example: In "how (is|was) * (adjnoun)", key1 would refer to is/was, key2 to *, and key3 to the adjnoun.

If you want the bot to come up with a random (adjnoun), use something like "I like (adj) (noun)". (adjnoun) itself only works in keyphrases, but (adj) will give you a random adjective and (noun) a random noun. Also, (object) gives a random object, and in most contexts makes more sense than (noun).