DOCSLIB.ORG

IF XML Metadata Format

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

**Draft** Interactive Fiction XML metadata format Version 1.0 (Draft) August 3, 2005 by Andrew Hunter Contents 1 Introduction 2 1.1 Who should use this format? ................................ 2 2 The format 3 2.1 The root element: ifindex .................................. 3 2.2 The story tag: story ..................................... 3 2.3 The story identification tag: identification ......................... 3 2.3.1 Example ...................................... 4 2.3.2 Z-Code identification tag: zcode .......................... 4 2.3.3 Glulx identification ................................. 4 2.3.4 MD5 identification ................................. 5 2.4 The metadata tags ...................................... 5 3 Optional modules 7 3.1 The feelies module ..................................... 7 3.2 The comments module ................................... 7 3.3 The resources module .................................... 7 3.4 The review module ..................................... 8 4 Parsing notes 9 5 Attaching metadata 10 5.1 To z-code games ...................................... 10 5.2 In filesystem metadata ................................... 10 5.3 To archive sites ....................................... 10 5.4 To review sites ....................................... 10 1 1 Introduction The original inspiration of this format is an improvement on the existing interactive fiction cataloguing system in Zoom. The original design for this used a text file with an arbitrary format, mainly designed for storing interpreter settings. It was also capable of storing some limited metadata along with stories, in particular a full title for the story, which was used in the interpreter’s title bar, and also to provide a simple menu of stories. This format is intended to provide a more advanced indexing system for stories. It deals specifically with metadata aspects of stories, leaving interpreter configuration issues up to specific interpreters. This release (1.0) will be implemented in the 1.0.2 release of Zoom. The initial emphasis is on Z-Code stories, but the intention is to allow the indexing of stories in any of the formats currently in use. A simpler format (0.9) was originally used by Zoom. This new version is based on the results of a discussion on the Inform-developers mailing list. 1.1 Who should use this format? Initially, this format will be used by Zoom to provide a searchable list of stories. However, I hope eventually to encourage archive maintainers and other interpreter authors to make use of the format. In addition, story authors may want to provide an XML description file along with their stories. 2 2 The format All metadata index files are in XML format, and so begin with a <?xml version="1.0"?> line. The namespace URI is http://www.logicalshift.org.uk/IF/metadata. The metadata may be extended by addi- tional modules, which must have their own unique namespace. Parsers must always identify namespaces by URI and not by prefix. The metadata for a story may come from many different files. For example, an archive site may provide an index of games, a review site may provide reviews, the game author may provide ’feelies’ (resources associated with the story), and the user may provide notes and comments. Modules are intended to be ’functionally unique’, providing the data for one of these specific domains. Therefore, when an application fetches metadata from multiple locations, it might use the entire resources module from one place and the review module from another, but won’t merge parts of the resources section from one site with those provided by another. 2.1 The root element: ifindex This tag specifies the version of the IF metadata format with the ’version’ attribute (0.9 for a file con- forming to this document). Usually, this should also specify the namespace URI and XML schema location. <ifindex version="1.0" xmlns="http://www.logicalshift.org.uk/IF/metadata"> (2.1) The <ifindex> tag contains <story> tags, one for each story that is defined in the file. 2.2 The story tag: story The <story> tag is used to specify the data associated with a particular story. It must contain at least one <identification> section, and may contain one or more metadata tags. It appears only as a child of the ifindex tag. The <identification> section may be omitted if the metadata is associated with a game in some other fashion (for example if it is contained in a Blorb file). 2.3 The story identification tag: identification The <identification> tag appears as part of a <story> section, and must contain a <format> tag identifying the format of the story, and some data providing a unique ID for the story. It appears only as a child of <story>, which must contain at least one of these tags, but may contain many if a story has several different versions. The <id> tag is a synonym for the <identification> tag. The <format> tag contains textual data identifying the format of the story. This version of the specifica- tion defines identification tags for the following formats: zcode A Z-Code story of the type released by Infocom in the 1980s, or, more recently, compiled with the Z-Code version of Inform. glulx A glulx story of the type compiled by the Glulx version of Inform. The following additional types are reserved for other existing formats, and may have identification tags defined in the future: 3 tads A TADS story compiled by the TADS compiler. hugo A HUGO story compiled by the HUGO compiler. alan An Alan story adrift An Adrift story level9 A story in the Level 9 format AGT A story in the AGT format magscrolls A story in the magnetic scrolls format advsys A story in the advsys format 2.3.1 Example <story> <identification> <format>zcode</format> <zcode> <serial>871125</serial> <release>52</release> (2.2) <checksum>4b37</checksum> </zcode> <md5>d82484e664a8c328364e9814d1f73c60</md5> </identification> </story> 2.3.2 Z-Code identification tag: zcode The <zcode> tag is used only when the <format> value is ’zcode’. In that case, it must appear exactly once as a child of an <indentification> tag. It should contain the following elements: <serial> The textual serial number of the story. This is usually a six-digit string specifying the date of release, such as 871125. <release> The release number of the story (for example, 52). <checksum> (Optional, but recommended) The checksum of the story, in hexadecimal format, as spec- ified in the header of the story (for example, 4b37). This field is optional, but note that the se- rial/release numbers are not guaranteed to be unique, especially with more recent stories. 2.3.3 Glulx identification ULX format files do not contain any specific story identification information. However, those compiled by Inform may contain a short ’Info’ section located after the header. The <glulx> section is therefore optional, and only applies to stories compiled with Inform. An <md5> section should be used to more precisely identify a Glulx story. The <glulx> section may contain the following tags: <serial> The textual serial number of the story. This is usually a six-digit string specifying the date of release, such as 030501. <release> The release number of the story (for example, 2). 4 2.3.4 MD5 identification Any story format may have an MD5 section. This is a hexadecimal representation of the MD5 checksum of a story file. In the case of a Blorb file, this is the MD5 checksum of the executable portion of the file (the Z-Code or Glulx code file that it contains) rather than the entire file. There are several utilities available for generating MD5 checksums, for example the ’md5’ utility that comes with OpenSSL. Any story <format> may have an <md5> section, although the format-specific identification should be used for preference as it will be easier to write for a story author. 2.4 The metadata tags Each metadata tag may appear zero or one times as a child of the <story> tag. The following tags are defined: <title> The title of the story (for example, Zork 1, Solid Gold Edition) <author> The author of the story <genre> The genre of the story (Fantasy) <published> The date the story was first published in YYYYMMDD format (19810505) <revision> The revision number of the game <headline> The headline of the story (Infocom interactive fiction - a fantasy story) <group> The ’group’ the story is in (for example, ’Infocom’, ’Competition 1998’, etc) <zarfian> The story’s rating according to the ’Zarfian’ scale (’Merciful’, ’Polite’, ’Tough’, ’Nasty’, ’Cruel’) <teaser> The story’s teaser text <series> Specifies the series that a game is part of <seriesnumber> Specifies the number in the series the game is <serieslength> Specifies the length of the game series The ’Zarfian’ rating system is described by Andrew Plotkin as follows: Merciful cannot get stuck Polite can get stuck or die, but it’s immediately obvious that you’re stuck or dead Tough can get stuck, but it’s immediately obvious that you’re about to do something irrevocable Nasty can get stuck, but when you do something irrevocable, it’s clear Cruel can get stuck by doing something which isn’t obviously irrevocable (even after the act) Comments and teasers may contain newlines, specified by a <br /> tag: all other tags are single line values. No tag may appear more than once. The genre can be any textual value, but Zoom suggests the following list of ’standard’ genres: • Fantasy 5 • Science fiction • Horror • Fairy tale • Surreal • Mystery • Romance • Historical • Humour • Parody • Speed-IF • Arcade • Interpreter abuse 6 3 Optional modules 3.1 The feelies module This module can be used to specify ’feelies’: additional media associated with a game. The namespace URI for this module is http://www.logicalshift.org.uk/IF/metadata/feelies The tags supported by this module are: <icon> A miniature picture associated with the game. This should be a base 64 encoded PNG file of 128x128 size, and can be used by an interpreter to display an image associated with a game file.
Recommended publications
  • Alan Adventure System V3.0

    Alan Adventure System V3.0

    The ALAN Adventure Language Reference Manual Version 3.0beta2 Alan Adventure System - Reference Manual This version of the manual was printed on September 26, 2011 - ii - Alan Adventure System - Reference Manual Table of Contents 1 INTRODUCTION.........................................................................11 1.1 Programmer’s Pitch........................................................................................................12 1.2 To the Reader.................................................................................................................12 2 CONCEPTS......................................................................................13 2.1 What Is An Adventure?................................................................................................13 2.2 Elements Of Adventures.................................................................................................15 2.3 Alan Fundamentals.......................................................................................................16 What Is A Language?....................................................................................................................................16 The Alan Idea..................................................................................................................................................18 What’s Happening?........................................................................................................................................18 The Map..........................................................................................................................................................19
  • DESIGN-DRIVEN APPROACHES TOWARD MORE EXPRESSIVE STORYGAMES a Dissertation Submitted in Partial Satisfaction of the Requirements for the Degree Of

    DESIGN-DRIVEN APPROACHES TOWARD MORE EXPRESSIVE STORYGAMES a Dissertation Submitted in Partial Satisfaction of the Requirements for the Degree Of

    UNIVERSITY OF CALIFORNIA SANTA CRUZ CHANGEFUL TALES: DESIGN-DRIVEN APPROACHES TOWARD MORE EXPRESSIVE STORYGAMES A dissertation submitted in partial satisfaction of the requirements for the degree of DOCTOR OF PHILOSOPHY in COMPUTER SCIENCE by Aaron A. Reed June 2017 The Dissertation of Aaron A. Reed is approved: Noah Wardrip-Fruin, Chair Michael Mateas Michael Chemers Dean Tyrus Miller Vice Provost and Dean of Graduate Studies Copyright c by Aaron A. Reed 2017 Table of Contents List of Figures viii List of Tables xii Abstract xiii Acknowledgments xv Introduction 1 1 Framework 15 1.1 Vocabulary . 15 1.1.1 Foundational terms . 15 1.1.2 Storygames . 18 1.1.2.1 Adventure as prototypical storygame . 19 1.1.2.2 What Isn't a Storygame? . 21 1.1.3 Expressive Input . 24 1.1.4 Why Fiction? . 27 1.2 A Framework for Storygame Discussion . 30 1.2.1 The Slipperiness of Genre . 30 1.2.2 Inputs, Events, and Actions . 31 1.2.3 Mechanics and Dynamics . 32 1.2.4 Operational Logics . 33 1.2.5 Narrative Mechanics . 34 1.2.6 Narrative Logics . 36 1.2.7 The Choice Graph: A Standard Narrative Logic . 38 2 The Adventure Game: An Existing Storygame Mode 44 2.1 Definition . 46 2.2 Eureka Stories . 56 2.3 The Adventure Triangle and its Flaws . 60 2.3.1 Instability . 65 iii 2.4 Blue Lacuna ................................. 66 2.5 Three Design Solutions . 69 2.5.1 The Witness ............................. 70 2.5.2 Firewatch ............................... 78 2.5.3 Her Story ............................... 86 2.6 A Technological Fix? .
  • Metadefender Core V4.12.2

    Metadefender Core V4.12.2

    MetaDefender Core v4.12.2 © 2018 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of Metadefender Core 14 1. Quick Start with Metadefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Scan Files with Metadefender Core 21 2. Installing or Upgrading Metadefender Core 22 2.1. Recommended System Requirements 22 System Requirements For Server 22 Browser Requirements for the Metadefender Core Management Console 24 2.2. Installing Metadefender 25 Installation 25 Installation notes 25 2.2.1. Installing Metadefender Core using command line 26 2.2.2. Installing Metadefender Core using the Install Wizard 27 2.3. Upgrading MetaDefender Core 27 Upgrading from MetaDefender Core 3.x 27 Upgrading from MetaDefender Core 4.x 28 2.4. Metadefender Core Licensing 28 2.4.1. Activating Metadefender Licenses 28 2.4.2. Checking Your Metadefender Core License 35 2.5. Performance and Load Estimation 36 What to know before reading the results: Some factors that affect performance 36 How test results are calculated 37 Test Reports 37 Performance Report - Multi-Scanning On Linux 37 Performance Report - Multi-Scanning On Windows 41 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3. Configuring Metadefender Core 50 3.1. Management Console 50 3.2.
  • Metadefender Core V4.13.1

    Metadefender Core V4.13.1

    MetaDefender Core v4.13.1 © 2018 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of Metadefender Core 14 1. Quick Start with Metadefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Scan Files with Metadefender Core 21 2. Installing or Upgrading Metadefender Core 22 2.1. Recommended System Requirements 22 System Requirements For Server 22 Browser Requirements for the Metadefender Core Management Console 24 2.2. Installing Metadefender 25 Installation 25 Installation notes 25 2.2.1. Installing Metadefender Core using command line 26 2.2.2. Installing Metadefender Core using the Install Wizard 27 2.3. Upgrading MetaDefender Core 27 Upgrading from MetaDefender Core 3.x 27 Upgrading from MetaDefender Core 4.x 28 2.4. Metadefender Core Licensing 28 2.4.1. Activating Metadefender Licenses 28 2.4.2. Checking Your Metadefender Core License 35 2.5. Performance and Load Estimation 36 What to know before reading the results: Some factors that affect performance 36 How test results are calculated 37 Test Reports 37 Performance Report - Multi-Scanning On Linux 37 Performance Report - Multi-Scanning On Windows 41 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3. Configuring Metadefender Core 50 3.1. Management Console 50 3.2.
  • 14. Riddle Machines: the History and Nature of Interactive Fiction

    14. Riddle Machines: the History and Nature of Interactive Fiction

    Nick Montfort Riddle Machines: The History and Nature of Interactive Fiction 14. Riddle Machines: The History and Nature of Interactive Fiction Nick Montfort Introduction The genre that has also been labeled "text adventure" and "text game" is stereotypically thought to offer dungeons, dragons, and the ability for readers to choose their own adventure. While there may be dragons here, interactive fiction (abbreviated "IF") also offers utopias, revenge plays, horrors, parables, intrigues, and codework, and pieces in this form resound with and rework Gilgamesh, Shakespeare, and Eliot as well as Tolkien. The reader types in phrases to participate in a dialogue with the system, commanding a character with writing. Beneath this surface conversation, and determining what the computer narrates, there is the machinery of a simulated world, capable of drawing the reader into imagining new perspectives and understanding strange systems. Interactive fiction works can be challenging for literary readers, even those interested in other sorts of electronic literature, because of the text-based interface and because of the way in which these works require detailed exploration, mapping, and solution. Works in this form are often less visually rewarding, and the rewards they do offer are only attained with time and effort. But text-based interactive fiction has provided some of the most the intricate and compelling literary simulations yet developed. Understanding how interactive fiction works, and how it has developed over the past three decades, is an essential part of the puzzle of literary computing. Characteristics of interactive fiction Formally, a work of interactive fiction (often called a "game," even if it does not exhibit the typical qualities of a game) is an interactive computer program.
  • The Post Infocom Text Adventure Collection

    The Post Infocom Text Adventure Collection

    The Post Infocom Text Adventure Collection Many of us played and loved the text adventures produced by Infocom in the 1980’s. They were rich in story and puzzles, and contained some excellent writing. In the years since Infocom’s demise in 1989, there have been a lot of good games produced using the Z-Machine - the game format that Infocom was using. This gives us a chance to make these modern-day games run on the computers of the 80’s, like the Commodore 64. I decided to create a collection of Z-machine games for the C64, and this is it. All in all, it’s 31 games, released in 1993-2015. Each game has been put into its own directory, in which is also an empty disk for game saves and a file called AUTOSWAP.LST to make life easier for people using the SD2IEC diskdrive substitute. If you haven’t played text adventures before, or feel that you never got the hang of it, you should read the chapter How to play a text adventure. If you want more of a background on Infocom and the game format they used, you should read the chapter about The Zork Machine at the end of this document. There is also a chapter about the process of porting Z-machine games to the C64 and, finally, a chapter about writing your own games. I created this documentation as a PDF, so that you could easily print it out and keep it nearby if you’re enjoying the collection on a real C64.
  • The Z-Machine Standards Document: Contents

    The Z-Machine Standards Document: Contents

    The Z-Machine Standards Document: Contents The Z-Machine Standards Document Version 1.0 22nd June 1997 two misprints corrected, 9th August resources appendix updated and discovery added to header table, 4th September ● Preface ● Overview of Z-machine architecture Fundamentals ● 1. The memory map ● 2. Numbers and arithmetic ● 3. How text and characters are encoded ● 4. How instructions are encoded ● 5. How routines are encoded ● 6. The game state: storage and routine calls Input/Output ● 7. Output streams and file handling ● 8. The screen model ● 9. Sound effects ● 10. Input streams and devices Tables ● 11. The format of the header ● 12. The object table ● 13. The dictionary and lexical analysis Instruction Set ● 14. Complete table of opcodes (with Inform assembly syntax) file:///D|/doc/zspec10/index.html (1 of 2) [6/22/2000 4:34:11 PM] The Z-Machine Standards Document: Contents ● 15. Dictionary of opcodes An Unusual Font ● 16. Font 3 and character graphics Appendices ● A. Error messages and debugging ● B. Conventional contents of the header ● C. Resources available (with WWW links) ● D. A short history of the Z-machine ● E. Statistics ● F. Canonical story files file:///D|/doc/zspec10/index.html (2 of 2) [6/22/2000 4:34:11 PM] The Z-Machine Standards Document: Preface Preface The Z-machine was created on a coffee table in Pittsburgh in 1979. It is an imaginary computer whose programs are adventure games, and is well-adapted to its task, implementing complex games remarkably compactly. They were still perhaps 100K long, too large for the memory of the home computers of their day, and the Z-machine seems to have made the first usage of virtual memory on a microcomputer.
  • IF Theory Reader

    IF Theory Reader

    IF Theory Reader edited by Kevin Jackson-Mead J. Robinson Wheeler > Transcript On Press Boston, MA All authors of articles in this book retain their own copyrights. Neither the editors nor the publisher make any copyright claims. Version 1, March 2011. Version 2, April 2011. Please send corrections to [email protected]. Contents Preface Crimes Against Mimesis 1 Roger S. G. Sorolla Theory Toward a Theory of Interactive Fiction 25 Nick Montfort Characterizing, If Not Defining, Interactive Fiction 59 Andrew Plotkin not that you may remember time: Interactive Fiction, Stream-of-Consciousness Writing, and Free Will 67 Mark Silcox 2 Brief Dada Angels 89 Ryan Stevens, writing as Rybread Celsius Object Relations 91 Graham Nelson IF as Argument 101 Duncan Stevens The Success of Genre in Interactive Fiction 111 Neil Yorke-Smith Parser at the Threshold: Lovecraftian Horror in Interactive Fiction 129 Michael Gentry Distinguishing Between Game Design and Analysis: One View 135 Gareth Rees Natural Language, Semantic Analysis, and Interactive Fiction 141 Graham Nelson Afterword: Five Years Later 189 Graham Nelson Craft Challenges of a Broad Geography 203 Emily Short Thinking Into the Box: On the Use and Deployment of Puzzles 229 Jon Ingold PC Personality and Motivations 249 Duncan Stevens Landscape and Character in IF 261 Paul O’Brian Hint Development for IF 279 Lucian Smith Descriptions Constructed 291 Stephen Granade Mapping the Tale: Scene Description in IF 299 J. Robinson Wheeler Repetition of Text in Interactive Fiction 317 Jason Dyer NPC Dialogue Writing 325 Robb Sherwin NPC Conversation Systems 331 Emily Short History 10 Years of IF: 1994–2004 359 Duncan Stevens The Evolution of Short Works: From Sprawling Cave Crawls to Tiny Experiments 369 Stephen Granade History of Italian IF 379 Francesco Cordella Racontons une histoire ensemble: History and Characteristics of French IF 389 Hugo Labrande Preface This is a book for which people in the interactive fiction community have been waiting for quite some time.
  • Z-Machine and Descendants

    Z-Machine and Descendants

    Glk! A universal user interface for IF! Andrew Plotkin — BangBangCon ’17 Glk! A universal user interface! for interactive fiction! Relatively universal, anyhow. Universal-ish. # 1 Glk! A universal user interface for IF! Andrew Plotkin — BangBangCon ’17 Andrew Plotkin [email protected] http://zarfhome.com/ https://github.com/erkyrath @zarfeblong on Twitter Glk, Glulx, Hadean Lands, System’s Twilight, Spider and Web, Capture the Flag with Stuff, Shade, this t-shirt I’m wearing, Seltani, The Dreamhold, Branches and Twigs and Thorns, quite a lot of adventure game reviews, Praser 5, Boodler, A Change in the Weather, an imperfect diagram of the Soul Reaver timeline, Dual Transform, Draco Concordans, and you know how that game Mafia is also called Werewolf? Ok, funny story there — # 2 Glk! A universal user interface for IF! Andrew Plotkin — BangBangCon ’17 Zork 1 (Infocom) # 3 GrueFacts™: A grue can eat doughnuts indefinitely. Glk! A universal user interface for IF! Andrew Plotkin — BangBangCon ’17 Z-machine and descendants 1979: Z-machine design 1980: Z-machine version 3 (Zork 1) 1985: Z-machine version 4 (A Mind Forever Voyaging) 1987: ITF (first open-source Z-interpreter) 1988: Z-machine version 6 (Zork Zero) 1989: Infocom shuts down 1993: Inform (Curses) 1994: Inform 5 1996: Inform 6 1997: Glk spec 1999: Glulx spec 2006: Inform 7 2008: Parchment (first Javascript Z-interpreter) # 4 GrueFacts™: The first grue to swim around the world was named Amelia Nosewig. Glk! A universal user interface for IF! Andrew Plotkin — BangBangCon ’17 XZip (Curses, Graham Nelson) # 5 GrueFacts™: Grues live an average of 67 years, after which they retire to Iceland.
  • Metadefender Core V4.17.3

    Metadefender Core V4.17.3

    MetaDefender Core v4.17.3 © 2020 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of MetaDefender Core 14 1. Quick Start with MetaDefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Process Files with MetaDefender Core 21 2. Installing or Upgrading MetaDefender Core 22 2.1. Recommended System Configuration 22 Microsoft Windows Deployments 22 Unix Based Deployments 24 Data Retention 26 Custom Engines 27 Browser Requirements for the Metadefender Core Management Console 27 2.2. Installing MetaDefender 27 Installation 27 Installation notes 27 2.2.1. Installing Metadefender Core using command line 28 2.2.2. Installing Metadefender Core using the Install Wizard 31 2.3. Upgrading MetaDefender Core 31 Upgrading from MetaDefender Core 3.x 31 Upgrading from MetaDefender Core 4.x 31 2.4. MetaDefender Core Licensing 32 2.4.1. Activating Metadefender Licenses 32 2.4.2. Checking Your Metadefender Core License 37 2.5. Performance and Load Estimation 38 What to know before reading the results: Some factors that affect performance 38 How test results are calculated 39 Test Reports 39 Performance Report - Multi-Scanning On Linux 39 Performance Report - Multi-Scanning On Windows 43 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3.
  • Infocom-Type Games 10Lndns Z5 1-2-3 Z5 Title: 1,2,3.. Author: Chris

    Infocom-Type Games 10Lndns Z5 1-2-3 Z5 Title: 1,2,3.. Author: Chris

    Infocom-type Games 10lndns_z5 1-2-3_z5 Title: 1,2,3.. Author: Chris Mudd Horror adventure where you are a serial killer. 905_z5 Title: 9:05 Author: Adam Cadre Slice of life abent_z5 Title: Abenteur Author: William Crowther, Don Woods, Graham Nelson, and Toni Arnold Classic “Adventure” game in German. acid_z5 Title: Acid Whiplash Author: Ryan Stevens and Cody Sandier Surreal adventure game acorncourt_z5 Title: The Acorn Court Author: Todd S. Murchison A small, one-location game in which you must escape from a court. The game shows Inform's capability of handling multiple equal objects. Advent_z5 Title: Adventure Author: William Crowther and Donald Woods The original Adventure game from 1978. Adventureland_z5 Title: Adventure Land Author: Scott Adams Wander through an enchanted realm and try to uncover the 13 lost treasures. There are wild animals and magical beings to reckon with as well as many other perils and mysteries. (1978) adverbum_z5 Title: Ad Verbum Author: Nick Montfort "With the cantankerous Wizard of Wordplay evicted from his mansion, the worthless plot can now be redeveloped. The city regulations declare, however, that the rip-down job can't proceed until all the items within had been removed.” ADVLAND_Z5 Title: Adventureland Author: Scott Adams ADVSAMP_Z5 Title: Adventureland (Sample) Author: Scott Adams agb_z5 Title: A Good Breakfast Author: Stuart Adair You are longing for a good breakfast, but where do you get the ingredients from? Aisle_z5 Title: Aisle Author: Sam Barlow "Late Thursday night. You've had a hard day and the last thing you need is this: shopping. Luckily, the place is pretty empty and you're progressing rapidly.
  • Riddle Machines: the History and Nature of Interactive Fiction

    Riddle Machines: the History and Nature of Interactive Fiction

    Riddle Machines: The History and Nature of Interactive Fiction The MIT Faculty has made this article openly available. Please share how this access benefits you. Your story matters. Citation Montfort, Nick. "Riddle Machines: The History and Nature of Interactive Fiction." A Companion to Digital Literary Studies, edited by Ray Siemens and Susan Schreibman, John Wiley & Sons Ltd, 2013, 267-282. © 2013 Ray Siemens and Susan Schreibman As Published http://dx.doi.org/10.1002/9781405177504.ch14 Publisher John Wiley & Sons, Ltd Version Author's final manuscript Citable link https://hdl.handle.net/1721.1/129076 Terms of Use Creative Commons Attribution-Noncommercial-Share Alike Detailed Terms http://creativecommons.org/licenses/by-nc-sa/4.0/ Nick Montfort Riddle Machines: The History and Nature of Interactive Fiction 14. Riddle Machines: The History and Nature of Interactive Fiction Nick Montfort Introduction The genre that has also been labeled "text adventure" and "text game" is stereotypically thought to offer dungeons, dragons, and the ability for readers to choose their own adventure. While there may be dragons here, interactive fiction (abbreviated "IF") also offers utopias, revenge plays, horrors, parables, intrigues, and codework, and pieces in this form resound with and rework Gilgamesh, Shakespeare, and Eliot as well as Tolkien. The reader types in phrases to participate in a dialogue with the system, commanding a character with writing. Beneath this surface conversation, and determining what the computer narrates, there is the machinery of a simulated world, capable of drawing the reader into imagining new perspectives and understanding strange systems. Interactive fiction works can be challenging for literary readers, even those interested in other sorts of electronic literature, because of the text-based interface and because of the way in which these works require detailed exploration, mapping, and solution.