Interactive Jane Austen Novels

Versu is an interactive storytelling platform just released today by Linden Lab.

Basically, I see it as Chris Crawford's Storytron, except done right. It's a collaboration between IF author Emily Short and AI expert Richard Evans, combining written stories with sophisticated character and drama AI. So far it's basically interactive Jane Austen novels (seriously!), but it can support any genre of fiction, and more stories (and the tools for making them) are on the way.

You can read Emily Short's description of it and see some quotes from the Linden Lab CEO Rod Humble if you want to learn more.

I first came across this when it was demoed at GDC (before LittleTextPeople was acquired by Linden Lab) and I've been eagerly waiting for it to come out. Unfortunately, right now it's only available for iPad, and I don't have one. :( But it sounds like it will be coming out for other platforms eventually.

I recently started working at Linden Lab myself, and this project is a big reason why. Can you imagine something more revolutionary being done right now? :D

So, here we have interactive experiences fueled on storytelling, not gameplay. Sign me up.

Oh, and I almost forgot - Happy Valentine's Day! :) No new game from me this year, sorry (I went for something a bit more... personal). You could always just play The Love Letter again... ;)

How Artists Want to Make Games

On the notgames forum, Michaël Samyn posted this thread:

Programming in code is counter-productive for people with art-sided brains. The solution to this problem exists: graphical programming. But the people who need to implement this solution happen to be its worst enemies. Because to engineers, code-based programming beats everything.

Until somebody somewhere starts believing artists when they say they want to program in a visual language, or starts realizing that giving access to artists is the best way for a creative technology to continue evolving, I find myself settling with inferior designs. Because I cannot express myself adequately in code, I need to change my ideas, I need to talk about simpler things in a simple way.

It's like someone is forcing me to write poetry in French. French is a great language. And people who are familiar with it can write beautiful poetry. But I speak Dutch. My Dutch poems are subtle and sublime. In French, however, all I can write are nursery rhymes.

So I've been thinking about this a lot over the last several days. Actually I've been obsessively thinking about it non-stop and reading everything I can on related topics online.

I tend to do that for a different thing every week. This week, it's been this.

So there are a few pieces I've been focusing on, that seem most crucial to the success of a programming or game development tool for artists. There are probably others, but I thought I'd share what I've been thinking about so far.

One is readability through R-mode perception.

First of all, a disclaimer: When I say "R-mode" versus "L-mode", as in "Right brain" or "Relational" or "Rtistic" versus "Left brain" or "Logical" or "Linear", I don't mean to suggest that the brain is really divided into strict differences between its physical right and left halves. That is an outdated belief. But I find the terminology to be a useful shorthand.

Thinking on Michael's comments about visual flowcharts being easier for him to read than linguistic code, and looking back on my own experience, I think there really is something significant about how the code is presented and perceived, even when the underlying logic is the same.

When I am reading code (or a book!) I am usually using what I call "L-mode" perception - going through in a linear, linguistic way, and building up my mental model one step, one line of code at a time, following the logic that is expressed symbolically, in sequences like that.

However, sometimes my mind is in an "R-mode" of all-at-once, spatial perception like you'd use for looking at a painting or trying to find a certain LEGO piece in a big box of pieces. When I am in that state of mind, and I look at code (or to a lesser extent, written language) I see all the words at once and perceive the spatial relationships between them, and the underlying logic of the code is utterly incomprehensible to me. Obviously not the "right" way to read code.

But maybe it could be.

Ha, that would be a good tagline. "The right way to code." :P

The thing about R-mode perception is that it's a lot easier to be creative when you're in it. The other thing about R-mode perception is that artists are usually a lot more skilled at functioning in R-mode than they are in L-mode.

Therefore, if you had a tool that let you do programming while in R-mode rather than L-mode, it might be slightly easier to do creative things with it. At the least, there would be less inefficiency caused by switching between R-mode and L-mode whenever you think about what you want to change and then have to dive into the code to actually change it.

However, this may not even be possible.

All the visual programming editors I've seen, all the examples that have been posted here, require an uncomfortable mix of L-mode and R-mode perception in order to use. What I tend to see is a bunch of visually identical boxes connected by lines, and differentiated by text.

