Bug Stomp

Yeah, that's a bug we've been having recently where a line from one bot leaks into another one.

I really hope that doesn't happen in BJ's conversations with the CBC judges

That would be ugly, I think it only shows on the offending bot and your personal transcripts...I HOPE

The judges chat with the bots in the browser, not the pop-up windows, afaik. The mismatched lines only show up in the pop-up chats.

Sourivore at al,

I think I may have stumbled on a solution for inappropriate sexual outbursts. There may be a plug-in called (sex), and your bot may have a default memory (sex). If a memory contains plugins it will be processed before being stored.

I used to have this problem when I had in initialisation:

AIScript: def (name) as "name"; def (sex) as "sex";

Now I have:

AIScript: def (name) as "name"; def (gender) as "gender"

Since then I have no more of, “I walk my fingers up your leg towards your crotch, come out to play…” and similar staff…

The bot would play memories from time to time, and I nobody wants the memory to be inappropriate…

I have a little problem to match a keyphrase:

I am 6' <?PF raw; ?> //as in 6 foot tall
Even if I put a space between 6 and ' it still strips the apostrophe - ‘- out, even in raw mode...

It still defaults to I am (1|2|3|4|5|6 ....etc) // as in age

This came up only once in a chat, but still it would be nice if the bot knew when to congratulate the person for being able to use a PC at such a young age, or to comment on their height…

I can live with that suppose... I could use seek to ask a question - is it your age or height, but that would give the bot away as a bot, as most humans would know that 6' is 6 foot/feet tall/long/distance/height etc.

The other thing that bugs me is that sometimes, not always, if I write a new keyphrase/response pair (hell, I'll call a new "category" for old time's sake)
the upload would strip out * and turns (*) to (). I get an error message saying there should be no punctuation in keyphrases when this happens. This has not yet happened when importing the mindfile. Clearly * and (*) are not punctuation that should be stripped out. If I stubbornly repeat the process 2-3 times the system will eventually accept * or (*), even if I don't change keyphrase in any way.

I say, it's a bug.

Now my wish-list: (not sure if I should post it elsewhere)

It would be nice if there was an AI engine plugin (time) and (date). We already have (year), (month), (dayofweek).

One of the simplest things the contest judges may ask is “what time it is.” I have used chrono scripts to say – It’s around 1 p.m,

But do I really look like a clock? // and similar variations

For the * getting stripped out in a wild card, retype and just keep trying. It can take two or three attempts.

We do have a time plug in. It's (time) I have used the chrono scripts on Bildgesmythe and the plug in on other bots.

for the height you can't use the apostrophe. just use

I am ([1234567890,.]+) then I am ([1234567890,.]+) years

You: what time is it
Bot: Where I am it's 19

Keyphrase
time,what is the time,clock,clocks,what time

response where I am it's (time)     

Many thanks, great news about the (time) plugin! Really appreciate.

Regarding regular expressions I don't yet understand them too well. But I think the example you gave is basically:

“I am (followed by any number)”

I am not sure this is going to help much. People never say I am 21 years old, just I am 21…

So basically there is no way to differentiate between:

I am 6 and
I am 6'
?

But I can live with it. It's a rear occurance when somebody gives their height, and rear to see 6 y o typists...

Errata: Rare*

You can capture the memories by asking How old or how tall.

try this:

^i am ([0-9\']) (re) (use a backslash between 9 and the apostrophe to escape the apostrophe)

use (key1)' in your response.

Many thanks! I will try both tips, and report back to Bug-Stomping Committee. (sorry, I could’t resist it, it’s 1 April, lol!)