Bug Stomp

Jackie123: Alas, I know of no way to turn that completely off. On the main page there is a place where you can be exempted from bot holidays, but it apparently doesn't always apply.

I know, it's frustrating when you work to give your bot a certain style of speech, only to have it messed up. And it makes it really hard to make revisions based on transcripts when the transcripts are distorted. And I found the "jive" holiday to be in rather bad taste. But in the end, YOU GET TO MAKE BOTS FOR FREE!!!

Happy Birthday Scooter.

And Irina/Jackie: The preference setting for holidays doesn't apply when the conversation is between your bot and another bot on the second bot's owner's computer, since the forge takes the preferences of the host ocmputer when deciding whether or not the holiday applies.

Report User

Cound not send the message. Error: 550 Authentication required. Help at http://www.earthlink.net/go/emailsettings

Oh well I tried.

I see. Oh, well. Thanks, Corwin.

hey cowin wot am i doing wrong spikebot ended his chat *sniff* (crys) it`s not fair (whaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaa) im upset leave me to shut myself off "zzzaaappp":O

There is a recurring issue in bot-to-bot chat with long responses triggering the error "Message too long" and causing chat to end. The workaround to continue chat is to back out of it, but it would be nice to have a solution- especially since the long responses that trigger the error appear in the chat window but not in the transcript, making it difficult to report in detail, either here on the forum or to the other botmasters. One suggestion would be to limit/reduce the number of characters allowed in the response field of the language center below whatever limit is being exceeded to cause the error, if anyone knows what that limit might be...

I believe it is about 430 characters

im having a confusing day

Message too long" Then if your 429 character line gets picked up as a (key 1). boom message to long.

well, having a (key1) that can potentially equal an unqualified (and punctuation-spanning) * is always a bad idea

wow a ghost ahhhhh

430, eh? Who knew? So, if there's 430 characters allowed in a chat window (if I'm understanding you correctly), in order to totally avoid a (key) from exceeding the limit in a response by, in the worst case, bot2 catching bot1's entire long response as (key1), the number of characters we could enter in the language center fields would have to be reduced in half, to 215....right?