|resources:||Home Installation Mailing list Source code Bugs Screenshots Nightlies|
|reference:||Roadmap Error messages Code overview Debugger (prototype only) Playthroughs|
A playthrough is a file which contains instructions about how to play a particular game. We use playthroughs for testing Gnusto releases. You may find all current playthroughs at $/src/tests/gamescripts in CVS.
A playthrough may be:
- For a particular architecture, or even a particular version of a game. Sometimes they will only have been tested with these versions.
- Made for a particular reason. Often the playthrough will have been created to test Gnusto's support of the architecture.
- For a game from a particular era: Infocom or modern.
- In playback or ini format.
- Playback (example of playback format)
- Playback is an older form: it's simply a list of commands which Gnusto can play back (as the Z-spec requires). You may run a playback file by passing it as an "input" parameter to Gnusto.
- Ini (example of ini format)
- Ini is a newer and rarer format which can specify what it means to win a game. It can also give instructions about how to run Gnusto, and can contain comments. You need to use the program $/src/tools/playthrough.py to run an ini playthrough; it requires Python. Ini files often begin as playback files.
|Balances||Fair-sized modern game||Both playback and ini; use the ini version for preference||Working|
|Zork 1||Infocom game, version 3||playback||Fails. Needs work.|
|Trinity||Infocom game, version 4||playback||Under construction|
|Hitchhiker's||Infocom game, version 5||playback||Fails. Possibly a terp bug. Tracking bug.|
The "gamescripts" directory also contains many playback-format playthroughs for some of the test stories that come with Gnusto.
Builders of playthroughs for Infocom games will probably find this set of human-readable walkthroughs helpful.