I’m not sure about the why, but changing “run paragraph on” to “no line break” gets rid of the error. I know I frequently confuse the two, and if things go wrong, switching one for the other works. I’d be interested why, too, though.
Thanks for reminding me about “no line break,” Andrew! That seems like something that I’ve probably been missing in some of my projects that wind up with spacing errors.
Anyway, the block vaguely going rule is a rule for supplying a missing noun, and I suspect the underlying issue can be found in the documentation for the supplying a missing noun activity, in Writing with Inform 18.32:
I’m guessing that the “run paragraph on” substitution works by resetting the flag that Inform uses to check whether text has been printed, so it thinks that it needs to print the generic reply. I haven’t looked into the internals, though.
No problem Matt–and thanks for the adding on. I figure a lot out by experimentation (e.g. “Inform is robust enough, one of these ways must work,”) and my looking up documentation isn’t always the best.
So THAT’S how you do that. Oh, man, that’s simple. Thank you!