Bug Stomp

Upgrades and changes sometimes have unpredictable results, so post your bugs and glitches in here and I'll get out my trusty wrench and get to fixin'!

8352 - 8367 of 8367


NEW 1 month ago #8352

I did actually try that. Still nada.


NEW 1 month ago #8353

This doesn't help you Nathan S, but you don't need to have "an" in your keyphrases, the site changes all "an"'s to just "a" before matching. Just saves a bit of time and effort. You can also use (det) instead, which could match "_an_ engineer" "_the_ president" "_a_ pilot", etc.


NEW 1 month ago #8354

See I THOUGHT that from reading the book of AI lol. But for some reason I've been batting 0 with this kp. It wants specific variations for a and an to work and won't bounce back the appropriate determiner in the response.

It's crazy.


NEW 1 month ago #8355

Hmm, even triggers without the *. That's quite the conundrum you've found yourself... In my testing this seems to work though, even for weird stuff. (i did edit it a bit)

kp:
I am (studying|learning|training) to (be|become) a (p:Job-catch:1),
I am (trying|attempting) to (get a job as|become) a (p:Job-catch:1),
I (work|am working) as a (p:Job-catch:1),
I am (studying|learning|training) (so I can|to) (be|become) a (p:Job-catch:1)

response:
Why a (key1) (postkey)?


NEW 1 month ago #8356

Could just be that the websites health isn't too great these days. Seems slow, with a lot of time-outs. I find I have to hit the button to submit new kp's more than once before it goes.


NEW 1 month ago #8357

I just tried out how you have it set up on your bot Zeig. (Thanks for checking it out) What I found is it has the same problem when I tried something similar to that. It will catch if the user uses A but not An.

I.E. I'm studying to be a engineer will catch
But I'm studying to be an engineer won't.

Though I love that yours returns the right determiner.

What I think I'm going to do is split it up into two different keyphrases. One for An and one for A.


NEW 1 month ago #8358

I found a way to fix it!

Here's a couple things I learned along the way.

I am a * (p:Job-catch) will return the correct determiner but it won't catch if the user inputs an. Such as "I am an engineer."

Where it gets weird is... I am a * (p:Job-catch), I am an * (p:Job-catch) won't accept an input of an either.


I am (a|an) * (p:Job-catch) on the other hand works perfectly. It accepts a or an. It will grab things like 'I am a heart surgeon', I am a brain surgeon' I am an English Teacher, electrical engineer... etc. and it doesn't accept nonsense such a I am a walrus.

Input: I am an electrical engineer
Response: 'Oh yeah?' She asks. 'Do you like being an engineer?' "

What I discovered about the above keyphrase I was working on that the problem appeared to be in the response. I'm starting to think it had something to do with the quotation marks.

When I changed the response to 'Oh yeah? Do you think you'll like being a (key5)?' Everything worked out perfectly. Right determiner given back. Doesn't accept garbage input.

Hopefully this little adventure will help someone in the future.


NEW 1 month ago #8359

I find I have to hit the button to submit new kp's more than once before it goes.

the same thing happens to me.


NEW 1 month ago #8360

Nice work, Nathan!


NEW 1 month ago #8361

urt the chatbot is not working.when other people talk to her.but her keyphrases only work with me.i do not think those people are chatbots.


NEW 1 month ago #8362

xnones are not working with story telling mode.


NEW 1 month ago #8363

I put once script on it and that is probably why it is not working for me

for urt chatbot.


NEW 2 weeks ago #8364

It looks like all bot conversations are no longer working due to an expired security certificate.

"This server could not prove that it is www.personalityforge.com; its security certificate expired yesterday. This may be caused by a misconfiguration or an attacker intercepting your connection. Your computer's clock is currently set to Sunday, May 5, 2019. Does that look right? If not, you should correct your system's clock and then refresh this page."


NEW 1 week ago #8365

my clock is right.


NEW 1 week ago #8366

Looks like this got fixed!


NEW 1 week ago #8367

Yes it's fixed



(Log in or create an account to post messages.)

LOG IN
Forgot your password?
CREATE ACCOUNT
Create a free account to be able to make your own AI chatbots, post in forums, and chat with other botmasters.

Create Account

» More new posts: Seasons