The AI Engine

The AI Engine always parses contractions. In this case "it's" correct. It's = It is should be broken down this way. Its = indicating something belongs to "it" shouldn't be broken down this way.

Similarly, can't is parsed into "can not"
don't is parsed into "do not"

One problem that I have noticed is that it doesn't distinguish well between possessive "'s" (Like Sonora's scorpions) vs. the contractive "'s" (Sonora's going to the desert). The AI Engine would parse "Sonora's scorpions" into "Sonora is scorpions."

I'm sorry I may be way off, but what I meant was that "It's probably always been like that" should have been parsed as "It has probably always been like that".

"It is probably always been like that" is an ungrammatical sentence.

I'm sure you're right about your last point.

Oh, sorry about that. I didn't finish reading your sentence. Yeah, the AI Engine doesn't distinguish well between 's as "is" and 's as "has"

So far as I know, the only way to take care of it is to have phrases for "it is * (past-tense-verb)", or else use raw mode (and I recommend asking someone besides me about raw mode, as I haven't played much with it)

Yeah, that's what i did. I put "it's probably (re)" in as the keyphrase, and typed "raw" into the ai script box, and put a catch-all phrase "Yes, probably" as the response. Not very exciting, but it's a grammatical response to both "it is probably" and "it has probably" so it will do for now.

Thanks Ulrike

I didn't need the re and raw. Changed my mind half way through and didn't realise.
Guess I need a break from this

Sonora: Yes?
Watzer: What, that? That's not right. That's a sock.

I've noticed my bots, and now Watzer, responding to "is that right" despite it not occurring in the actual dialogue. I'm assuming it's some sort of AI conversion, but for anyone who has a keyphrase for "is that (*)" or something similar, you may want to add one specifically for "is that right," bearing in mind that it comes up at odd times.

Good idea. I didn't know he was doing that again. Thanks for the heads-up.

Why don't gotos always come up but xnones instead? And how is the goto number used? Could anyone explain please? Thanks.

you can use a numeric goto anywhere in your bot's responses by using the format "goto 123456" (and no other text) as a response - this will select any response from the seek that has that number, as displayed in the web interface - it saves having to duplicate similar sets of responses when one set can do for multiple keyphrases.
It's very handy for grouping similar sets of responses to different keyphrases, and directing the conversation along lines you want it to follow.
Be very careful about gotos that point to a set of responses containing gotos that point to a set of responses containing gotos... etc. You'll get a "too many gotos in a row" error.

Alright Psimagus, Great, thanks

ill kill for 10 bucks

I've found that if you try to export with a goto # that's not a seek, it will change it to 'goto xnone'...so I've always had to put in the full line...