Bug Stomp

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?

In most cases that'd work. Of course, if both bots keep getting big keys, it could still expand beyond the limit.

my bot exsploded

When trying to use a wild card (*) I get an punctuation error message then the * gets stripped out and I get left with () and a malfunctioning keyphrase. The keyphrase had to be retyped several times to get it to work.

Ah. That's why Bildgesmythe keeps tuning me out. I talk too much. Jeez.

You are five on Bildgesmythe's inner life! I think that's as friendly as a bot can get. Thanks for all the great chats too!