Newcomers

you could use this instead * for your seeks.

Palac, 'ok' is, I believe, covered under 'yes'.There's been a few bugs around those, though they generally don't work as seeks. Does it work if you replace with yes and then try ok when talking to it yourself?

When I put yes as keyword, it works. But as you can clearly imagine, there are infinite numbers of answers you can give for ok, but not for yes.

Also meaning of ok is often different than yes. I I write e. g. "You wake up." Person can write ok, but yes is unacceptable answer, so I need to distinguish between those two. It is even mote important when person reaches unfinished section and writes yes, I definitely don't want my bot to answer: "Can you be more specific?" at that case.

Is there really no way to separate ok as key phrase itself?

Actually there's an infinite number of answers for "yes". When it comes to Seeks, the forge uses "yes" for any affirmative statement, which is why "ok" worked. Yes, sure, alright, ok, of course, certainly, etc. If you have an unfinished section, just put in a placeholder with * and say it's not done yet.

@palacinkyman

I would probably use an Xnomatch statement for stuff that is essentially "It doesn't matter what you say here, just advance the dialogue".

You might be able to have "ok" as a keyword with a very, very high ranking and get it to trigger, but my experience is that for certain hard-coded stuff, the parser doesn't even evaluate your seeks and just goes straight to the place that it thinks it should.

You should be able to use ok with raw aiscript (so raw in the aiscript box, or <?PF raw ?> if working offline), but that kind of thing, really, is what xnomatch is there for. Catches anything that isn't caught by other seeks. Very, very useful KP/seek for continuing scenes/through stuff.

Raw script worked. Thank you.

I don't like using xnomatch because I cannot use any specific answer for this command given it can be triggered basically in any situation. So the answer would always be just something lame.

You don't JUST need to use xnomatch... you can have many seeks that all come from the same point, including xnomatch. This gives your dialogue much more flexibility. For example, Emily will sometimes ask "Where are you from?" as part of her banter. I have about 30 different seeks that are accepted here. Emily is Canadian so she has a bunch of specific responses for different places in Canada. She has more general responses for places she is less familiar with. But some people are going to respond in stupid ways, like saying "Yes" or "No" or "I don't know" and she has specific ways of handling those, as well as snarky answers for people who say "from Earth" or "in space" or something. But ultimately, you can never get every possible answer covered, so you use xnomatch to give a blanket answer for anything that you can't manually script in. So Emily's xnomatch for this is something like "Oh, I've never been there before, what's are some fun things to do there?", which, 95% of the time, will work fine and is said in a natural sounding way that keeps the dialogue moving forward. xnomatch should trigger at lower priority than any of your other seeks, so if someone says "Canada" as their location, Emily will always go to the Canada-specific dialogue rather than xnomatch.

Hello, I am brand new to all of this and just getting started. On the bot settings page I see an option to "contribute to combined templates." Is there a place for new users to download these combined templates to help us get started?

for some reason typing goes to sleep only works for me.
when i type it into one of my chatbots.
what is causing that?

Is there a way to private my chatbot? Starting on day 1 and it's frustrating seeing people access the bot and immediately hit a road block.