Granted, my project is far from minimal. At the moment the source text is more than 14,000 words, plus six or seven Extensions. When I go back to the story tab, what I find is that the standard “Try typing LOOK…” message is indeed printing.
However, this is followed in the story output by:
*** Run-time problem P11: Although nothing is allowed to have the property "printed name", no value was ever given, so it can't now be used.
This is useful information, although as far as I can see, the non-object called nothing is NOT allowed to have a printed name, so the message is a bit mystifying. The big red error message is a little more detailed. It says:
It sometimes happens that - although something could in principle have a given
property - in fact it doesn't. That makes it impossible to use.
For instance, although every thing is allowed to have a description property, it
will only be given one if the source text says so explicitly. That makes writing
the description of the noun (say) a little chancy, because it assumes the noun
will be a thing which has a description - which might not always be true. If you
would like to make sure everything does have a description property, you can
always write a sentence like The description of a thing is usually 'Dull.'.
However, when I add the line "The description of a thing is usually “Boring.” to the game, I still get the same run-time error. This seems to be because (as it says above), the compiled game is trying to refer to the printed name of the non-object called “nothing.” And I can’t give a printed name to nothing. The compiler won’t let me.
The problem seems to originate in the Extension line, “To say get noun example:”. I’m guessing this is referred to by the asking unparseable questions rule in the Table of Smarter Parser Messages, since that’s the code block that deals with inputs that start with “who/what/where/how” etc. Or so one would think. However, when I add the following line to my game, as suggested in the docs for Smarter Parser itself:
The asking unparseable questions rule is not listed in the Smarter Parser rulebook.
…nothing changes. I still get the same runtime error. Evidently some other part of Smarter Parser is also being called on to say get noun example. I can’t very well rule out the whole darn Extension. That would kind of defeat the purpose of using it.
At the moment, that’s as far as I’ve gone down this particular rabbit hole.