Slashdot Mirror


A New Stab at Interactive Fiction

pamar writes "Dr Dobbs Journal interviews Chris Crawford, the noted game designer, about a new direction for interactive fiction. In the interview, he talks of his new stab at Interactive Fiction, and mentions Storytron, his new company which he hopes will make interactive fiction easier to write, not only for games, but for complex social interactions in general."

9 of 141 comments (clear)

  1. Quite a... by GillBates0 · · Score: 5, Funny

    Quite a creative venture, but who knows how it'll end.

    --
    An Indian-American Hindu committed to non-violent thought/speech/action alarmed by the global explosion of radical Islam
    1. Re:Quite a... by VJ42 · · Score: 4, Funny

      It'll get eaten by a grue

      --
      If I have nothing to hide, you have no reason to search me
  2. Pilot's seat? by Anonymous Coward · · Score: 5, Insightful

    Here's the question though. Is fiction really ment to be interactive? Or is fiction the journey the author leads you on?

    1. Re:Pilot's seat? by lawpoop · · Score: 4, Interesting

      That's exactly right. Fiction, or a story, is not interactive. Fiction is a retelling *of the past*. It's not what you're doing right now.

      A story has three parts. In the first act, we have the status quo, situation normal. A good storyteller might call this the set up. Then, something happens that disturbs the status quo -- something that the protagonist has to deal with. They can't go back to the status quo. In the third act, there is the final confrontation with whatever the obstacle is. After the final confrontation, there is a new equalibrium, a new status quo.

      So, if you are having a bad day, you don't know where the story ends. You might get in a car wreck in the morning. You might get fired by your boss in the afternoon for being late. Your wife might leave you in the evening for getting fired and wrecking the car. At any point, you might decide to tell a story about 'the car wreck', 'the firing', or 'my wife leaving me', or you might tell a story about 'my horrible day'. Any one of those events might be the climax or final confrontation of this particular story you are choosing to tell.

      You have to decide in advance what events *of the past* are going to be in your story. You have to know the climax of the story in order to build it up properly. This subject is coincidentally the subject of my last journal entry.

      --
      Computers are useless. They can only give you answers.
      -- Pablo Picasso
  3. stimulus-response too limited. by headkase · · Score: 4, Insightful

    There is still the problem of brittleness which this verb based approach WILL suffer from. Each verb represents a concept and unless you allow concepts to overlap (probably using fuzzy logic) you will end up with situations where the mapping of the user input does not match the preprogrammed verbs properly. Basically he's programming points on a line where the computer knows what to do instead of creating a smooth continuum where the computer can compute the probability of what you meant. Then as the number of verbs grow the complexity of the system increases exponentially so you need some sort of culling algorithm (maybe as simple as a list of synonyms) to reduce the choices to something that more closely fits the preprogrammed responses.
    People smarter than you and I have been working on open-ended AI for a long time and there's still no solution yet so I wouldn't get my hopes up too high for this program.

    --
    Shh.
  4. How is this different? by paintswithcolour · · Score: 4, Insightful
    How is this different from the Interactive Fiction programming languages that are already out there?

    The limitations of these languages have generally always been with the developer not in the chosen language, so I'm a little unclear how this will make inherently more immersive games. I'm not even sure it looks easier to use (this is a little unfair as I'm judging on screenshots), but the language 'Inform' has made leaps forward in this area with a natrual language system. Or designers can use 3rd party GUI tools to assist with construction in many of the IF languages. I'm skeptical of how this will compete with the games developed with other languages and made freely accessiable in the IF archive.

  5. Seems like most people are missing the point. by Wordplay · · Score: 5, Interesting

    This doesn't compete with Inform, TADS, or any of the narrative languages, at least in a meaningful way. As best I can tell, this approach doesn't even allow for a traditional guided narrative at all.

    You have an initial setup (there's your bit of narrative). You have Stages, Verbs, Actors with Inclinations (personality), and Roles (which are sets of reactions).

    You, the player, and the Actors can all perform Verbs. Performing a Verb on an Actor causes a reaction, defined by a Role assigned to the Actor. Actors semi-autonomously react, within their Roles, by performing Verbs on you and the other Actors. The Verbs they pick are constrained by the Role, and weighted by the Actor's Inclinations. Actors also choose to wander between Stages according to Inclinations, which increases or decreases the possibility that two actors meet. The important bit is that all of this is cyclic. If I do something to Actor A, Actor A may react by doing something to Actor B, who in turn reacts...etc. Or Actor B may just have -witnessed- what I did to Actor A, and then goes off and gossips to Actor C, who...etc.

    So, basically, any story is emergent. You define Actors, Stages, Verbs, Inclinations, and Roles, so as to guide the Storyworld towards a particular type of theme, but from there, you (the architect) don't have very granular control. I suppose you could program an Actor as the MoverAndShaker, whose agenda (through some pretty absolute Inclinations and Roles) is basically to wander through the Storyworld and provoke people in the direction you want.

    In any case, note that this type of storytelling can be very successful. Facade works much this way.

    It's a really interesting setup. In its current form, I'm not sure how successful it be for game-authoring, if only because the game interface seems to be Actors' talking heads plus a diagrammed language. It's pretty obscure for any sort of casual player. But as a core technology and an authoring system, I think there are terrific possibilities for this. I'd be especially interested in a hybrid between this and traditional guided narrative.

  6. Interaction is the Enemy of Narrative by dforsey · · Score: 5, Insightful

    The basic problem with interactive fiction is the interactive part... :-)

    A player is extremely unlikely to make the choices and take the actions that lead to a compelling story.

    They won't make the mistakes that lead to King Lear or Hamlet to their tragic ends.

    They won't make the choices that take Luke Skywalker to defeating the death star (not if they have real choices that affect the storyline)

    A good story takes the reader through a series of psychological stages resulting from the characters making choices a player is unlikely to make. (they just look up the "right" answer on the net...)

    I would be more convinced if Crawford had a single example: mockup, text, an animated video - anything - that demonstrated how a working game would play in a (even a 15-minute) gaming session.

    I don't even want a working system at this point - show me a walkthrough so we can get an idea of what game play would be. (it would be nice it that doesn't require the strong AI problem to be solved first as well:-)

  7. Some overall comments by Chris+Crawford · · Score: 5, Informative
    I'm quite surprised at the amount of activity in response to this article; somebody just advised me of it and it appears to be rather busy. Here are some generic responses:

    1. First, there are always skeptics and naysayers who have disparaging things to say about the Storytron technology. Some of this is due to the fact that my often harsh criticisms of the games biz have antagonized many people. That's OK -- but I just want to advise other readers that some portion of the negative comments are a response to my comments about the games industry, not a response to the Storytron technology itself.

    2. Second, I remind everybody that Storytron technology is exceedingly complex, largely because narrative is exceedingly complex. I have spent years trying to trim it down to the absolute minimum required to do the job, but that absolute minimum is still overwhelming to beginners.

    3. I'm always surprised by the comments along the lines of "How does this differ from Technology X?" All I can say in answer to such questions is "read the documentation". Storytron technology is so utterly different from role-playing, MUDs, interactive fiction, and other technologies that it's difficult to know how to begin to answer such a question. It's rather like somebody asking you the difference between a spreadsheet and a word processor. Well, yes, they do both allow you to set fonts. They both allow you to create tables. They both allow you to print out documents. But they are so completely different in form and purpose that it's a waste of time trying to come up with a list of differences. The easiest way to differentiate Storytron from the other stuff is to cite its purpose: to provide genuine, honest-to-gum interactive storytelling. (See next point)

    4. A common question (already offered here) is, "What is interactive storytelling, anyway?" If you attempt to answer this question by comparing it to other forms, you get confusion. Interactive storytelling cannot be described as "just like a game, only..." or "kinda like interactive fiction, except..." This approach always yields even more confusion. I haven't spent 14 years re-inventing the wheel -- this thing really is profoundly different from other stuff out there. The closest to it is Facade -- and Andrew Stern and Michael Mateas will be quick to point out the many, many differences between Storytron and Facade.

    It's not a story, it's storytelling, and the difference between the two is profound -- and confusing. A story is noun or data; storytelling is verb or process. That's why there's not a plot in it; only stories can have plots. Storytelling does not intrinsically include plot. Think of it this way: the difference between story and storytelling is analogous to the difference between a cake and cooking. A cake can have texture, but cooking doesn't have texture. Texture is a consequence of cooking, but not a component of cooking. In the same way, plot is a consequence of storytelling, but not a component of storytelling.

    So what is it? As we have built it, interactive storytelling puts the player in the role of protagonist in a dramatically rich environment, and then permits the player to interact with other actors in a dramatically rich fashion. The size of the verb vocabulary is what makes it so different; Storytron can provide thousands of verbs. No more just picking things up, using them, destroying them, and so forth. Most of the verbs provide interaction with PEOPLE, not THINGS. We already have about 80 verbs (few of which are fleshed out, though) and intend to have hundreds by the time we release the technology.

    Anyway, if you want to learn more, go to the website.