Showing posts with label interactive fiction. Show all posts
Showing posts with label interactive fiction. Show all posts

Thursday, May 16, 2019

Capsule reviews, vol. 1


Capsule reviews are short critiques of games that I've been playing. In this post, I discuss Heaven's Vault, Virginia, Islanders, and Two Point Hospital. There's no specific story spoilers, but I do talk about how I think the games work.

Heaven's Vault. The dynamic branching and language system is great and impressive, and the Muslim-inflected sci-fi art direction feels fresh. It's basically a must-play for anyone interested in narrative design. (Maybe the main weakness is the less-than-relatable characters, who basically feel like vehicles to bring about plot beats. Which is probably how the narrative system works! Hmm.)

The game pacing feels awkward for much of the game. You get to do one fun archaeological linguistics detective scene every hour, but to get there, you have to sit through an uncomfortable water slide mini-game. It's meant to give a sense of journey and a bit of rest (as well as pad out the game length) but it's a bad sign when even the fast travel options here feel inconsistent and confusing; sometimes the game lets you go back to your ship cabin to ask for fast travel, and sometimes not.

But also just on a core minute-to-minute basis, the movement and camera never felt comfortable for me, and The Last Express styled character animation never stopped feeling like a crutch for scoping down production costs. It's interesting how this project made so much (very impressive) progress on "hard" game design problems like dynamic narrative or language simulation, but then tripped on what's considered relatively "easy" solved design problems like 3D character movement, game feel, or encounter pacing.

Again, though, I still think this is a must-play for anyone working in narrative. Just soldier through the less fluent parts.

Monday, November 26, 2018

Notes on "Sparkling Dialogue", a great narrative design / game writing talk by Jon Ingold at AdventureX 2018


My colleague Clara Fernandez-Vara pointed me towards this great game writing talk by Jon Ingold this year at AdventureX, an excellent narrative design conference in London. Unfortunately the Twitch video of the talk is hard to follow and the YouTube version of this talk is still forthcoming, so I thought I'd summarize the talk here because I found it very useful. As of December 1st, the YouTube version is now online!

