| 1 |
======================================== |
| 2 |
Installing and playing games on Frotz || |
| 3 |
======================================== |
| 4 |
|
| 5 |
If you're unfamiliar with Infocom-style text adventures, you should |
| 6 |
probably stop here and read the file HOW_TO_PLAY. Then come back and |
| 7 |
continue. |
| 8 |
|
| 9 |
Now that you have Frotz installed, you'll probably want to play some of |
| 10 |
those ultra-nifty text adventures on it. These games come in files |
| 11 |
which are compiled programs that run on the Z-machine, which |
| 12 |
interpreters like Frotz emulate. The best-stocked archive of freeware |
| 13 |
games for use on Z-machine interpreters is the Interactive Fiction |
| 14 |
Archive at http://www.ifarchive.org. There are several mirrors of the |
| 15 |
archive all over the world listed there. |
| 16 |
|
| 17 |
Here are direct URLs to the zcode directories: |
| 18 |
|
| 19 |
http://www.ifarchive.org/indexes/if-archiveXgamesXzcode.html |
| 20 |
ftp://ftp.ifarchive.org/if-archive/games/zcode |
| 21 |
|
| 22 |
|
| 23 |
Here is the scheme I use for organizing my Zcode games: |
| 24 |
|
| 25 |
/usr/local/share/zcode This contains games written after the |
| 26 |
demise of Infocom. Most are freeware. |
| 27 |
|
| 28 |
/home/dave/.zcode I sometimes put games here too. |
| 29 |
|
| 30 |
/usr/local/share/zcode/infocom This is where I keep my collection of |
| 31 |
genuine Infocom games. |
| 32 |
|
| 33 |
/usr/local/share/zcode/infocom/sound Soundfiles from "Lurking Horror" |
| 34 |
and "Sherlock" go here. |
| 35 |
|
| 36 |
/usr/local/share/zcode/infocom/graphics Graphics files from Zork 0, |
| 37 |
Arthur, Shogun, and Journey go here. |
| 38 |
|
| 39 |
I add this command to my .profile file: |
| 40 |
export ZCODE_PATH="/usr/local/share/zcode: \ |
| 41 |
/usr/local/share/zcode/infocom:$HOME/.zcode |
| 42 |
|
| 43 |
Now, when I want to play Zork I, I will type "frotz zork1.dat" at the |
| 44 |
command prompt. Then I will then be told I am standing in an open field |
| 45 |
west of a white house which has a boarded front door. |
| 46 |
|
| 47 |
You can also just give a path to the game file. |
| 48 |
|
| 49 |
When you save your game, all save files are put in the current directory |
| 50 |
unless you specify a full path. Please name your saves intelligently. |
| 51 |
|
| 52 |
You MUST put sound and graphics in directories named "sound" and |
| 53 |
"graphics" in the same directory as the gamefile. Yes, this is a bit |
| 54 |
confusing. That's why Blorb will be so wonderful when Unix Frotz supports |
| 55 |
it. |
| 56 |
|
| 57 |
You'll probably want to make use of Frotz's new config file functionality. |
| 58 |
The options in the config file mirror the command line options and free |
| 59 |
you from having to remember to add something like "-Z0" to get rid of |
| 60 |
complaints about buggy zcode or if you want to always play with white text |
| 61 |
on black at a Linux console (instead of white on blue). Sample config |
| 62 |
files are included here as "frotz.conf-big" (which lists all possible |
| 63 |
options) and "frotz.conf-small" (a shortened one listing the more |
| 64 |
commonly-used options). The Makefile defines where Frotz will look for |
| 65 |
the frotz.conf file. By default, this is /usr/local/etc and can be |
| 66 |
changed at compile time if you like. This file will be read if Frotz |
| 67 |
notices you don't have a config file of your own in "$HOME/.frotzrc". |