From 2e6654e14922d35af465e5e09ecca4afe2b5de8a Mon Sep 17 00:00:00 2001 From: Eric Swenson Date: Tue, 7 Mar 2023 12:42:03 -0800 Subject: [PATCH] Updated zork documentation for old and new zorks using heasm66's recommendations. --- Makefile | 2 +- build/timestamps.txt | 8 +- build/zork.tcl | 5 - doc/cfs/madadv.doc | 331 ++++++++++++++++++++++++++++++++++ doc/cfs/madadv.help | 19 ++ doc/cfs/madadv.info | 34 ++++ doc/madman/madadv.help | 391 +++++++++++------------------------------ doc/madman/madadv.info | Bin 1798 -> 1498 bytes 8 files changed, 490 insertions(+), 300 deletions(-) create mode 100755 doc/cfs/madadv.doc create mode 100755 doc/cfs/madadv.help create mode 100755 doc/cfs/madadv.info mode change 100644 => 100755 doc/madman/madadv.help mode change 100644 => 100755 doc/madman/madadv.info diff --git a/Makefile b/Makefile index 61bfb61c..379d34eb 100644 --- a/Makefile +++ b/Makefile @@ -53,7 +53,7 @@ DOC = info _info_ sysdoc sysnet syshst kshack _teco_ emacs emacs1 c kcc \ aplogo _temp_ pdp11 chsncp cbf rug bawden llogo eak clib teach pcnet \ combat pdl minits mits_s chaos hal -pics- imlac maint cent ksc klh \ digest prs decus bsg madman hur lmdoc rrs danny netwrk klotz hello \ - clu r mini nova sits jay rjl nlogo mprog2 mudbug + clu r mini nova sits jay rjl nlogo mprog2 mudbug cfs BIN = sys sys1 sys2 emacs _teco_ lisp liblsp alan inquir sail comlap \ c decsys graphs draw datdrw fonts fonts1 fonts2 games macsym \ maint _www_ gt40 llogo bawden sysbin -pics- lmman shrdlu imlac \ diff --git a/build/timestamps.txt b/build/timestamps.txt index e7377797..c75221f0 100644 --- a/build/timestamps.txt +++ b/build/timestamps.txt @@ -115,6 +115,9 @@ cent/tapes.howcpy 198702122140.48 cent/tapes.method 198808122342.43 cent/tapes.save 198912211754.13 cffk/cpoly.64 198112010719.13 +cfs/madadv.doc 197904051732.50 +cfs/madadv.info 197903170902.45 +cfs/madadv.help 197903170900.49 cfs/zork.2 197902132100.56 channa/logout.times 199008150019.00 channa/nampic.bag 197611120605.59 @@ -1634,9 +1637,8 @@ macsym/script.aux 198103051328.01 macsym/script.begin 198311170637.53 macsym/script.intro 198311170643.35 macsym/trhook.fasl 198103091334.34 -madman/madadv.help 197801242321.29 -madman/madadv.info 197706132325.56 -madman/madadv.save 197801281445.07 +madman/madadv.info 197706071315.19 +madman/madadv.help 197801242021.28 maeda/yow.14 198902071550.43 _mail_/bboard.info 198404291701.28 _mail_/*msg.exp 199001302026.07 diff --git a/build/zork.tcl b/build/zork.tcl index 257c8aef..3b5c325c 100644 --- a/build/zork.tcl +++ b/build/zork.tcl @@ -20,8 +20,3 @@ respond "*" ":xxfile lcf;zork log_lcf;zork xxfile\r" expect "Job XXFILE interrupted: .VALUE;" type "\033p" expect ":KILL" - -respond "*" ":link cfs;madadv help,madman;\r" -respond "*" ":link cfs;madadv info,madman;\r" -respond "*" ":link cfs;madadv doc,cfs;madadv help\r" - diff --git a/doc/cfs/madadv.doc b/doc/cfs/madadv.doc new file mode 100755 index 00000000..431806af --- /dev/null +++ b/doc/cfs/madadv.doc @@ -0,0 +1,331 @@ +ZORK User Information + +I. Getting a ZORK + + a. ITS: Say ZORK^K to DDT rather than :ZORK to get a zork. + b. 10X/20X: Invoke the local dungeon (usually ZORK.EXE) + +II. Bugs, comments, suggestions... + + Always welcome and encouraged. All mail should be sent to + ZORK@MIT-DMS. ZORK has a BUG command, in addition, which + may be used to report strange happenings. Its use is described + below. Please note that for 10X/20X systems, net mail to ZORK + will be acted on much more quickly than BUG command reports. + + If, in making a bug report, you know what symptoms were exhibited + by the program, PLEASE, PLEASE!!!!! include them. It is at best + extremely irritating and at worst useless to receive a bug report + like 'mumble frotz' loses, or 'try saying \"mumble frotz\"'. With + such reports, we have no way of knowing the situation when your + 'mumble frotz' lost, and no way of knowing if any bug we manage + to reproduce (if we do) is the same one you saw. In consequence, + everyone's time is wasted. + +III. Typing to Zork. + + A number of characters in Zork have special effects. These + include a number of line editing commands. The characters are: + + or : delete the last character typed + : delete the last word typed + or or : delete the entire buffer + : redisplay the buffer + : redisplay the buffer. Sometimes this also clears the + screen. + + : terminate commands + : flush long typeouts + : like the QUIT command (vide infra) + : Causes the remainder of the command line to be ignored. + This may be useful for annotating hard copies/scripts of games. + +IV. Garbage Collection + + Zork may occasionally type out a message 'GIN FREE STORAGE- + GOUT TIME=10.92'. This indicates that a garbage + collection is occurring. We have attempted to prevent this, since it + may take a significant amount of real time on a loaded system; should + it ever occur, please send mail to ZORK@MIT-DMS describing the + circumstances -- how many moves have been made, whether a RESTORE has + been done, and so on. THIS IS NOT FATAL: after the GOUT message is + printed, you may continue playing. + +V. User Commands + + The following commands may prove useful for the playing of Zork. +They are not, however, game commands (i.e. they have no side effects +in the current game). + + a. Verbosity + + Verbose: The default: print long room descriptions on first + visit, 20% of the time thereafter. + + Brief: Supresses printing of long room descriptions for rooms + which have been visited. Short object descriptions + are also used in such rooms. + + Super(brief): Suppresses printing of all long descriptions, even + on the first visit. Short object descriptions are + always used. + + Noobj: Suppresses printing of object descriptions in rooms + already visited. See the 'object' command. + +Note that the maximally verbose description (that printed on the +first visit to a room in verbose mode) may always be obtained by +saying 'look'. See also the 'room' and 'object' commands. + + b. Help + + Info: Prints a file which might give some idea of + what the game is about. + + Help: Prints a short summary of useful commands. + + Doc: Prints this. + + c. Progress + + Quit: Prints your score, and asks whether you wish to + continue playing. + + Score: Deflate your ego. + + Time: Describe how much of eternity you have injured. + + Versi(on): Describe the current version. + + d. Hard copy (directory owners only!) + + Scrip(t): Script to a file ZORK.SCRIPT + + Unscr(ipt): End scripting + + e. Save/restore (directory owners only!) + + Save: Save the game for future continuation (to ZORK.SAVE) + + Resto(re): Restore a saved game (from ZORK.SAVE) + Only the player who created the save file can restore + it at a later time! You are warned. + + f. Bugs, etc. + + Bug: Although the best way to report bugs is to send mail + to ZORK@MIT-DMS, there is a 'bug' and command + built in to the game. This generates files which + must, alas, be manually transmitted to the + maintainers. It is, however, better than nothing. + + Featu(re): Like Bug, to make a suggestion for a feature. + + g. General + + Again: Repeat the last input. + + Look: Describe the current surroundings. 'L' is equivalent. + + Room: Print the verbose description of the room, without + mentioning any objects. + + Rname: Print the short description of the room. + + Object: Print the verbose description of all the objects in + the room, without describing the room. 'Look' is + equivalent to a 'room' command followed by an + 'object' command. + + Inven(t): Describe your possessions. 'I' is equivalent. + + Diagn(ose): Describe your state of health. + + Wait: Causes 'time' to pass. + + Oops: Corrects a misspelled word: As an example, + for 'I don't know the word TORHC' -> say 'OOPS TORCH'. + +VI. Zork Command Parser + + A command is one line of text terminated by a carriage return or + altmode. For reasons of simplicity all words are distinguished by + their first five letters. All others are ignored. For example, + typing 'DISASSEMBLE THE ENCYLOPEDIA', while meaningless, is also + creating excess finger motion. Note also that ambiguities can be + introduced by this: 'unscr' is 'UNSCRipt', not 'UNSCRew'. + + You are talking to a moderately stupid parser, which understands + the following types of things. + + Actions: + + Among the more obvious of these, TAKE, DROP, etc. Fairly general + forms of these may be used: PICK UP, PUT DOWN, etc. + + Directions: + + NORTH, SOUTH, UP, DOWN, etc. and their various abbreviations. + Other more obscure directions (LAND, CLIMB) are appropriate in + only certain situations. Because words are only five letters, + you must say 'nw' for 'northwest': the latter is truncated to + 'north', which isn't quite what you had in mind. + + Objects: + + Most objects have names, and can be referenced by them. At most, + two objects can be specified in one command. + + Adjectives: + + Some adjectives are understood and are required when there are + two objects which can be referenced with the same 'name' (e.g. + DOORs, BUTTONs) + + Prepositions: + + It may be necessary in some cases to include prepositions, but + the parser attempts to handle cases which aren't ambiguous + without. Thus 'Give car to demon' will work, as will 'Give demon + car.' When a preposition is used, it should be appropriate: + 'Give car with demon' does not parse. + + Sentences: + + The parser understands a reasonable number of things. Rather + than listing them, we advise you to do reasonable things. Note + that several sentences may be typed on the same line, separated + by periods or by 'and': 'n.e.s.w.open mailb and read' will [try + to] do just that. + + Multiple Objects: + + Sentences of the following forms will parse: + Put A and B and C in trophy case + Put A, B, and C in trophy case + Give A and B to the troll + The following will not: + Put A B in case + Take A B C + The point is that an AND or a are required so as not + to hopelessly confuse the parser. + Special objects named 'everything' and 'valuables' exist; one + may, for example, say 'take everything' and 'put valuables in + trophy case'. + + Multiple commands: + + Several commands may be included on a single line. They must be + separated by 'then' or '.'. Thus: + TAKE BOOK. N. DROP BOOK AND CANDLE + is correct. Note that the use of a comma between commands will + cause the command line to be parsed incorrectly: comma should + only be used between multiple objects. + + Ambiguity: + + The parser tries to be clever about what to do in the case of + actions which require objects in the case that the object is not + specified. If there is only one possible object, the parser will + assume that it should be used. Otherwise, the parser will ask. + Most questions asked by the parser can be answered (e.g. With + what?). + + Errors: + + There are a number of errors which the parser may find in an input + sentence. Some of the more common ones are listed here: + + 1. 'I don't know the word ZROK'. Probably the most common parser + error. To correct the spelling of a work, use the OOPS command. + In this case, 'OOPS ZORK' would be the correct thing. + + 2. 'I can't make sense out of that.'. This error means that there + is no known syntax that matches the input. For example, saying + 'PUT X WITH Y' does not match any known form for the verb 'PUT'. + This error never implies that the idea of the command was not + good, but rather that the parser doesn't know that form of the + verb. It's usually best to try another way of saying the same + thing. + + 3. 'Huh?'. A command usually without a noun or a verb. Sometimes + this is confusing, because a word thought to be a noun was really + an adjective. This is the case with, for example, 'GOLD'. + Other commands which cause this are: 'WITH' and 'THE'. + + 4. 'I can't see any here.'. An object represented by + 'thing' was not found within the room or on your person. + + 5. 'It's too dark in here to see.'. A reference was made to + an object within an unlighted room. + + 6. 'I can't reach the from within the '. This + means that the referenced was within the room proper, + while you are in a vehicle within that room. Some vehicles + will not allow access to objects outside of themselves. + + 7. 'That doesn't make any sense.' Usually this will mean that + something like 'TAKE THE COIL OF KEYS' instead of the 'SET' + of keys. In the general case, 'THE of ' is legal only + if and are names for the same thing. + + 8. 'Two verbs in command?' The parser believes that two verbs + were in the command. If you check carefully, you will find + that one of the words is really a verb, and not a noun as + supposed. + + 9. 'Double preposition?' Try 'TAKE WITH IN MAILBOX'. + + 10. 'Multiple inputs cannot be used with '. It is only + legal to use multiple inputs with certain verbs. The ones + which come to mind are TAKE, DROP, and PUT. + + 11. 'Too many objects specified?' A legal command may contain + at most two object references. + + 12. 'Beg pardon?'. A null input was parsed. + +VII. Theories + + The following 'theories' are fundamental to the game and should + be noted: + + Containment: + + Some objects can contain other objects. Many such containers + can be opened and closed; the rest are always open. They may or + may not be transparent. For you to access (take, for example) + an object which is in a container, the container must be open; + for you to see such an object, the container must either be open + or transparent. Containers have a capacity, and objects have + sizes; the number of objects which will fit therefore depends on + their sizes. You may "put" any object you have access to (it + need not be in your hands) into any other object; at some point, + the program will attempt to pick it up if you don't already have + it, which process may fail if you're carrying too much. + Although containers can contain other containers, the program + doesn't access more than one level down. + + Fighting: + + Occupants of the dungeon will, as a rule, fight back when + attacked; they may in some cases attack you unprovoked. Useful + verbs here are 'attack with ', 'kill', etc. + Knife-throwing may or may not be useful. The adventurer has a + fighting strength, which varies with time: in particular, being + in a fight, getting killed, and getting injured, all lower it. + One's carrying capacity may also be reduced after a fight. + Strength is regained with time. (Thus, it is not a good idea to + fight someone immediately after being killed.) Other details + may become apparent in the course of a few melees. The + 'diagnose' command describes your state of health. + + Vehicles: + + There are some objects in the labyrinth which are rumoured to have + the ability to transport the fearless adventurer to mysterious + regions which are inaccessible on foot. Needless to say, the + adventurer faces great personal peril as he encounters these + regions. The 'vehicles' can usually be entered with the 'board' + command, and can be exited with the 'disembark' command. + \ No newline at end of file diff --git a/doc/cfs/madadv.help b/doc/cfs/madadv.help new file mode 100755 index 00000000..a2972f45 --- /dev/null +++ b/doc/cfs/madadv.help @@ -0,0 +1,19 @@ + Commands to ZORK are simple sentences: , , +and are examples. Only the first five +characters of a word are looked at. Simple line editing commands include + to delete the last character, to delete the +entire buffer, and to redisplay the buffer. Commands terminate +with or . Long typeouts can be flushed with . + Some useful commands are: + + Walk in that direction. Common directions + are N, S, E, W, NE, NW, SE, SW, U(p), and D(own) +L(ook) Describe the surroundings. +I(nventory) Describe your possessions. +Diagnose Describe your state of health +Score Print your score & number of moves +Q(uit) Leave the game +Save/Restore Directory owners only - save/restore state of game +Bug Report a bug +Info Describe the goals of the game +Doc Game documentation (complete) \ No newline at end of file diff --git a/doc/cfs/madadv.info b/doc/cfs/madadv.info new file mode 100755 index 00000000..ee6e940b --- /dev/null +++ b/doc/cfs/madadv.info @@ -0,0 +1,34 @@ +Welcome to Zork! + + You are near a large underground labyrinth, which is reputed to +contain vast quantities of treasure. Naturally, you wish to acquire +some of it. In order to do so, you must of course remove it from the +caverns; to receive full credit for it, you must deposit it safely in +the trophy case in the living room. + + In addition to valuables, the cave contains various objects which +may or may not be useful in your attempt to get rich; you may need +sources of light, since caves are often dark, and weapons, since +dungeons often have unfriendly things wandering about. Reading material +is scattered around as well; some of it is rumoured to be useful. + + To determine how successful you have been, there is a score kept. +When you find a valuable object (i.e., pick it up), you receive a +certain number of points, which depends on the difficulty of finding +it. You receive extra points for transporting the treasure safely to +the living room, and placing it in the trophy case. In addition, +some particularly interesting rooms have a value associated with +your entering them. The only penalty is for getting yourself killed, +which you may do only twice. + + Of special note is a thief (always carrying a large bag) who likes +to wander around underground (he has never been seen by the light of +day). He likes to take things; since he steals for pleasure rather than +profit, and is sadistic, he only takes things which you have seen. +Although he prefers valuables, sometimes in his haste he may take +something which is worthless; from time to time, he examines his take +and discards objects which he doesn't like. He may occasionally stop in +a room you are visiting, but more often he just wanders through and rips +you off (he is a skilled pickpocket). + + Have Fun! \ No newline at end of file diff --git a/doc/madman/madadv.help b/doc/madman/madadv.help old mode 100644 new mode 100755 index 431806af..196ede1a --- a/doc/madman/madadv.help +++ b/doc/madman/madadv.help @@ -1,331 +1,140 @@ -ZORK User Information +Editorials -I. Getting a ZORK - - a. ITS: Say ZORK^K to DDT rather than :ZORK to get a zork. - b. 10X/20X: Invoke the local dungeon (usually ZORK.EXE) + 1. Users on ITS: say ZORK^K to DDT rather than :ZORK to get a + zork--this keeps you from tying up more than one of the three + available slots. + 2. Bugs, comments, etc. are always welcome. + Send mail to DUNGEON@MIT-DMS -II. Bugs, comments, suggestions... +Special characters, cautions, &c. + The characters ctrl-D and ctrl-L are useful for redisplaying what +you've typed before you terminate--particularly when you're on a +printing terminal (or TENEX/TOPS-20) where echoes the +character deleted rather than erasing it. Ctrl-@ (null) deletes the +entire line you've typed. + Dungeon may occasionally type out a message 'GIN FREE STORAGE- + GOUT TIME=10.92'. This indicates that a garbage +collection is occurring. We have attempted to prevent this, since it +may take a significant amount of real time on a loaded system; should +it ever occur, please send mail to DUNGEON@MIT-DMS describing the +circumstances--how many moves have been made, whether a RESTORE has +been done, and so on. THIS IS NOT FATAL: after the GOUT message is +printed, you may continue playing. - Always welcome and encouraged. All mail should be sent to - ZORK@MIT-DMS. ZORK has a BUG command, in addition, which - may be used to report strange happenings. Its use is described - below. Please note that for 10X/20X systems, net mail to ZORK - will be acted on much more quickly than BUG command reports. +Useful commands - If, in making a bug report, you know what symptoms were exhibited - by the program, PLEASE, PLEASE!!!!! include them. It is at best - extremely irritating and at worst useless to receive a bug report - like 'mumble frotz' loses, or 'try saying \"mumble frotz\"'. With - such reports, we have no way of knowing the situation when your - 'mumble frotz' lost, and no way of knowing if any bug we manage - to reproduce (if we do) is the same one you saw. In consequence, - everyone's time is wasted. + The 'brief' command suppresses printing of long room descriptions +for rooms which have been visited. The 'unbrief' command turns this +off. The 'superbrief' command suppresses printing of long room +descriptions for all rooms; 'unsup' turns this off. + The 'info' command prints a file which might give some idea of +what the game is about. + The 'quit' command (or ctrl-G) prints your score, and asks whether +you wish to continue playing. + The 'script', 'unscript', 'save', and 'restore' commands are +useful if you are a local user. + Although the best way to report bugs is to send mail to +DUNGEON@MIT-DMS, there are 'bug' and 'feature' commands built in to +the game. These generate files which must, alas, be manually +transmitted to the maintainers. It is, however, better than nothing. -III. Typing to Zork. - - A number of characters in Zork have special effects. These - include a number of line editing commands. The characters are: - - or : delete the last character typed - : delete the last word typed - or or : delete the entire buffer - : redisplay the buffer - : redisplay the buffer. Sometimes this also clears the - screen. - - : terminate commands - : flush long typeouts - : like the QUIT command (vide infra) - : Causes the remainder of the command line to be ignored. - This may be useful for annotating hard copies/scripts of games. - -IV. Garbage Collection - - Zork may occasionally type out a message 'GIN FREE STORAGE- - GOUT TIME=10.92'. This indicates that a garbage - collection is occurring. We have attempted to prevent this, since it - may take a significant amount of real time on a loaded system; should - it ever occur, please send mail to ZORK@MIT-DMS describing the - circumstances -- how many moves have been made, whether a RESTORE has - been done, and so on. THIS IS NOT FATAL: after the GOUT message is - printed, you may continue playing. - -V. User Commands - - The following commands may prove useful for the playing of Zork. -They are not, however, game commands (i.e. they have no side effects -in the current game). - - a. Verbosity - - Verbose: The default: print long room descriptions on first - visit, 20% of the time thereafter. - - Brief: Supresses printing of long room descriptions for rooms - which have been visited. Short object descriptions - are also used in such rooms. - - Super(brief): Suppresses printing of all long descriptions, even - on the first visit. Short object descriptions are - always used. - - Noobj: Suppresses printing of object descriptions in rooms - already visited. See the 'object' command. - -Note that the maximally verbose description (that printed on the -first visit to a room in verbose mode) may always be obtained by -saying 'look'. See also the 'room' and 'object' commands. - - b. Help +Dungeon Command Parser - Info: Prints a file which might give some idea of - what the game is about. - - Help: Prints a short summary of useful commands. + A command is one line of text terminated by a carriage return. +For reasons of simplicity all words are distinguished by their first +five letters. All others are ignored. For example, your typing +'DISASSEMBLE THE ENCYLOPEDIA' while meaningless is also creating +excess effort for your fingers. Note also that ambiguities can be +introduced by this: 'unscr' is 'UNSCRipt', not 'UNSCRew'. - Doc: Prints this. - - c. Progress - - Quit: Prints your score, and asks whether you wish to - continue playing. - - Score: Deflate your ego. - - Time: Describe how much of eternity you have injured. - - Versi(on): Describe the current version. - - d. Hard copy (directory owners only!) - - Scrip(t): Script to a file ZORK.SCRIPT - - Unscr(ipt): End scripting - - e. Save/restore (directory owners only!) - - Save: Save the game for future continuation (to ZORK.SAVE) - - Resto(re): Restore a saved game (from ZORK.SAVE) - Only the player who created the save file can restore - it at a later time! You are warned. - - f. Bugs, etc. - - Bug: Although the best way to report bugs is to send mail - to ZORK@MIT-DMS, there is a 'bug' and command - built in to the game. This generates files which - must, alas, be manually transmitted to the - maintainers. It is, however, better than nothing. - - Featu(re): Like Bug, to make a suggestion for a feature. - - g. General - - Again: Repeat the last input. - - Look: Describe the current surroundings. 'L' is equivalent. - - Room: Print the verbose description of the room, without - mentioning any objects. - - Rname: Print the short description of the room. - - Object: Print the verbose description of all the objects in - the room, without describing the room. 'Look' is - equivalent to a 'room' command followed by an - 'object' command. - - Inven(t): Describe your possessions. 'I' is equivalent. - - Diagn(ose): Describe your state of health. - - Wait: Causes 'time' to pass. - - Oops: Corrects a misspelled word: As an example, - for 'I don't know the word TORHC' -> say 'OOPS TORCH'. - -VI. Zork Command Parser - - A command is one line of text terminated by a carriage return or - altmode. For reasons of simplicity all words are distinguished by - their first five letters. All others are ignored. For example, - typing 'DISASSEMBLE THE ENCYLOPEDIA', while meaningless, is also - creating excess finger motion. Note also that ambiguities can be - introduced by this: 'unscr' is 'UNSCRipt', not 'UNSCRew'. - - You are talking to a moderately stupid parser, which understands - the following types of things. + You are talking to a fairly stupid parser, which understands the +following types of things. Actions: - - Among the more obvious of these, TAKE, DROP, etc. Fairly general - forms of these may be used: PICK UP, PUT DOWN, etc. + Among the more obvious of these, TAKE, DROP, etc. Fairly general + forms of these may be used: PICK UP, PUT DOWN, etc. Directions: - - NORTH, SOUTH, UP, DOWN, etc. and their various abbreviations. - Other more obscure directions (LAND, CLIMB) are appropriate in - only certain situations. Because words are only five letters, - you must say 'nw' for 'northwest': the latter is truncated to - 'north', which isn't quite what you had in mind. - + NORTH, SOUTH, UP, DOWN, etc. and their various abbreviations. + Other more obscure directions (LAND, CLIMB) are appropriate in + only certain situations. Because words are only five letters, + you must say 'nw' for 'northwest': the latter is truncated to + 'north', which isn't quite what you had in mind. + Objects: - - Most objects have names, and can be referenced by them. At most, - two objects can be specified in one command. + Most objects have names, and can be referenced by them. Adjectives: - - Some adjectives are understood and are required when there are - two objects which can be referenced with the same 'name' (e.g. - DOORs, BUTTONs) + Some adjectives are understood and are required when there are + two objects which can be referenced with the same 'name' (e.g. + DOORs, BUTTONs) Prepositions: - It may be necessary in some cases to include prepositions, but - the parser attempts to handle cases which aren't ambiguous - without. Thus 'Give car to demon' will work, as will 'Give demon - car.' When a preposition is used, it should be appropriate: - 'Give car with demon' does not parse. + It may be necessary in some cases to include prepositions, but + the parser attempts to handle cases which aren't ambiguous + without. Thus 'Give car to demon' will work, as will 'Give demon + car.' 'Give car demon' probably won't do anything interesting. + When a preposition is used, it should be appropriate: 'Give car + with demon' does not parse. Sentences: - The parser understands a reasonable number of things. Rather - than listing them, we advise you to do reasonable things. Note - that several sentences may be typed on the same line, separated - by periods or by 'and': 'n.e.s.w.open mailb and read' will [try - to] do just that. + The parser understands a reasonable number of things. Rather + than listing them, we advise you to do reasonable things. Multiple Objects: - Sentences of the following forms will parse: + Sentences of the following forms will parse: Put A and B and C in trophy case Put A, B, and C in trophy case Give A and B to the troll - The following will not: + The following will not: Put A B in case Take A B C - The point is that an AND or a are required so as not - to hopelessly confuse the parser. - Special objects named 'everything' and 'valuables' exist; one - may, for example, say 'take everything' and 'put valuables in - trophy case'. - - Multiple commands: - - Several commands may be included on a single line. They must be - separated by 'then' or '.'. Thus: - TAKE BOOK. N. DROP BOOK AND CANDLE - is correct. Note that the use of a comma between commands will - cause the command line to be parsed incorrectly: comma should - only be used between multiple objects. + The point is that an AND or a are required so as not + to hopelessly confuse the parser. Ambiguity: - The parser tries to be clever about what to do in the case of - actions which require objects in the case that the object is not - specified. If there is only one possible object, the parser will - assume that it should be used. Otherwise, the parser will ask. - Most questions asked by the parser can be answered (e.g. With - what?). + The parser tries to be clever about what to do in the case of + actions which require objects in the case that the object is not + specified. If there is only one possible object, the parser will + assume that it should be used. Otherwise, the parser will ask. + Most questions asked by the parser can be answered (e.g. With + what?). - Errors: + Inventory: Lists the objects in your possession. - There are a number of errors which the parser may find in an input - sentence. Some of the more common ones are listed here: - - 1. 'I don't know the word ZROK'. Probably the most common parser - error. To correct the spelling of a work, use the OOPS command. - In this case, 'OOPS ZORK' would be the correct thing. - - 2. 'I can't make sense out of that.'. This error means that there - is no known syntax that matches the input. For example, saying - 'PUT X WITH Y' does not match any known form for the verb 'PUT'. - This error never implies that the idea of the command was not - good, but rather that the parser doesn't know that form of the - verb. It's usually best to try another way of saying the same - thing. - - 3. 'Huh?'. A command usually without a noun or a verb. Sometimes - this is confusing, because a word thought to be a noun was really - an adjective. This is the case with, for example, 'GOLD'. - Other commands which cause this are: 'WITH' and 'THE'. - - 4. 'I can't see any here.'. An object represented by - 'thing' was not found within the room or on your person. - - 5. 'It's too dark in here to see.'. A reference was made to - an object within an unlighted room. - - 6. 'I can't reach the from within the '. This - means that the referenced was within the room proper, - while you are in a vehicle within that room. Some vehicles - will not allow access to objects outside of themselves. - - 7. 'That doesn't make any sense.' Usually this will mean that - something like 'TAKE THE COIL OF KEYS' instead of the 'SET' - of keys. In the general case, 'THE of ' is legal only - if and are names for the same thing. - - 8. 'Two verbs in command?' The parser believes that two verbs - were in the command. If you check carefully, you will find - that one of the words is really a verb, and not a noun as - supposed. - - 9. 'Double preposition?' Try 'TAKE WITH IN MAILBOX'. - - 10. 'Multiple inputs cannot be used with '. It is only - legal to use multiple inputs with certain verbs. The ones - which come to mind are TAKE, DROP, and PUT. - - 11. 'Too many objects specified?' A legal command may contain - at most two object references. - - 12. 'Beg pardon?'. A null input was parsed. - -VII. Theories - - The following 'theories' are fundamental to the game and should - be noted: + Look: Prints a description of your surroundings. Containment: - Some objects can contain other objects. Many such containers - can be opened and closed; the rest are always open. They may or - may not be transparent. For you to access (take, for example) - an object which is in a container, the container must be open; - for you to see such an object, the container must either be open - or transparent. Containers have a capacity, and objects have - sizes; the number of objects which will fit therefore depends on - their sizes. You may "put" any object you have access to (it - need not be in your hands) into any other object; at some point, - the program will attempt to pick it up if you don't already have - it, which process may fail if you're carrying too much. - Although containers can contain other containers, the program - doesn't access more than one level down. + Some objects can contain other objects. Many such containers can + be opened and closed; the rest are always open. They may or may + not be transparent. For you to access (take, for example) an + object which is in a container, the container must be open; for you + to see such an object, the container must either be open or + transparent. Containers have a capacity, and objects have sizes; + the number of objects which will fit therefore depends on their + sizes. You may "put" any object you have access to (it need not be + in your hands) into any other object; at some point, the program + will attempt to pick it up if you don't already have it, which + process may fail if you're carrying too much. Although containers + can contain other containers, the program doesn't access more than + one level down. Fighting: - Occupants of the dungeon will, as a rule, fight back when - attacked; they may in some cases attack you unprovoked. Useful - verbs here are 'attack with ', 'kill', etc. - Knife-throwing may or may not be useful. The adventurer has a - fighting strength, which varies with time: in particular, being - in a fight, getting killed, and getting injured, all lower it. - One's carrying capacity may also be reduced after a fight. - Strength is regained with time. (Thus, it is not a good idea to - fight someone immediately after being killed.) Other details - may become apparent in the course of a few melees. The - 'diagnose' command describes your state of health. + Occupants of the dungeon will, as a rule, fight back when + attacked; they may in some cases attack you unprovoked. Useful + verbs here are 'attack with ', 'kill', etc. + Knife-throwing may or may not be useful. The adventurer has a + fighting strength, which varies with time: in particular, being + in a fight, getting killed, and getting injured, all lower it. + One's carrying capacity may also be reduced after a fight. + Strength is regained with time. (Thus, it is not a good idea to + fight someone immediately after being killed.) Other details + may become apparent in the course of a few melees. The + 'diagnose' command describes your state of health. - Vehicles: - - There are some objects in the labyrinth which are rumoured to have - the ability to transport the fearless adventurer to mysterious - regions which are inaccessible on foot. Needless to say, the - adventurer faces great personal peril as he encounters these - regions. The 'vehicles' can usually be entered with the 'board' - command, and can be exited with the 'disembark' command. - \ No newline at end of file diff --git a/doc/madman/madadv.info b/doc/madman/madadv.info old mode 100644 new mode 100755 index ee6e940b4fb4dbe272ebe0a080e9fd8ce769b8d5..6821e57f9d19c7561275f2ea53a52949b82385c5 GIT binary patch delta 543 zcmYjOyKWOf6!qF#M+{1&6zK>YEb@{pcM(Nggc1n}Q6ZFS*uCo+yq;^#%-V`l&>>N- zMtlVD1N;dR-#|e@m5RGgEYXaPuI{<#F`xE+J$&?z8)#2(q&+lh?Pr9taWi7qULNeB zU>CJ@Sm_W|TRh)K;01vz*f;@RI@NwV-`!F!5LvaqPmXH4A}=clx}y48#)yV6lDTy= z<(U_wNqUpvjXI71rePbA%|{PYk@&y|g12)(-7S93Ba-Hu&@Kso?L!bL-^gByxh3jvXB8M zq?O_#N{a|Oms`fEoT%|UmtGp3u`umFcn>AH1x}PzO}leONb;3KBYnwQ5(}uKPwGn4 zmek}8!84lJR;ao1#MnV$EX>jSm==p1ssa{LDa+C`$#iBA|f&Sp1xmOYKajl1c0g287UjP6A