(NOTE: This post isn't a transcript of Ingold's talk. It's a summary with my interpretations, and I might be wrong or misunderstanding.)

Ingold begins with something that should be obvious and uncontroversial to everyone: generally, most video game dialogue is poorly written. This isn't to say video games are bad, or that they we shouldn't try to do any dialogue at all. There are also many reasons why game writers are forced to write poorly, whether it's because of lack of resources, or last minute changes in the design, or other production constraints, etc.

The point is not to blame writers. The point is to highlight a problem in the craft and to define a better ideal. So, how can we write more competent game dialogue that is slightly less embarrassing?

To demonstrate the problem of typical video game writing, Ingold shows us this conversation from the first hour of Assassins Creed Odyssey in the starting mission "So It Begins":

Tuesday, August 28, 2018

Darner's Digest, vol. 2: Why I made two new Yarn tools


Darner's Digest is a series of occasional posts about the game dialogue system Yarn.

Last time, I talked about some Yarn community news. As I've written before, I've become a sort of community booster for Yarn and Yarn Spinner because I want to see it become a standard in game narrative design -- I think it occupies a nice middle-ground between frameworks that try to do everything for you vs. coding a system yourself.

This time, I'm making the Yarn news myself. I've released two free open source Yarn / Unity tools for people to use, and I reckon they're darn good:
  • Merino, a Yarn script plugin for the Unity Editor, with built-in syntax highlighting and playtest preview. With Merino you can easily test the flow of your interactive stories without leaving the textbox or the Unity Editor.
  • Ropework, a Yarn-powered visual novel template for Unity. With Ropework you can control scene changes, sprite rendering, and sound playback, all from Yarn scripts -- and you can basically make a visual novel without writing C# code.

Wednesday, July 18, 2018

Darner's Digest, vol. 1


Darner's Digest is a series of occasional posts about the game dialogue system Yarn.

As I've written before, there are a variety of different narrative system plugins to use with Unity. Fungus is a full visual scripting solution ideal for beginners, Ink is great for text heavy games with huge word counts (like 80 Days), and Yarn / Yarn Spinner is a lightweight extensible Twine-like dialogue system for games about occasionally talking to characters (like Night In The Woods).

I don't know what's going on in the Fungus community, and I loosely follow Ink -- they are running an upcoming Ink Jam to encourage new users, and the maintainer Inkle Studios is doing exciting dynamic narrative research in Inkle with their upcoming game Heaven's Vault.

However, I can definitely speak to more detail about what's happening with Yarn these days though, so here's my attempt to recap:

Saturday, September 23, 2017

Writing stories / dialogue for Unity games with Yarn

I've been using Yarn for a little while, and I've grown to prefer it as my "talking to NPCs" solution for game development. If you're not familiar, Yarn and Yarn Spinner are a pretty powerful Twine-like plugin for Unity (though it could technically work in any C# game engine) that's geared towards writing video game dialogue, and it was most famously used for Night In The Woods.

Yarn is fairly lightweight, extensible, and it basically gets out of your way. Want to make a really big long monologue, or 100 little pieces of dialogue snippets? Yarn works well for both of those use-cases. (If you want something that's more focused on manipulating very long dense passages of text, you might want something more like inkle/ink, the system that powers the huge 750,000 word narrative game 80 Days.)

To try to provide more resources for other Yarn users, or potential Yarn users, here's a write-up with some advice and a short guide to working with Yarn...

Friday, June 19, 2015

Videogames for Humans, edited by Merritt Kopas

The first reaction most people had was, "it's bigger than I expected." 575 pages to be exact. But that obfuscates the actual format of Videogames for Humans: 27 different close readings / commentaries on short stories.

What those most people actually meant was that they had no idea that 575 pages of thought on Twine was possible, that they're surprised Twine is this big or that it is worth preserving on a tree carcass.

Preserving! In order to preserve something, it has to be more or less "over", and Merritt Kopas has a lot of feelings and anxiety about how Twine will be remembered. In the introduction, she confesses, "late 2012 and early 2013 was an extraordinarily exciting period for me [...] the 'queer games scene' covered by videogame outlets might not have been as cohesive as some accounts supposed, but for a little under a year, it definitely felt real,"

... then later she argues, "but I don't want Videogames for Humans to be seen as the capstone of the 'Twine revolution,' a kind of historical record of some interesting work done in the early 2010s."

So then, this book is partly an attempt to correct or amend a prior history... but not with more history. It wants to break a cycle.

Thursday, February 28, 2013

Castle of the Red Prince, by CEJ Pacian

CEJ Pacian is probably the best short-form IF writer today. His (?) writing is usually firmly grounded in a genre -- Gun Mute in Mad Max / apocalyptic Western, Snowblind Aces in pulp adventure -- and Castle of the Red Prince is firmly rooted in magical fantasy.

The best part of his work, though, is that these genres and settings aren't really the point. In Gun Mute, Walker and Silhouette, as well as this newest entry, Pacian is clearly more interested in formal experimentation on a small but vital scale, and the genre is just a shortcut to approach narrative effect faster. What if navigation doesn't involve cardinal directions? What if everything is a metaphor? Above all, Pacian is interested in re-configuring how we perceive and navigate through space, in a way that only interactive fiction can afford.

Castle of the Red Prince's experiment, then, might follow these rationales:

Friday, January 25, 2013

More talk, more rock: on algorithmic game narratives, speculative narrative design futures, and "Shakespeare."

by Nexus

Last time, I wrote about procedural narrative in the context of "process intensity." Here, I expand more on designing the procedural / process part.

Back in an expertly-conducted 2011 Rock Paper Shotgun interview, Dan Pinchbeck argued that game development culture unnecessarily separates narrative from the rest of a video game:

"I just want story to be talked about as a gameplay element that sometimes isn’t there. It’s part of the set of tools that a game designer uses to create an experience – and it should be thought of along the same lines, as physics or AI or something more mechanical."

We have physics engines or texture libraries, so why don't we think of narrative as a modular "asset" or "engine" or "library" to be swapped around as well? Why can't narrative be more "mechanical." Where's all the narrative middleware? (Storybricks doesn't seem to be doing too well, unfortunately. I also don't agree with them, that proc narrative is mainly an AI problem...)

Friday, December 7, 2012

Recent happenings at New Statesman

Liz Ryerson recently linked here in her "recommended game criticism reading list" at the New Statesman, and John Brindle recently wrote a piece for them about text-based games commenting on war better than AAA counterparts with a few quotes from me on the topic. Check it out.

Tuesday, September 18, 2012

How to Make Games with Twine

Public service announcement: Anna Anthropy has written a great short tutorial on making games using Twine -- it's perfect for people with little or no game development experience at all, and will allow you to make cool text-based games with choices and stuff.

Friday, July 20, 2012

Return to Zobeide.


To tell the truth, I had kind of forgotten about Zobeide. My Twine / Unity interface experiment, instead of being my own version of Unmanned's interface, was strange and broken. People kept forgetting the text was there. But after conferring with some interactive fiction people at No Show -- where one had an interpretation of the game that made it sound much more fascinating than it really was -- I think I know what to do with this.



Expect another announcement in a few days (or weeks?)...

Wednesday, July 18, 2012

How to integrate Unity and Twine.

EDIT, 16 May 2013: Unity has changed their Browser to Web Player communications, but just a little. Basically, you don't use "getObjectById()" anymore, you just use "getUnity()" to get a reference to the web player -- more details here.

*****

Okay, I'm one of those people who thinks the problem with interactive fiction is that it's not sexy enough. However, I think IF, as a mode of interaction, is extremely powerful and is quite possibly light years ahead of whatever we're doing with narrative / meaning in the latest 3D whiz-bang video games.

Then one day I realized -- I could combine the CYOA tool Twine with the web player export of Unity, and the two could possibly hook into each other through Javascript. Turns out, they can.

Unfortunately, the project I used it for -- well, it didn't really work out -- but maybe someone else can use it?

The Unity Web Player has a useful method Application.ExternalCall() that can call Javascript methods on the web page. Similarly, you can call SendMessage() from a page script to call a method on a specific GameObject and even pass strings into Unity. That's the gist. If you need more help / my code snippets, a more detailed guide is here:

Friday, July 6, 2012

Rule Databases for Contextual Narrative... and spelling bees.


Valve's Elan Ruskin gave a fantastic talk at GDC 2012 on using "Rule Databases for Contextual Dialog and Game Logic" -- basically, the implementation behind the dialogue response system in Source games, most recently used in Left 4 Dead 2 and DOTA 2. I'm surprised more people haven't picked up on it because I think it presents some really effective research on procedural narrative systems.

A lot of game logic / narrative resembles a flowchart, especially with the advent of visual scripting systems like Unreal's Kismet or Twine -- resulting in this deeply entrenched concept of branching structure. Authoring and changing these individual branches is usually very expensive.

Sunday, February 19, 2012

Unmanned, by Molleindustria

I'm a bit late to the party, but Unmanned is probably one of the best games I've played in a while.

It's a fantastic use of interactive fiction / first person sensibilities (some of which I'm going to steal) with innovative use of split-frame and achievements, contemporary relevance but also rather personal narratives... it's got everything.

If you're upset that it's not subtle enough, consider all the noise it's trying to combat, all by itself. You don't bring a toothpick to a knife fight, folks. Also, in case you missed it the first time, check out this game's distant cousin, "maybe make some change."

Funny how similar the premises of these two games' methodologies are: that text and only text can adequately communicate the psychological damage of modern warfare, and militaristic first person games thrive on the lack of text and introspection.

Pop music doesn't care whether you think it's authentic, though.

Thursday, September 22, 2011

On process intensity and procedural narrative: either don't try, gameify, fill a plot, be bushy, tell a world or pass the buck?

For my master's thesis (no, not Pilsner, though I still like the idea and I'm going to re-work it more as a single player puzzle game) me and my design partners are trying to tackle a Holy Grail of video game design: procedural narrative. We're crazy stupid for trying.

