zarf: Just saw your message on posting. I think the attached files should do it. [EDITED to actually attach the files.] The source file is “source.txt.” I’m compiling under 6L02.
I’m not sure whether the problem occurs for everyone. Looking at the transcripts I got it’s only in some of them but some (probably all) of the transcripts are of earlier versions of the game. I’ve only got feedback from one person who I know to be using the release build, and it’s happening for me with the release build.
Jim: Well, it’s not actually the for-release code (I don’t have any “not for release” code as such, unless it’s in an extension), because the for-release code shows up in the release-for-testing build and the bug doesn’t. So it’s somehow being bypassed by whatever allows “rules” and “actions” to be run in testing builds, or caused by whatever Inform does when it creates a release build rather than a testing build (or rather by some interaction of the code with the aforesaid).
Also the bug appears to be happening somewhere between the parser and the action generation. I put in this:
[code]First for supplying a missing noun:
say “Supplying a missing noun rules running on [the player’s command] for [the current action].”;
continue the activity.
This is the print action check rule:
say “The current action is [the current action].”
The print action check rule is listed before the declare everything initially unmentioned rule in the turn sequence rulebook.[/code]
and the output in the release build is:
…this at the first command prompt after an initial yes/no question, so there wasn’t a stray going nothing action left over from a previous turn. (In the IDE version I get “the current action is waiting” twice and then the final message, which is what I’m supposed to get.)
Which makes me think that maybe instead of the standard rules I’d need to be putting debug statements into the parser, and that’s not something I know how to do, or particularly want to learn.
Some of the extensions and kludges I use hack things up pretty bad, I guess, but why would they hack things up in release builds and not testing builds?
Terminator code and extensions.zip (37.5 KB)