What you see in R-mode is the set of relationships between the boxes. But you can't tell what each of the boxes does. To do that, you must read the text and think symbolically, in L-mode. Really, very little information is conveyed through spatial relationships, through R-mode. Most of it is still sequential and symbolic.

For that reason, I find that pure written code, all L-mode, is much easier for me to deal with, since I don't need to switch around multiple times a second just to figure out what everything means. However, I suspect that there may be a way to create a pure R-mode method of programming too. But I'm not confident that it's actually possible. Just intrigued enough to try.

There are some programmers who hate the idea of visual programming, and say that it's a waste of time to use spatial relationships to convey the meaning of code. If you are one of those people and you use syntax coloring or indentation, you are a hypocrite.

So there's one aspect. Make sure your tool is R-mode accessible, if you want artists to be able to use it.

The second thing is building with functional pieces in real (or almost real) time.

Artists tend to appreciate tools where "what you see is what you get" - you're manipulating the end result, so you can immediately see the results of your actions. The process becomes more like sculpting.

Programmers tend to discount such tools as nice but unnecessary. They are used to typing in code for an hour, hitting a button, and waiting a minute for everything to compile and show up on the screen.

These are two fundamentally different mindsets, as different as a slideshow and an animation.

When you operate in the slow, "slideshow" approach, development and creativity tends to happen in an architected, "top-down" way. You have a plan, which is in your head, and then you put in a bunch of time and hard work to mold reality into the shape of that plan.

There is a fundamental shift that occurs as you decrease the time between action and result. It's as real as the shift that occurs when you hit 24 frames per second - from slideshow to animation. To your brain, it's alive, it's moving.

When you operate in the immediate, "animation" way, development tends to operate in a more exploratory, "bottom-up" process. You don't have to have an entire plan in your head. You see the results of your actions immediately, and if they are surprising or unexpected, you can adjust your plan. You can try random things and follow them if they prove to be interesting.

In the area of game design, innovation is much more likely to come out of an exploratory process than an architected one. As Jonathan Blow said earlier. It's hard to do things that haven't been done before if you have to plan it all out in your head first.

So we want a tool that allows us to sculpt the end result, with immediate feedback.

Part of this is that everything you can make should work. It may not work in the way you desire or expect, but it should still do something.

If you are painting with pixels in an art program, no matter how you put those pixels down on the screen, it will always be a functional, viewable image. It might not be pretty, but you can still see it. You are never going to run into a error message that says, "Invalid pixels at position 55, 46. Image cannot be displayed."

But if you are writing the code for a program, this sort of thing happens all the time. Most of the things you can type won't work at all. They won't turn into a program, even a broken one. There are right ways to write code, and wrong ways to write it.

I would say that this also makes a big difference. Perhaps the biggest difference is that writing code has a much higher barrier to entry, more learning how to do things at all before you can start learning how to do them well. But it also makes experimentation so much more difficult. You can't throw a bunch of random stuff together just to see what happens. Because what happens is nothing. It just won't do anything at all.

So if you can build only with pieces that work, and immediately see what changes, this would make truly artistic interactive art much easier to create.

The last thing is expressing general logic through specific examples.

This is probably the most impossible and most revolutionary but least important of the three. If you just had a tool that you'd use in R-mode, that let you shape the end results with immediate feedback, that could be awesome, and probably enough to make a huge difference.

But at the same time I am intrigued by this further vision I have of providing specific examples, which the system will extrapolate to create possible general rules for creating those examples, which you will then provide feedback on and refine in order to guide the system's hypotheses toward the end you have in mind.

Because I don't see how to actually avoid symbols when describing logic, or how to directly manipulate end results in a general way. Because games are systems, and the end results happen when you take the rules that you have set up and run them through their paces.

So maybe this is the only way to achieve those first two goals in their entirety.

What am I talking about?

You know how you draw diagrams and mockups for different things that happen in different situations in a game? Like this. It's a pretty common way to organize your thoughts when you're designing. The thing about those is they're all organized around specific examples, not general rules. So you might draw a diagram with a guy hitting a wall, showing how he bounces off or breaks through it or whatever. It's not completely specific, as you might have an abstract line standing in for any kind of wall, and a stick figure representing any kind of guy, but at the same time it's very concrete. And you can add general connotations by writing in little notes, to explain the rules behind the example more clearly.

