Storytron: Interactive storytelling platform for nontechnical authors

Legendary game designer Chris Crawford has disclosed some information about his next big project, an interactive storytelling platform called Storytron.

I saw a demo of Storytron this weekend, given by sf writer Laura J Mixon (author of the early cyberpunk classic Glass Houses), who's working on the project. It seems like there's a lot of potential there — it's basically an engine for describing autonomous game-AIs that exist to move a story forward. The toolkit is simpler than learning LISP, but harder than rolling up a quickie avatar in WoW — the kind of thing you're going to have to care about before you get good enough to see much in the way of results. I think that code examples and libraries of user-created characters can make the hump a little shallower — but this is a tool for storytelling, and there's no getting around the complexity of that task.

Mixon described her aha moment with the technology — she'd defined some characters and set out to "play" or "solve" the story they inhabited. She happened upon these little automata, going about their daily round, and then watched slack-jawed as the two characters improved a totally spontaneous argument that made perfect sense in the context of the story she'd set out to "write" in her design, but which she had not anticipated, written, or hinted at. The game took on a life of its own and inserted some reasonably good dramatic fooforaw at just the right moment — the computer was telling her the story.

Now, that's pretty cool.

CC: I will not claim that it is superior to conventional algorithmic notation. We simply won't know that until people start using it. I'm playing a hunch here. Perhaps the most useful observation is that we don't have to be locked into algebraic notation.

DDJ: How else does SWAT accommodate nontechnical types?

CC: The storybuilder does not get to create types. I create the types. And every [datatype] is color-coded: Booleans are black, actors are blue, quantifiers are purple. I think this is useful for amateur programmers. Another thing: Runtime errors are survivable. It happens by virtue of the design of the system that runtime errors only occur when we are considering an action or changing something, and when that happens, we say it poisons that calculation. This invokes a system called "Poison" that logs it for future reference. "Rehearsal," our testing feature, plays the storyworld one way, adjusts a random number, does a thousand passes, and then presents you with a statistical analysis. You had this many poisoned events. Looping cycles. Thread killers.

Link

(via /.)