Seasons

Thanks Psi. Did anyone DL Nick who is willing to compress it (zip, rar, whatever) and email him? It's not a big deal, but I missed my chance, and I didn't realize he used a neural net at the time. Now, too late, I am more curious.

Then again, the SL chatters would still all have the same IP right Psi? Do I still need the complex identity memory thing?

I don't know. it's a good question, and probably depends on where the bot is deployed. I don't know how the server farms allocate IP#s, and whether it's the same on mainland and estates. Certainly it is not going to distinguish between individuals it's talking to, but the IP# might not be entirely consistent even for one bot permanently installed in one place. The IP# could change after region restarts, or even randomly, so you might need even more complexity than having them all Guest153 requires.
I'm afraid the Forge was never designed to be (ab)used in this kind of a mashup with a 3rd party virtual world!

Maybe a simple auto reset between guest 153 chats so we don't have to hand clear memories would help?

It would be even better to get the distinct IPs back (I'll hassle the Prof about it once the Loebner's over.)
You can reset memories between chats in the 'AIScript Initialization' of course, and it's not too arduous. Just a matter of adding a line there for each of your memories. And once that's done, you can forget about it.

OK Pis, what line do I add to make them reset between each guest chat? I' don't' see it in the book of AI (sorry if I missed it).

PS It's not abuse--it's development! PF 2.0 and all that (unless it bothers the prof and then I'd stop--seeing as I'd have no choice)

OK Pis, what line do I add to make them reset between each guest chat? I' don't' see it in the book of AI (sorry if I missed it).

Just fill each memory with a blank in the AIScript Initialization box in the bot's settings:

default "" as "nickname";
default "" as "hasdog";
default "" as "likesShakespeare";

etc.

You don't even need to use the {?PF tags if you do it there, rather than in xhello/xintroduce

Even though the IP number doesn't change, the AIEngine will re-initialize these when any new conversation starts.

but, if I understand you correctly, it will be a clean slate - it won't carry anything over from previous chats with the same person.

yes. Wasn't that the intention, Bev?

Yes, that was what I wanted. I'll try it, but I don't understand why default "" as "name" resets when default (name) as "name" doesn't. The way I have it set up now, guest153 stays the last mem-name recorded until someone says "I am not QM, I am KZ"

I see. I thought you wanted continuity for each guest.

that would be very difficult. But this would at least avoid memories trailing across a succession of visitors (all with the same "Guest153")

Bev, the original author of Nick has another site that I found that has a copy of Nick you can download: http://www.freewebs.com/colonel720/artificialintelligence.htm

Yes, that was what I wanted. I'll try it, but I don't understand why default "" as "name" resets when default (name) as "name" doesn't.

(name) isn't a user-editable memory - it's a plugin that takes a defined value from the AIEngine. So default "" as "name" won't work. My solution is to make all references to mem-nickname instead. It starts off defaulting to (name) as "nickname" (because the Guest153 problem is more recent, and I haven't got round to adding conditional filters to deal with them simply,) but can be changed if people say "call me..." or "my name is..."

The way I have it set up now, guest153 stays the last mem-name recorded until someone says "I am not QM, I am KZ"

I'm very surprised even then that it will change, but it would be considerably more stable to use a different memory name.