The reason that we don't just stop there is that our game development tools require everything to be spelled out exactly - they cannot extrapolate from these examples, because there is so much ambiguity. It could mean this or it could mean that.

However, we run into a similar problem when trying to communicate our ideas to other people who are helping us make them into a reality. Especially if we are designers and we are telling programmers what to do. How do we solve this problem with other people?

Part of this is by clarifying with more examples when an area is unclear. Kind of starting at the highest level and breaking it down into more specific situations when necessary. Another part is through conversation, asking "It sounds like you're describing this... Is that right?" and responding "Yes, exactly!" or "No, I was thinking something more like this..."

Both of these could be accomplished with a special computer program instead of a human programmer. Maybe not as well, especially in terms of accuracy of translation, but in some ways better - particularly, in the time between your description of a design and seeing something on the screen. And this increase in speed could make up for the lack of accuracy, since you can adjust and correct much more quickly. And as a result, make use of exploratory design instead of architecture.

Break dynamics down into stories instead of rules. A playthrough of the entire game could be an example story, and you could create example stories of successively smaller and smaller pieces of the game until you have specified it completely. Or completely enough.

The tool generates possible rules that could create the situations you specify, and presents several for you to try out. Most likely none of them work the way you want. Pick the one that's closest, and let it generate more possibilities based on that. It's an evolutionary search. Like Biomorphs.

And stories don't always have to be specific stories about specific instances. They can be more or less abstract and universal. Like Raven, with a capital "R", who is both the character Raven and all ravens and all tricksters at once. Or the princess in the tower, or the wise old man, or the dragon in the cave. Or the stick figure on the crosswalk sign who represents all pedestrians who could ever walk this way. There is a continuum between the specific and the symbol.

I am particularly inspired by the concept of the Dreamtime. The translation of this name is misleading, as it does not refer to a time in history. It is like a parallel slice of the world running alongside and underneath the specific, physical world, where the gods and heroes walk, creating and personifying the dynamics and processes that underlie everything we see in reality.

I want a tool where I can not only shape the world as a level designer, but also shift into the Dreamtime and shape the dynamics of that world as concretely I would shape the placement of coins and mushrooms.

When this happens, we will get our interactive art.

Active Sketch 03 - Words

Update:
Reviewed by Gregory Weir, the author of Silent Conversation! :D

A new prototype.

It's an attempt to turn a text into an interesting environment for a game, along the lines of some of my earlier thoughts. I was never really satisfied by Silent Conversation's take on the whole "text as environment" thing, and I've been trying to extract some meaningful gameplay out of the words themselves.

So this is where I'm at so far.

Active Sketch 03 - Words

The goal is to match similar words. Use the arrow keys to move around. You can pick up a word by pressing x or c.

On the right is your score, and on the left is your score multiplier and the current word you are holding. If you match two words exactly, your multiplier goes up. If you pick up two words that have no letters in common, your multiplier is halved. Otherwise, you get points for each letter the two words have in common, multiplied by your score multiplier. I stole the multiplier system from Music Catch.

There is no time limit, and words reappear after they go off the screen, so you can get as many points as you have patience for. It's not a game. It's just a test.

The story is something I wrote over a year ago, a retelling of Where the Wild Things Are with the themes of Ishmael, in the style of a Haida myth. It still has a sappy Western ending, though.

The lines that end in "they say" are the canonical elements of the story - actually two stories, Where the Wild Things Are, and Genesis. That's based on a Haida mythtelling convention, more or less. The symbolism and structural harmony and such is woefully inadequate compared to the stories of the master mythtellers, but hey, it's my first try.

Anyway, the story doesn't matter. It's just filler text to test out the matching mechanics. :p

Try it out and let me know what you think.

they will eat you up...

Thoughts on the EXPLORE Contest

I'm working on a project with brontosaurus.

We have seven days to submit a game for the EXPLORE contest at Jay is Games. I like our current idea, and I think we should keep going with it. But even if we can put it together in seven days, I'd want to take at least another seven days to playtest and polish it. In other words, I don't want to rush this for the contest.

We could take a break and make a short, quick game for the contest just for fun, not expecting to win anything. I had a few ideas for that. One is to use our conversation history as the game content, since we have plenty of it, and it's interesting. There are a number of ways we could use it, but one very simple way to do it would be combine it with the Linear RPG. Or the typography could be a physical space to traverse, like Silent Conversation, with emoticons as powerups or something.

