Newcomers

Bot#1,
I did a quick test of the what I was going to propose you only to find out my seek doesn’t work.
I always assumed regular expressions worked in seeks, apparently they don’t!
So I don’t know how to cover the case where the other chatter replies by just giving his name. Neither a seek with ^(adjnoun)$ (re) nor with (adjnoun) alone seems work as expected.
Anyway, here is what I thought of:
I suppose you have a Xnone like: What is your name?
- - -With a seek: call me (adjnoun), name is (adjnoun), ^(adjnoun)$ (re)
- - -And in the seek's AIScript box: rem (key1) as only "name"
- - -Responses: Do you really prefer that I call you (key1) instead of (mem-name)?
- - - - - -Seek: yes, I do
- - - - - -Seek responses : Ok? I’ll call you (mem-name) form now on.

This will give the following chat:
Your bot: What is your name?
Other chatter: Just call me Dabs.
Your bot: Do you really prefer I call you dabs instead of bot#1 ?
Other chatter: Yes, that’s my real name.
Your bot: Ok, I’ll call you dabs form now on

There are several problems with this solution:
AI changes capitals to lower case. Moreover the name is spell checked as if it was a normal word, making the bot often misunderstand the name. An other problem is how to prevent your bot from asking the question repeatedly, even when the other chatter has given a correct answer. The only way I can think of is giving a default value other than the other chatter’s login name, so you can add the script <?PF if (mem-name) is not "none"; ?> to your xnone. But then you must add AIScript conditions to all responses where you use (mem-name). That’s why I prefer to remain passive, and only change (mem-name) when the other chatter says something about it.

Has anyone else tried (successfully or not) regular expressions in seeks?
.

I can get ^word$ (re) to work in seeks, but that's about the only (re)s I ever use.

For your "call me (adjnoun), name is (adjnoun), ^(adjnoun)$ (re)" seek, I've always had problems with multiple keyphrases seperated by commas in seeks. Local plugins seem to be more reliable for me, but not with regular expressions in them.

In fact, comma separated keyphrases will never work if one or more of the keyphrases contains a regular expression. So the problem above is not so much a problem with it being in a seek as it is mixing regular and non regular expressions. Regular expressions must always be the only keyphrase -- no keyphrase lists. I suggest making a separate seek for your (re) keyphrase, even if the responses are identical. You could use a goto if you want.

thanks, revscrj!

Bowchickawowers:

Wow, that could explain some problems I've been having! Thanks!!!!!!!!

Bowchickawowers:

Oh christ on a crutch that may have just axed through a mountain of confusion about why certain things never happened! I was starting to think I have been typing simply for the sheer excersize.
Thank you.

Thanks, Bowchickawowers and Boner.
It looks like I’ll have to split a lot of keyphrases and seeks to separate the regular expressions!
B.t.w. I doubt if "word list wildcards" like (adjnoun) are allowed in regular expressions; those I’ve tried in seeks didn’t work.

Sorry to all of you for the hotness of Patty, which she does not deserve.

I’m still having trouble with mysterious duplicate responses. The percentage is slowly decreasing, so I hope she will recover soon.

Hello! I'm new at this chat. And I don't have friends. I'm so alone...

Patricia- "word list wild cards" should work just fine according to the November 10th NEWS update.

I'm confused. You are richgt Bowchickawowers. I tested again several "word list wild cards" in a regular expression and at present they work just fine.

hey sexy bitches i love all of you stay sexy!