Bug Stomp

That's probably it. I've updated the doctype declaration and the set the charset to ISO-8859-1 which should be the default and seems to be correct for displaying umlauts and the like. Do you see a difference?

Sorry, it is still not working. The charset is still missing in the popup windows.

(And there seem to be two spaces missing in the "big" pages, when I compare them to other websites; Firefox renders that source line in red)

Seems to work now. Thanks, Professor!

When the Forge initiates a bot chat while I am debugging my bot, the chat doesn't open in a popup window but replaces the debug window. (Occurs every time.)

-----

There is still a bug with special characters in popup chats.

The following characters are still not displayed in a popup chat, and suppress anything that follows on that line too:
Œ œ Å Ñ Ò Ó Ô Ö ×

There are no problems in normal chats and Flash chats, but in Debug those characters are replaced by white question marks on black squares in Firefox.

(I've looked at the UTF-8 representation of those characters - their second bytes interpreted as ASCII is something that might be interpreted as punctuation:

… ¼ ½ ‘ ’ “ ” – — )

Btw, I had to enter all those special characters as HTML entities in the edit box of this forum.

There is something I've noticed wrong about all the bots in that their conversation is now choppy, they cannot hold a specific topic nor can they interpret responses as responses, instead they view each user input as part of a new topic of conversation

I noticed that too Kenta. The bots will come up with phrases that doesn't even match any keyword what the guest has just typed. And I'm not talking about xnone phrases. It takes out a lot of the fun of programming the bots.

Could you give some examples? I just did some chatting and it seems okay. Also note if the chat was in directchat, flash chat, debug, or a pop-up message window.

I just experienced a plugin failure in a seek - in debug. It is a shared plugin and it is the list of plugins. I have not misspelled it - I copied and pasted it. It is not a huge array - some 20 words only. I try to overcome the problem by adding the most common words of the plugin individually to that seek.

Plugins in keyphrases work ok.

Sorry, false alarm. (plugins) work fine!

I had an errant script suppressing the response. It's not easy to hold multiple conversations with lusty lads simultaneously AND work on my mind-file.

Mome Rath, I think you are complicating thing a bit.

I may be just a dumb adult chatbot, but I have this keyphrase:

How many (*) in a pair, How many (*) in a couple [50,0]
    Trying to trick me? The answer is 2.
    Trying to trick me? Two.

Thanks for your advice, Laurel, that's what I considered to use as a makeshift as long as the bug isn't fixed.

But this was not my point, it was just the incident that notified me of the bug, that is, that (noun) and (np) don't work properly.

(The - meanwhile - minus one new messages are beginning to annoy me instead of just amuse me.)

Mome Rath,

I understand your frustration. I really do. I have these test keyphrases to enable the bot answer IQ-style math questions, like: "If I had 5 apples and I gave you 1 how many apples I would have left."

With the PF enhancer script I would be able to answer that, but the PF refuses to remember key1 and key2 in this case. I don't know what is wrong...
-----
a equals ([1234567890]+) and b equals ([1234567890]+) (re) [40,0] <?PF raw; rem (key1) as only "aVar"; rem (postkey) as only "bVar"; ?>
    a = (key1), b=(key2). OK
    a = (key1), b=(key2). I'll try to remember that.

This is what happens on debug.

You: a equals 6 and b equals 7
Bot: a =, b=7. I'll try to remember that.

Why is the PF refusing to set key1? Is this something that gets affected by regex/raw? Hmm.

    
how much is a (plus|\+) b [20,0]
    (mem-aVar) plus (mem-bVar)
    (mem-aVar) plus (mem-bVar)