Richard "Safety" Dansky, Part TwoComplications Ensue
Complications Ensue:
The Crafty Game, TV, and Screenwriting Blog




Archives

April 2004

May 2004

June 2004

July 2004

August 2004

September 2004

October 2004

November 2004

December 2004

January 2005

February 2005

March 2005

April 2005

May 2005

June 2005

July 2005

August 2005

September 2005

October 2005

November 2005

December 2005

January 2006

February 2006

March 2006

April 2006

May 2006

June 2006

July 2006

August 2006

September 2006

October 2006

November 2006

December 2006

January 2007

February 2007

March 2007

April 2007

May 2007

June 2007

July 2007

August 2007

September 2007

October 2007

November 2007

December 2007

January 2008

February 2008

March 2008

April 2008

May 2008

June 2008

July 2008

August 2008

September 2008

October 2008

November 2008

December 2008

January 2009

February 2009

March 2009

April 2009

May 2009

June 2009

July 2009

August 2009

September 2009

October 2009

November 2009

December 2009

January 2010

February 2010

March 2010

April 2010

May 2010

June 2010

July 2010

August 2010

September 2010

October 2010

November 2010

December 2010

January 2011

February 2011

March 2011

April 2011

May 2011

June 2011

July 2011

August 2011

September 2011

October 2011

November 2011

December 2011

January 2012

February 2012

March 2012

April 2012

May 2012

June 2012

July 2012

August 2012

September 2012

October 2012

November 2012

December 2012

January 2013

February 2013

March 2013

April 2013

May 2013

June 2013

July 2013

August 2013

September 2013

October 2013

November 2013

December 2013

January 2014

February 2014

March 2014

April 2014

May 2014

June 2014

July 2014

August 2014

September 2014

October 2014

November 2014

December 2014

January 2015

February 2015

March 2015

April 2015

May 2015

June 2015

August 2015

September 2015

October 2015

November 2015

December 2015

January 2016

February 2016

March 2016

April 2016

May 2016

June 2016

July 2016

August 2016

September 2016

October 2016

November 2016

December 2016

January 2017

February 2017

March 2017

May 2017

June 2017

July 2017

August 2017

September 2017

October 2017

November 2017

December 2017

January 2018

March 2018

April 2018

June 2018

July 2018

October 2018

November 2018

December 2018

January 2019

February 2019

November 2019

February 2020

March 2020

April 2020

May 2020

August 2020

September 2020

October 2020

December 2020

January 2021

February 2021

March 2021

May 2021

June 2021

November 2021

 

Sunday, September 27, 2020

Vaporware, by Richard Dansky (Book Cover)

Richard Dansky is a veteran game writer and horror novelist. Among his many novels, Vaporware is the horrifying tale of a game project that refuses to allow herself to be killed off. There is a monster in it, but not the one you think.

Alex: How would you define a narrative designer versus a writer?

Richard: I would say that the two jobs can overlap, but the narrative designer is responsible for the systems for delivering narrative to the player while the writers are responsible for the content that gets delivered.

Alex: And why do you think it's valuable to separate those job descriptions?

Richard: Because it's…. how can I put this delicately?--

Alex: --Some people can't write, and some writers can't program, is that it?

Richard: Some writers can't program, some writers can't design. As games get more sophisticated, you need more and more sophisticated ways of telling stories, you need more intricate artificial intelligence structures to call on for systemic dialog, you need better environmental storytelling. You need somebody to keep track of all of that, and somebody whose primary skill is writing may not have those skills. At the same time, someone whose primary skill is writing should be able to go ahead and write. Maximize the resources, make sure that you're getting people in a position to succeed. But it's not just writing, it has to be a way of delivering the story as well as the story itself.

Alex: So talking about narrative delivery systems: what's a narrative delivery system that you really thought worked? Something that you thought, This is cool, this is doing a new thing. This is something movies don't do.

Richard: I thought that the narrative delivery in Assassin's Creed: Odyssey was fantastic. Really brought you into that world.

Alex: How so?

