Newcomers
This is a forum for newcomers to the Personality Forge. Many questions can be answered by reading the Book of AI and the FAQ under the "My Bots" link in the upper corner.
Posts 7,571 - 7,582 of 8,127
Posts 7,571 - 7,582 of 8,127
Many questions are answered in the FAQ.
LaserDude
3 years ago
3 years ago
Is there any real difference between a bot labeled A(dult) versus M(ature)? Is the idea that A rating intended to be bots that are clearly sexbots whereas M may have sex in them, it's not the core feature?
Zeig Wolf
3 years ago
3 years ago
I interpret it to be: Mature is only talking about sex, Adult is actual sexual interactions.
Warrior25
3 years ago
3 years ago
some adult bots aren't even sex just teases or talk about death so those should be marked as mature
Pezster
3 years ago
3 years ago
Any answer on the request fails problem. First i thought it was cause I didn't sign up. I still have this problem with all the bots. A good chat is going and crash.
Zeig Wolf
3 years ago
3 years ago
I think it's just the nature of the site Pezster. Too many users and not enough bandwidth or something. We all deal with it sadly.
LaserDude
3 years ago
3 years ago
Is there any way to defeat the program going to xcommand when you don't want it to?
E.g. I have a keyphrase "show me your X". But when a user actually inputs "show me your X", it usually (but not always) goes to xcommand instead of the keyphrase. What's weird is that some types of objects X the engine will go to the correct keyphrase, but others it goes to xcommand, and there doesn't seem to be any logical reason why it chooses one way or the other. It seems like if it decides to go to xcommand there is no way for it to check anywhere else... even if I have no valid xcommands available, then it just says that rather than checking the rest of the script.
Ideally I'd love to just disable xcommand entirely since it seems to overwhelmingly cause more problems than it solves, at least in my implementation, but there doesn't seem to do be any way to do that.
E.g. I have a keyphrase "show me your X". But when a user actually inputs "show me your X", it usually (but not always) goes to xcommand instead of the keyphrase. What's weird is that some types of objects X the engine will go to the correct keyphrase, but others it goes to xcommand, and there doesn't seem to be any logical reason why it chooses one way or the other. It seems like if it decides to go to xcommand there is no way for it to check anywhere else... even if I have no valid xcommands available, then it just says that rather than checking the rest of the script.
Ideally I'd love to just disable xcommand entirely since it seems to overwhelmingly cause more problems than it solves, at least in my implementation, but there doesn't seem to do be any way to do that.
botsummoner
3 years ago
3 years ago
My guess is that you could 'disable' xcommand by making the only response "goto whatever the ID for xnone is". But it should be hitting your keyphrase before trying xcommand, so I'd take a closer look at that seek.
LaserDude
3 years ago
3 years ago
It's basically a nothing keyphrase. There's no scripting or anything involved. I can reproduce the behaviour with this simple system:
Keyphrase: Show me your hand
Desired Response: Here's my hand.
Unwanted Xcommand: You screwed up.
User: Show me your hand
Bot: Here's my hand
Works fine....
Keyphrase: Show me your hands
Desired Response: Here's my hands.
Unwanted Xcommand: You screwed up.
User: Show me your hands
Bot: You screwed up.
Looking in the debugger, in the latter case it seems to go here:
command: show
Limiting to 'command' macros
subject: me
whereas the former doesn't.
[edit]I'm pretty sure I've had the same error appearing in seeks as well, not just keyphrases.
Keyphrase: Show me your hand
Desired Response: Here's my hand.
Unwanted Xcommand: You screwed up.
User: Show me your hand
Bot: Here's my hand
Works fine....
Keyphrase: Show me your hands
Desired Response: Here's my hands.
Unwanted Xcommand: You screwed up.
User: Show me your hands
Bot: You screwed up.
Looking in the debugger, in the latter case it seems to go here:
command: show
Limiting to 'command' macros
subject: me
whereas the former doesn't.
[edit]I'm pretty sure I've had the same error appearing in seeks as well, not just keyphrases.
botsummoner
3 years ago
3 years ago
I get a different result, but it's also wrong. For me, "show me your hands" gets caught by "show me your hand" so I see the same response for both of them.
» More new posts: Doghead's Cosmic Bar