Newcomers

This is frustrating to read... Again, there is no rule against making money with your bot. While it would be nice to pay the site if you're making money, there is no rule for that either. in fact, the opposite is true:

"Independence

The Personality Forge and I are independent contractors, and no agency, partnership, joint venture, employee-employer or franchiser-franchisee relationship is intended or created by this Agreement."

There is also the sites API, which is the sites intended and sole means for making itself money. You are not required to use it if you are not bringing your bot off-site.

There is no reason that any of you, could not have pay-walled content on your bots. Make money from your work. Get rewarded for your work. Or earn the funds to start your own website for your bot, and pay the forge for the use of the API.

I know some of you feel it's in bad taste, or poor faith. But you're thinking with feelings, not logic. Calm down a little, there's no reason to become incensed because someone is doing something you don't agree with. Especially, again, when it's not against the rules.

WOOOO

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?

I interpret it to be: Mature is only talking about sex, Adult is actual sexual interactions.

some adult bots aren't even sex just teases or talk about death so those should be marked as mature

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.

FUCK ME DADDY

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.

well congrats on signing up though now bots can remember you much easily

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.

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.

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.