I was thinking about the Stick Figures story in Tales from Outer Suburbia, and where the story is, or where you might find a game there. It seems to just describe a scene, a place, without turning it into a particular story. It's hard to identify the protagonist, antagonist, and conflict. Maybe the antagonist is actually the confusion felt by the townspeople, rather than an actual character. Who knows? But you can more easily see little stories inside of it, like a kid smashing a stick figure with a baseball bat and getting frustrated, and uncertainty turning to fear and anger.

I was thinking about games, and how you could have a persistent world that is experienced through short, repeated game sessions. Little stories inside a world. Imagine Canabalt if instead of starting over when you die, you start again in the same world, at the place where you left off, or on the ground where you landed, or as another character somewhere else. It is similar to Calamity Annie, the way the narrative progresses even as you play again, where the gameplay repeats, but the world is fleshed out as you continually revisit it.

I'm also thinking about Zero Punctuation. Our conversation history could take the role of the monologue that narrates the images in a Zero Punctuation review. The only difference is that it is a dialogue, in text and not in speech. But the communication is similar. It does not tell a story, it discusses and explains. However, if we were to do this, we'd need a way to automatically come up with the images based on the text since it is not feasible to generate so much content by hand.

Freedom of movement across an image, linear movement along a text. Text forms the goals, while images are the medium of action? One action per line of text, one visual change. How do you create images from text? How do you combine text and action to get an image? The image and text give rise to the feedback. And the text leads the progression.

I was thinking about Spirited Away, my favorite animated movie. If Canabalt is like The Matrix, what would be the equivalent for Spirited Away? For Canabalt, you take the decisions that are implied and make them explicit. Or rather, you make it explicit, since there is only one decision. What equivalent can be found in Spirited Away? What decision can be made with the press of a single button?

But Canabalt is a linear game. You decide nothing. You act, in order to experience. Can exploration be about anything other than freedom of movement? When does exploration feel linear? A map does not dictate a path. When does it feel linear? A maze might have only one path, though it looks like a map. A labyrinth, even more so. Look at the feet. They never change their rhythm, yet the landscape around them changes. Is that exploration? What if they do change their rhythm?

You could make a game where you press a button to turn and change direction. This could be freedom of movement. Is it linear? If your actions have bigger consequences later on, maybe it is not really linear. If you turn here, you got to the desert. If you turn here, you go to the ocean. In Canabalt, your actions now have their consequence now - they do not change your route for the future. Can you explore without changing your route?

I've been thinking about tension before it solidifies into an emotion. I've been able to notice this tension already several times today, and let it fade away without latching onto anything external and feeding off the imbalance that results. I imagine there could be something similar for positive emotions. It all reminds me very much of Daniel Cook's Constructing Artificial Emotions, and I am intrigued by the idea of incorporating this into a game.

Where will this take us? I don't know. We'll see.

Story in Games

Henry Jenkins is one of my favorite authors writing about games, along with a few others such as Ian Bogost and Daniel Cook. But you're not as likely to find his writing on the web. Well, maybe you are, but that's not how I came across it. :p

One piece of his, which you may not have encountered since it was published as an academic paper rather than a blog post or online article, is called Game Design as Narrative Architecture. It examines four ways that story can be expressed through gameplay, and I found it very inspiring when I read it. I thought I'd share my notes here. :)

Spatial Stories and Environmental Storytelling

Evocative Spaces
ex: American McGee's Alice

• play on existing mental mappings
• fill in broadly the spaces and moods to evoke earlier mental images formed by previous storytelling experiences
• story information spread across books, film, television, comics, games, etc.

Enacting Stories
ex: I Fell in Love With the Majesty of Colors

• let players perform or witness narrative events
• broadly defined goals and conflicts
• obstacles and affordances facilitate player's movement to resolution
• enact specific, localized incidents or micronarratives - shape emotion
• compelling framework vs. local freedom

Embedded Narratives
ex: Myst

• linear backstory separate from nonlinear experience of player
• find bits of evidence to reconstruct understanding of the backstory, and test these mental maps against game world
• distributing information across the game space, redundantly
• can mix enacted and embedded narratives
• melodrama based on the external project of internal states - spaces of mood, feeling, not just factual information

