Bug Stomp

No, (subj) comes from input by whoever the bot is talking to. It is determined based on keyphrases; e.g. right before or right after the keyphrase. If the input has no keyphrase, then no (subj) gets defined.

than only if the Xnone is something like: huh? Or hmm..
...and most Xnones are complete sentences, like: I haven't a clue what you're talking about. Or: let's talk about something else etc etc

There are times when subj is lost in other keywords anyway, so I say let the botbuilder beware, but give them the power. If I use xnone to point to a set of responses that I know don't have (subj) in them, I'll be fine.

you can't use goto's in any of the xKeywords, or a chain of goto's, as well as a goto pointing to an x-Keyword

None of these will work:

Ex 1:
xFavorite: goto zJoke
Ex 2:
banana: goto fruit: goto happy
("banana: goto happy" would work though)
Ex 3:
banana: goto xNone

Okay, let me try once more. If I type a sentence to my bot, it looks for a kephrase that occurs in that sentence. If it finds one, (subj) gets defined from other words in my response that are near the keyphrase. If there is no keyphrase in what I typed, then there is no way to determine (subj).

and it selects an xNone.

Not true, a key phrase will get an answer from that key phrase, no matter if that answer uses * or subject.

Example: Bot 1: No!
Bot 2 (key phrase: no) will pick one of the answers in that key phrase, for example: yes! If there is a response like: no (subj), why not? Then I think that one won't be picked anyway, or will show as: no, why not?

it will show it as no, why not? because the subject is " " so the space just gets edited out in post-processing.

...point taken, what I wanted to say, having a possible (subj) or not won't affect a bots responses.

agreed

Which is exactly why it should be ok to use a goto in an x-keyphrase!

No, they still don't, though