Newcomers

woooow I lagged REALLY bad

Someone was probably doing an import. The new import should keep those lag bursts short.

I've done a quick clean-up of the plug-ins page. I removed the broken and useless plug-ins, updated the text, and changed the layout to fit the new design. I also added some checks to prevent some of the more useless plug-ins from being created.

Thanks prof ^_^

Hi!
I just created a new shared plug-in under "phrases". It is called (verb-qstart). It currently contains:

am,are,
can,could
did,do,does,
had,has,have,
is,
may,might,must,
shall,should,
were,will,would,

. These are all verbs one might start a question with, e.g., "May I go?" So for example you might write:

(verb-qstart) (adjartnounprep) (verb-trans) (adjartnounprep)

Yes, (key2) (key1) (key3) (key4)

For example, to the input

May the Mayor of London kiss the winner of the contest?

this would reply,

Yes, the Mayor of London may kiss the winner of the contest

.

Let me know if you see any errors or missing cases!

More precisely, they are auxiliary verbs.

Thanks for the cleanup, Professor!

Of course, some of the very same sentences could be exclamations:

May the Mayor of London kiss the winner of the contest!

Isn't English wonderful?

Professor, none of my plug ins are working.

Is there a way to write comments into a (downloaded) language center without messing it up?

Good question. My bits inside pointy brackets disappear--can you "//comment" in the pointy brackets and not effect any PF script?

For makers of bots too large to use the non-expert upload:

I got an error uploading "Irina Khalidar". As text it gave me "xnomatch [0]" and it said that it was wrongly indented or something. AAAIEEEEEEEEEEEEEEEE!!! There must be in the high hundreds of "xnomatch [0]" in "Irina Khalidar"! I'll give you my solution, though I hope one of you has a less tedious one!

I made a deliberate error of another kind and placed it in the middle of the download. I tried to upload it; of course I got an error. It was the old error, so I knew the old error must be above the new error. So I moved the new error up to 1/4 of the way through the file. And so on.

In general,

if you get the old error, that means that the old error is earlier in your file than the new error, so move the new error upward

if you get the old error, that means that the old error is later in your file than the new error, so move the new error downward

In this way you can bracket the old error with greater and greater precision until you know its location with enough precision that you can spot it.