Newcomers

My seeks are working! My seeks are working! Hooray! [Leaps and dances about] thank you, world! thank you, Professor! Ah, life is good!!!!!!!!!!

Hey Irinia and psimagus,

I am back, just graduated from highschool, yays!
I was Gossypiboma before, then I took a leave for a couple of months to study. I also happened to loose the sheet of paper where I kept the password for my old screen name. I didn\\\'t put an e-mail account so I just made a new user account. I already removed the bots i was working on, and i had my notes written on paper, so it wasn\\\'t that much of a loss.

Oh and this time, i made up my mind on how i want my bot to be, so i\\\'m working on that. I also wanted to complete the idea i had before.

Oh and a quick question,
when a guest messages a bot, are they genderless or are they given a default gender like \"male\".

in some of my responses, i created a response for \"male\" and one for \"female\". I noticed that you don\'t have to pick a gender when creating a bot or user account. Would it result in a no response if there isn\'t a response that did not specify a gender? --and if that is true, is there a way to give them a default gender?

noob question: how do I get a contraction (e.g. It\'s) to output properly as a response? It always comes out as \"It\\\'s\", and appears in the Language Centre as \"It\\\\\\\'s\".

default gender like \"male\".
the default gender is female. For a long time all my bots registered as female, even the two males. It\'s fixed now. Thanks to the Professor, he can fix everything.

Re: contractions

As responses, contractions should be fine. It sounds like you mean as keyphrases. To catch "can't" the keyphrase should have "can not". To catch "don't" the keyphrase should have "do not". Etc. The AI Engine automatically processes out the contractions. Once in a while, it misinterprets possessive stuff as a contraction, too, though.

Bot1: "Dave's bike has a flat tire."
Bot2: "Dave is bike, huh? I didn't know that!"

Ah. The new server seems to be doing things a bit differently. I got a weird message when I tried to update one of Sonora's responses, with an output like this:
1: Oh, it worked soooo well that they had to call the (feds) to make it stop!
2: Oh, it worked soooo well that they had to call the (feds) to make it stop!
3: Oh, it worked soooo well that they had to call the (feds) to make it stop!
Old: 'Oh, it worked soooo well that they had to call the (feds) to make it stop!'
New: 'Oh, it worked soooo well that they had to call the (feds) to make it stop!'
1: Did what work?
2: Did what work?
3: Did what work?
Old: 'Did what work?'
New: 'Did what work?'
1: Well, of course it (worked|didn/'t work).
2: Well, of course it (worked|didn/'t work).
3: Well, of course it (worked|didn/'t work).
Old: 'Well, of course it (worked|didn't work).'
New: 'Well, of course it (worked|didn/'t work).'
UPDATING
1: Dunno. D/'you think it worked?
2: Dunno. D/'you think it worked?
3: Dunno. D/'you think it worked?
1: Let/'s hide behind a (object) and find out!
2: Let/'s hide behind a (object) and find out!
3: Let/'s hide behind a (object) and find out!

And a whole bunch of blank 1.,2.,3.'s follow all that, since she only has five responses. However, when I checked the language center, the apostrophes were there without any extra slashes. *shrugs* If the slashes show up in responses in the language center, post an example. If they show up in the Keyphrases, that's normal. (Actually, those were backslashes, but they didn't seem to show up, so I changed them to forward slashes)

New server? You mean that\'s not a grammar link thing?

Doh! News page. Yipee!

I do mean specifically in responses (I\'m not that much of a noob ). For now, I\'ve given up and resorted to leaving out apostrophes.

It was working for me three hours ago with apostrophes. *shrugs*

Checking now: don\'t, can\'t, shouldn\'t

Yes, it\'s working now. Now I have to go back and correct things

thanks prob123.