Richard: For the first time in that series, you really got a sense of who the people in that world were. And it was deeper immersion. The sense that their lives have been going on before you got there and will continue to go on after you left.

Alex: I was talking with Anna Megill and she was saying that's apparently called "negative capability." Was that a term you've heard?

Richard: It's not a term I've heard, but I'm happy to steal it.

Alex: What was happening in the game that was new that was making you feel like these people had lives?

Richard: Part of it was the content, what they were talking about, what they were asking the player to do. The language that was used felt realistic and personable. And part of it was the structure of the conversations. There wasn't a character standing around waiting for you to interact with them, in a way that was obvious that they were just tools in the delivery of narrative. They felt like characters. They did not feel like signposts on the way to the story.

Alex: So were these were these branching conversations? Was there AI going on, do you think?

Richard: Yes. And I fully imagine that QA spent many hours screaming into the night testing that because branching dialog is hell. But they did a wonderful job of it.

Alex: What is an interesting narrative delivery system that you weren't able to implement, that you wanted to?

Richard: Well, the early days of the Clancy franchise we basically had no narrative implementation except for a giant wall of text at the beginning of the missions. And with pressure from production and management to fill in every last detail of the mission, those walls got pretty tall indeed.

Alex: I feel like games had way more dialog in the 90s, and then there was a big step back. Because in the 90s it was all just text, so you could write as much as you like. Like Planescape: Torment, there has to be several novels worth of dialogue in there. And then once we started voicing lines and animating characters, then it's like, oh, my God, we can't do that anymore. And we're only now getting back to where we were in the 90s when it was just texts. Does that feel right?

Richard: I think so. But I would say you look even at a game as venerable as Knights of the Old Republic, that had a metric fuckton of dialog. The revolution happened a while ago, to get us back to more and more dialog. Planescape: Torment, I used to know the word count on that. But if you looked at Old Republic, that must be 26 times as large. Just the blossoming of how much is in there. Part of it is the game types that are available now. Part of it is the idea of games as a service so you can keep extending the life of the game and keep on telling more story with that one game. And part of it, like you said, is the advanced technology and the ability to record more easily and more cheaply.

Alex: The mocap, the cost has come down. We're putting more of those dots on people. They can capture more expressions. People don't have to go to a mocap studio anymore, they can have a mocap room in their studio.

Richard: Yeah, ours is in the break room at Red Storm. So when the animation team is at work, everybody clears out, nobody's getting any snacks.

Alex: Oh noes!

Richard: They all deny that. They will say, “You can walk around the edges.” But you don't want to go in there.

Alex: What can you do in non-linear narrative that you can't do in linear narrative?

Richard: We can do a lot of things with messing with the players expectation. One of the nonlinear narratives that I wrote was Splinter Cell: Conviction. That starts with Grimsdottir shooting him. And then the entire game is a flashback leading up to that moment. It tells you how you got there and why that's actually a perfectly rational thing for her to do. Except there's also a flashback within the flashback.

Alex: OK, but to me that's telling a linear story, just not chronologically. I'm talking about, in games, you can have the player discover narrative bits in different orders.

Richard: Sure, that's something that's more prevalent with open world now. Yeah, games like The Division. You still have a lot of short, overlapping stretches of linear narrative. It's a question of what order of the player encounters them. And whether they're gated by difficulty for the player to only run across some of the easy stuff early on.

Alex: Do you think that that is more fun for the player? Does that create verisimilitude? Is that more powerful emotionally? Does it immerse the player more?

Richard: It certainly gives the player more feeling of authorship of their experience. If you talk to somebody who's played a video game, they're going to say, "I did this." Not, "The main character did this." And by letting them choose, you're increasing the amount of authorship that they can have. They'll even say, "I did this" on something that's a roller coaster ride straight rail shooter. Because they will have a better feeling of ownership of their actions, I think, when they have an open world to play with and they can go in any direction.

Labels: , ,

0 Comments:

Post a Comment

Back to Complications Ensue main blog page.



This page is powered by Blogger.