Emergent Narratives
ex: The Sims

• stories emerge from player's experience with the system
• the system is simplified, designed to maximize narrative possibilities
• characters with desires, needs that can come into conflict, with emotional responses to events, and consequences to their choices
• designing spaces to have poetic and symbolic potential

In Summary

evoked - new perspective on existing story

enacted - story about movement through space

embedded - discover and reconstruct story from clues

emergent - create new stories from experience

I think that games have barely scratched the surface in storytelling. If someone tells you that games can't tell stories, or that there's only one way for games to tell a story, well, I'd say they're not looking very hard. There is quite a bit of interesting experimentation going on if you know where to look. The Path and (I Fell in Love With) The Majesty of Colors are just two recent examples. Distributed narratives make up another intriguing offshoot. It's all very fascinating to me.

Another paper by Jenkins, very thought-provoking, is "Complete Freedom of Movement": Video Games as Gendered Play Spaces. It's fairly long, but well worth the read. Take a look! :)

Review of A Story as Sharp as a Knife

In an earlier post, I mentioned that the one artform with the most relevance to games is myth. Here is a review of the book that lead me to that conclusion.

A Story as Sharp as a Knife:
The Classical Haida Mythtellers and Their World
by Robert Bringhurst

This book is about myth, and how to understand this ancient art form in a time when we are so far from the sort of social context in which myth was the primary way of making sense of the world.

What do you think of when you hear the word "myth"?

Perhaps the most frequent way the word is used in our modern, literate society is to refer to a story that is false, an explanation that is incorrect. This is not the sort of myth to which Bringhurst has devoted over four hundred pages. Another place we might encounter the word is in museum exhibits or books about ancient history, where we read "myths" as the rather fanciful religious stories of those cultures yet to be blessed with a scientific understanding of the world. This sense of the word is somewhat closer to what Bringhurst is concerned with. But there is an important difference.

Myth is a performance art. It is oral poetry, storytelling. When we open a book and read "the creation myth of the ancient Egyptians" what we find is a fossilized skeleton that reveals no trace of its original vitality. As Bringhurst convincingly shows, the art and value of a myth is in its individual, idiosyncratic telling. If we read a summary of a myth and assume that that's all there is to it, we are no better off than someone who tries to understand a masterpiece of jazz improvisation by looking at the song's chord changes. In the case of myth, the story isn't enough - you need a transcription of the artist's actual words, just as you'd need a transcription of the actual notes that were played in a jazz solo. Better yet, listen to a live performance.

As you might expect, however, live performances of mythic storytelling are hard to come by nowadays. We are lucky to find even a faithful transcription of such a telling, as it is a rare anthropologist who has understood the importance of taking precise dictation rather than recording only a summary. One notable exception was the linguist John Swanton, who in 1900 went to live with the Haida people off the northwest coast of Canada and transcribed thousands of lines of oral poetry. Then in the late 20th century, Robert Bringhurst managed to come across Swanton's work.

Bringhurst's background is in poetry, not anthropology. As a result, he has been able to see in these old transcriptions a quality that most others have failed to appreciate. And with his book, A Story as Sharp as a Knife, he provides a means for others to begin to understand what is so great about these classical Haida myths and about all myth in general.

The book's subtitle is The Classical Haida Mythtellers and Their World, and in it you will find a tour of that world, organized around a selection of about a dozen myths. It's a tour that you may repeat many times, or just skip around to the parts that interest you. The book doesn't set out to prove one particular point, and there is no explicit introduction or concluding chapter to summarize the book for you - the prologue gets you started on a journey, but it doesn't provide a map of what you'll encounter.

Each myth featured in the book serves as the reference material for an investigation into a different aspect of mythtelling. In each section, Bringhurst provides some historical and cultural background, followed by the translated myth transcription itself and an analysis, highlighting certain passages and occasionally bringing in outside connections such as Renaissance painting to compare or contrast with Haida mythtelling traditions. The main chapters of the book are supplemented by an extensive collection of notes, as well as several appendices on language and translation concerns.

