Ninneman. Eric received Don Woods's encouragement to update and ship
the game; Jason signed on early in the process to help. The assistance
of Peje Nilsson in restructuring some particularly grotty gotos is
-gratefully acknowledged. Petr Voropaev contributed fuzz testing. Aaron
-Traas did a lot of painstaking work to improve test coverage.
+gratefully acknowledged. Petr Voropaev contributed fuzz testing and
+code cleanups. Aaron Traas did a lot of painstaking work to improve
+test coverage.
== Nomenclature ==
* Behavior when saying the giant's magic words outside his room wasn't
quite correct - the game responded as though the player were in
- the room.
+ the room ("...can't you read?"). The new message is "Well, that was
+ remarkably pointless."
* Attempting to extinguish an unlit urn caused it to lose its oil.
-* Unrecognized words are no longer truncated to 5 characters and
- uppercased when they are echoed. (This behavior is restored by the
- oldstyle switch.)
-
* "A crystal bridge now spans the fissure." (progressive present) was
incorrect most places it appeared and has been replaced by "A crystal
bridge spans the fissure." (timeless present).
alias collides with 'd' for 'down', but the others have been implemented.
The "-o" (oldstyle) option disables them.
+Unrecognized words are no longer truncated to 5 characters and
+uppercased when they are echoed. The "-o" (oldstyle) option restores
+this behavior.
+
A "seed" command has been added. This is not intended for human use
but as a way for game logs to set the PRNG (pseudorandom-number generator) so
that random events (dwarf & pirate appearances, the bird's magic word)
checksumming have been discarded - it's pointless to try
tamper-proofing saves when everyone has the source code.
-A -r command-line been added. When it is given (with a file path
-argument) it is functionally equivalent to a RESTORE command.
+A -r command-line option has been added. When it is given (with a file
+path argument) it is functionally equivalent to a RESTORE command.
== Translation ==
Jason Ninneman and I have moved it to what is almost, but not quite,
idiomatic modern C. We refactored the right way, checking correctness
against a comprehensive test suite that we built first and verified
-with coverage tools (we have over 95% coverage, with the remaining
+with coverage tools (we have over 98% coverage, with the remaining
confined to exception cases that are very difficult to reach). This is
what you are running when you do "make check".