How can a computer generate, whether in-part or in-whole, a meaningful narrative?

Back in 1987, Chris Crawford coined the term "process intensity", or "the degree to which a program emphasizes processes instead of data." Greg Costikyan used this idea to analyze what he argued was the low-hanging fruit, the data-heavy applications the game industry was and still is pursuing, such as more polygons, more shaders and more uncompressed rendered cinematics, etc. He proposed Spore as a new hallmark in procedural generation... then two years later, we all actually played Spore and wanted to forget a lot of it.

I still think the idea is important though, and I want to use it as a lens to analyze approaches to procedural narrative.

Monday, April 18, 2011

Ludodiegesis, or Pinchbeck's unified field theory of FPS games, or "please pee on my leg and tell me it's raining."

photo by National Media Museum, "You want a piece of me?!"
I'm reading (fellow frontiersman of modding) Dan "Dear Esther" Pinchbeck's PhD dissertation / unified field theory of FPS games. Contrary to what my inflammatory post title implies, I actually really like it and think it's valuable.

I've also kind of fact-checked my summary with him too, so let this post serve as a Wikipedia article of sorts for piquing your interest in reading the real thing...

“Story as a function of gameplay in First Person Shooters: an analysis of FPS diegetic content 1998-2007.” 

Central to his conceptual framework is the idea of "ludodiegesis" -- ludo meaning "play" and diegesis referring to "the fictive reality of the game." (If you're gagging at these words: remember that part about games being a legitimate form of art and culture? Well, we need to invent new words to effectively talk about this new media. So learn this word.)

It's his elegant way of growing something from the rotting corpse that is the narratology vs. ludology non-debate, mainly by shifting what "game narrative" means:

Wednesday, May 26, 2010

Byzantine Perspective: on IF, adapting it to the FPS

Text is special. It can do things that voice acting can't; it can do things visuals can't. (How? Well, Kenneth Young explains this really well in a post about dialogue in Dragon Age)

I recently played an piece of interactive fiction that can't possibly be made outside of IF -- "Byzantine Perspective." It has a single really great puzzle in it, which it won an XYZZY award for.

The premise -- you're a burglar trying to steal a valuable chalice in a museum. You begin in the vault room and type "take chalice" -- and your hand passes through it. Something's not quite right.

(SPOILER ALERT! Make sure you've either played it or don't intend to play it before continuing...)