Of course, there are plenty of things that the book doesn't do. It doesn't give you a large number of myths, just enough to give you a feel for them. Neither does Bringhurst go into much detail about Haida culture or mythology beyond what is required to understand the particular stories he presents. And while obviously a great deal of research went into writing this book, everything in it is either historical fact or the author's personal interpretation; it is not what you might call a "scientific" book. Not that that's necessarily a weakness, but it would be nice to have further verification of his views through another source or the support of a fleshed-out theoretical framework. What you can expect is to gradually gain a unique appreciation for myth through the experience of reading the book.

Though it is difficult to reduce Bringhurst's investigation into a single question or argument, there are several identifiable threads connecting the many observations and explanations distributed throughout. Some of these are simply context, the stories of villages and mythtellers and anthropologists, together covering the who, where, and when of the subject. The others could be thought of as supporting the main theoretical concern of this book, the what, how, and why of mythology.

One of these threads, answering the question of what is the nature of myth, explains that myths are living things, perpetuated through human minds because they are deeply meaningful. Together, many myths form an ecology, a living mythology, in symbiosis with a human society. This mythological system exists to make sense of the structure and dynamics of the world, how the world works and how it is organized. While it is still alive, every mythology is an ecosystem that continually evolves as individual mythtellers reinterpret the stories in terms of their own understanding of the world. As Bringhurst writes, "A genuine mythology is a systematically elaborated, extended, interconnected and adaptable set of myths. It is a kind of science in narrative form."

Another thread, which deals with how people convey meaning through myth, emphasizes the importance of individual tellings, that the way myths convey an understanding of the world depends on the details of a particular artistic performance. Myths make use of archetypes, themes, plots, and patterns, but these are building blocks - they are not the essential message. What matters is how these elements are connected and arranged to create new meaning: "A story is, in fact, a sentence: a big sentence saying, or revealing, many things that a full list of its components cannot say." When myths are reduced to summaries and stereotypes, as has sadly been the case in a vast majority of anthropological work on the subject, "we lose all the learning and insight, perception and wisdom, that the myth has been used to convey."

The other thread, of why myth takes the form it does, contrasts myth - oral narrative poetry - with other art forms such as verse poetry or prose. Bringhurst makes the point that myth can only thrive as myth in an oral society, one without writing. Verse poetry may also exist in oral societies, but only in those that make their living through agriculture rather than hunting. "Humans, as a rule, do not begin to farm their language until they have begun to till the earth and to manipulate the growth of plants and animals." The argument there is that the structure of mythic poetry has a spatial quality reflecting the irregular order of the forest rather than the uniform repetition of the cultivated field reflected in verse poetry. Myth can be very musical in its own way, but as a music of thoughts and images rather than sounds.

That last thread helps explain why historically so many anthropologists have misplaced the significance of the myths they encountered. As members of an industrial, literate society, they were ill-equipped to understand story in the same way as their hunter-gatherer subjects. Words simply do not have the same role or meaning in oral societies as they do in literate ones. According to Bringhurst, "In a self-sustaining oral culture, faith, hope, and even charity are invested very differently than in cultures that are learning or have learned the use of writing. A shift from oral to written culture affects the functioning of memory, the understanding of truth, and the place of voice and language in the working of the world. It affects not just the meaning of words but the meaning of language itself. It affects the meaning of meaning."

If only those anthropologists could have read A Story as Sharp as a Knife before they went forth to capture the traditions of those people who had yet to be enveloped into industrial global culture! Time warps aside, those of us in the 21st century now have an excellent opportunity to acquaint ourselves with the mythic mindset through Bringhurst's book. When you first start reading the actual myths, you will likely feel somewhat out of place, getting used to the translations, the unfamiliar storytelling style, and the initial strangeness of the stories themselves for those unaccustomed to Haida mythology and culture. But as you become more familiar with the style and learn how to appreciate the myths through Bringhurst's insightful analysis, they become quite enjoyable in their own right.

The book is not dense, but it is long and there is plenty of material to chew through. There's such a variety of ideas to absorb that you'll likely want to spread out your reading of it, enough to appropriately digest each topic. It is a thoughtful book that paces out its most fascinating bursts of insight such that the interested reader will remain eager all the way through its four hundred pages of discussion. And by the end of it you'll have developed a new appreciation for myth and oral storytelling, and perhaps even an interest in discovering more about this often neglected subject.

In other words, read it! :D