Bug Stomp

Ezzer - When I updated the goto system, I wrote a script to automatically fix all the ones that were still working. The weakness in the old system is that if you updated the target Keyphrase, the goto would break. The ones labeled "goto broken" were the ones that were broken for that reason.

Charles, I'd like to know more about this. Do you have a copy of the original bugged export file? I wonder if a particular text editor was having issues with some of the line feeds. If you have the original, or if someone else runs into this, please email me the problematic export file at benji@personalityforge.com. I've been using exports and imports without issues so I need an example of a broken one.

Since last night, many bots I have tried will give me "There was an error with this request.". I tried on different computers, my cell phone on my mobile data, while logged in or anonymous, those bots do the same.
Example: https://www.personalityforge.com/chatbot-profile.php?botID=69474

I'm having the same issue as johnnysebre, with random bots sometimes as well as favorited ones. For example: https://www.personalityforge.com/chatbot-profile.php?botID=3330 aka Little Mu. I have been using my Android (up to date) phone to get around on the site after the death of my laptop.

Yes, sorry. It was a bit of debugging code that I discovered and fixed last night. It should be working fine again now.

Yep, working again for me!

Same here, thanks.

Hello, I am getting a request failed on my main bot here:
https://www.personalityforge.com/chatbot-chat.php?botID=9479

Anything I need to do?

Hi Melody. This was a really tricky one. I spent 3 hours on it today and finally figured it out. Elke was a sort of canary in a coal mine with this, due to the quantity of plugins as Keyphrases. So not only is she working again but the system got a little faster in the process.

(adjective) plugin doesn't work anymore.

I find it rather irritating that I have to erase (optional) from the AIScript TextBox in order to proceed. For some odd reason, that string is registering as an actual value in the box, even if I don't even touch the TextBox. I think that should be fixed.

For some reason my bots never respond to the seek "yes". Every other form of affirmative is fine, like "sure" or "ok", but with "yes" it just goes to xnone.

Mine is inconsistent with Yes and No Responses. I'm hoping that gets fixed, as well.