Introducing Versu

Versu is a new interactive storytelling platform Richard Evans and I have been working on at Linden Lab. Some of you may have seen lead-up presentations about it at GDC (possibly long enough ago that it was still called Cotillion).

versu_logo

Today, the first four Versu stories are available for iPad. Clients for Kindle and Google Play will follow, as well as stories in other genres and by other authors, and both character- and episode-authoring tools will be made available to the general public in the future.

whist_game01Versu focuses on character interaction as its primary form of play. The Versu platform can do rooms, objects, movement, and the “medium-sized dry goods” interaction of a typical interactive fiction engine, but it’s primarily designed for interactive stories about people: how they act, how they react to you, how they talk to you and talk about you, the relationships you form with them. The social landscape in which you act is constantly changing.

Versu uses an AI engine designed by Richard Evans, the lead AI designer for Sims 3, which allows each character in a story (and in some cases a drama manager AI) to act autonomously or be played by a human player.

Because there’s a strong social model at work in Versu, it’s possible to form relationships with characters that the story author did not explicitly create. In play, you can decide you want to pursue a romance or make an enemy, and that outcome can occur even if the author did not write an arc specific to those two characters.

Versu has a choice-based interface, but it’s very unlike standard CYOA. At any moment in the story, you can choose to act, or wait for others to act. If you choose to take action yourself, you’re offered a set of options drawn from the world model at that moment, from taking a bold stand to giving someone a significant sideways glance. Just about everything you can do affects your character’s opinion of the other characters, and theirs of you, altering the playing field for what’s to come. Inaction can be a powerful choice.

lucy_happyVersu offers moments of narrative emergence. Late in testing, one of my characters was talking to another in confidence when a third party wandered in. Because the speaker didn’t feel comfortable around that third person, he fell silent and didn’t continue the conversation — there was an awkward pause and dialogue moved on to other things. I’d never written the “awkward pause when X walks in on a private conversation” outcome — just an engine that knew when the characters would be willing to discuss those topics, and also that it was awkward for someone to stop talking about a conversation topic when others were expecting them to go on.

This can happen elsewhere too, in large and small ways. The degree to which emergent character behavior affects large story outcomes depends on how flexibly the author has written the overarching plot. “The Unwelcome Proposal” is an example of Versu being used very conservatively, capturing as much as possible of the story text from a scene in Pride and Prejudice, and allowing for few deviations from that story. “House on the Cliff” and “A Family Supper” have a much broader spectrum of possible results, depending on character choices and relationships. Even more sandbox-like experiences are in the pipeline.

brown_inspiredVersu allows for characters who act distinctly. A social model is only interesting for building fiction if it doesn’t make everyone act like identical automata. In Versu, different characters are built with different abilities and parameters — not a handful or a few dozen character traits, but a potentially infinite range of quirks and habits. It is possible to craft social behaviors that are unique to just one character — giving one guy the ability to get under people’s skin more than anyone else, say — or to make a character who hates being in a crowded room.

In addition, because characters are defined as separate entities in this way, they could be transferred from one story context to another, and even cast in stories that weren’t specifically written for them.

The stories we’re releasing today are just a taste of what is possible with this engine. I’ll post more of my usual analysis content over coming weeks — what it’s like to write for Versu, the difference between authoring characters and authoring stories, details of the conversation modeling system, and more about what we’re expecting to see in the future.

Future Voices (inkle)

Future Voices logoFuture Voices is an iOS-based anthology of eleven CYOA stories from inkle, culled from an open competition. As one might expect from inkle’s work, it’s an aesthetically pleasing object: it uses Frankenstein’s imagery of pieces of paper being attached to the end of an ongoing, developing story. Proofreading is not flawless — I ran into a handful of typos here and there — but this is a fairly rare problem, and overall the app is an elegant-looking piece of work, tactile and classy.

I’m also delighted to see someone running with the concept of anthologized interactive narrative: curating and promoting the best material from the wide variety of freeware is still a really useful role for publishers or publisher-equivalents. And I gather that the competition leading to this anthology drew work from a wide range of authors, some of whom had no previous experience with interactive writing.

Continue reading “Future Voices (inkle)”

Making of Counterfeit Monkey: Puzzles and Toys

This is the first of a couple of making-of posts about Counterfeit Monkey, in case people are interested: these are a bit like some of the making-of material I’ve published about Bronze and other games, but I’m splitting it up between story discussion and puzzle discussion.

We’ll start with puzzles. This is going to be spoilery, so if you’re still planning to play, I recommend finishing the game first.

Continue reading “Making of Counterfeit Monkey: Puzzles and Toys”

Zero Summer: Fifty Miles South of Lexington

Zero Summer IconIn November I wrote about the StoryNexus game Zero Summer. At the time I didn’t play their for-pay content, Fifty Miles South of Lexington, but I’ve done so now, and it deserves its own discussion. Fifty Miles is its own short story, which you can buy from within the main game of Zero Summer using Nex, once you’ve progressed far enough to move around town a bit.

From the StoryNexus perspective, Fifty Miles South of Lexington is pushing the envelope of what the engine can do. Which is a good thing! Every new storytelling engine needs some content that pushes it to or beyond its capacity; that’s how the formal capacities of the machine are discovered. Experimental stuff typically feels just a little bit odd, though, just because it is doing something that may be hacky and weird for the affordances of the toolset. Consequently, the following is a review both of the content of Fifty Miles and a discussion of StoryNexus’ ability to cope with this kind of content.

Continue reading “Zero Summer: Fifty Miles South of Lexington”

CM Release 3

Once again, the Monkey site contains an updated release of CM that doesn’t handle all the bugs reported, but cherry-picks the ones that seem to be causing the most confusion to the greatest number of players, or that were extremely easy to fix.

Among other things, this includes improvements to the handling of the car; greater clarity in the “utilitarian-style” inventory listing about what is being carried in the backpack or worn at the moment; some debugging of issues with hard mode; and the addition of a number of objects that really ought to have been possible to generate.

Rot13’d change log for releases 2 and 3 after the break.

Continue reading “CM Release 3”