7DFPS x PROCJAM, 20-28 October 2018 (make a first person game in 7 days) + (make a proc gen thing in 7 days)

For the first time since 2014, the #7dfps challenge is starting tomorrow. If you're not familiar, it's a week-long jam to make a first person game that tries to do something new.

Past alumni of 7DFPS include high-concept gun games like the original Superhot prototype as well as Receiver, but of course you don't have to do any shooting or violence for your first person game. Make a first person whatever-you-want.

If you need help getting started with making a first person game, even if you've never made an FPS or even a video game before, then here's a great free step-by-step tutorial with video examples on KO-OP Mode's "Make Weird Stuff in Unity" workshop page.

For a bit of historical perspective on this, also check out the 7DFPS video keynote from 2012, where a baby-faced JW and other game industry folks beg you to do something new with the first person format:



This year, 7DFPS also falls on the same week as PROCJAM, a community jam to make something that makes something (procedural generation)... they have their own list of talks, tutorials, and resources to help you make a proc gen thing.

Maybe this is a good time to make that procedurally generated first person game you've been dreaming about it? It seems the gods will it so.

The destruction / extinction of digital brutalism

screenshot from "Brutalism: Prelude on Stone" by Moshe Linke

The other day in level design class, a student brought up Moshe Linke's "Brutalism: Prelude on Stone" for discussion. What does it mean to re-create / re-construct / build a brutalist building in a video game?

To review, brutalism was a design ideology deployed mostly in public architecture from 1950-1970s throughout the world, exemplified by large blocky concrete structures in Soviet Russia and/or brick housing developments across Europe.

For the last 2-3 decades, people have criticized brutalism mostly as a cold, ugly, overly institutional style that ignores local communities and human warmth -- and recently that's been amplified by various material and technical critiques of brutalism (poor weathering and staining; environmental impact of concrete; seismic issues; etc) -- but now that we've started demolishing iconic brutalist buildings around the world, there's been a resurgence in defending brutalism before it becomes extinct.

Given that brutalism faces a real existential threat, and it is so heavily focused on the real-world material aspects of architecture, does a digital brutalism make sense?

"Pylons are my penis": a phenomenology of building in Offworld Trading Company and other strategy games

Game feel always has a narrative aspect tied to the player's in-game identity -- but in a top-down strategy game, who are you? Why do you know all this stuff, and why are you able to do the things that you can do?

I'm not asking for more bullshit handwave-y game lore ("it's the future, you're a space wizard") but rather I mean it in terms of interface and "raw experience". Even in strategy games with fog of war, there is still a fantasy of absolute certainty involved with your command. If you see a unit, it's almost definitely there; if you order a unit, they will definitely try to obey your order. If your unit dies, it is definitely dead.

These are all myths and abstractions away from how a real-life military often works, where commanders must constantly act on incomplete information, even about the state of their own forces. Few popular real-time strategy games let troops ignore an order, be routed, or be "missing in action", because maybe that's too unfair or it would weigh down the game a lot. (Some notable exceptions: hardcore military sim games often simulate supply lines and unit morale, the overburdened 2011 game Achron had time-travel and alternate universes of troop movements, while the admirable 2010 experiment R.U.S.E emphasized military intelligence and decoys.)

I'm going to propose that top-down strategy games let players build their own identities, and part of that identity is a body, in the form of your "base."

"Rinse and Repeat" technical post-partum / how to do over-complicated wet skin shower shader effects in Unity

This is a technical overview of how I built certain parts of Rinse and Repeat. It spoils the game, so you should probably play it first if you care about stuff like that.

Rinse and Repeat took about 1-2 months to make. For these sex games, my development process can basically be summarized as "art first" -- my very first in-engine prototypes are usually about establishing mood and texture, and setting up the character you'll be staring at, and these are by far the most important parts of the game.

We are drugs; speculative dev tools and psychedelic hologram futures.

This post is adapted from a talk I gave at Indiecade East 2015, where the theater was way too small for the crowd, so not many people got to see the talk... sorry / oh well. Here's basically what I said:

Our story begins on October 8th, 2014, on a very special episode of the Late Show with David Letterman. He was ending that episode with a musical guest from Japan -- a holographic vocaloid named Hatsune Miku. Pay attention to Letterman's barely-veiled incredulity as he introduces her. He can't believe the words coming out of his mouth:



But what really makes this moment is the ending, after the performance. Letterman doesn't even know what to say, and he knows he doesn't know what to say. The experience was completely overwhelming, so Letterman has to somehow pivot back to interpret it for his audience (mostly moms and dads from Milwaukee) and all he can muster is a facile comparison to "being on Willie Nelson's bus." (Willie Nelson, if you're not familiar, is a celebrity notorious for his drug use, among other things.)

The meaning is both clear and agreeable: Hatsune Miku is drugs.

Second time's the charm; procedural NPC dialogue in Nostrum

Last time I tried some type of "procedural narrative" thing, my hubris got the better of me -- naming the system after one of the most famous and influential writers of all-time was, perhaps, just a little arrogant.

Despite my attempt to scope it properly, that system suffered greatly from trying to do too much stuff... It was so much stuff that it was difficult for me to write anything with it. So with the procedurally generated NPCs in Nostrum, I'm developing a much simpler system which will hopefully work better, to solve a smaller problem...

The basis is still the same: Elan Ruskin's GDC 2012 presentation on AI-driven dynamic dialogue in Left 4 Dead 2.

Design reboot: Thief.

This post relies on familiarity with the gameplay / affordances in Thief. You may want to read Dark Past or my write-up on "Assassins." You're also encouraged to read through Mr. Monahan's Design Reboot blog.

I've been watching Thief 4 coverage over the past months and I'm increasingly convinced that I'm going to hate it. So let's pretend, just for fun, that I'm making a Thief-like... What are the best qualities of Thief to preserve, and which parts of the sacred cow would I lop-off? Here's what I'm thinking:

KEEP: Level size. Thief levels vary from medium to extremely large. "Life of the Party" was a single mission where you had to traverse an entire cityscape of rooftops through two dozen buildings and then also infiltrate a huge skyscraper at the end. Sheer architectural scale is important to maintain a sense of...

KEEP: Infiltration and exfiltration. You have to get in, rob the place, and get out. There's always an outside and an inside, and it's great to feel that you're not supposed to be inside. But previous Thief games usually neglected exfiltration as redundant backtracking or worse -- something totally nonexistent because you've already incapacitated the entire guard garrison by the end of a mission. (My favorite Thief 1 mission, Assassins, is one of the few missions to really do something with exfiltration.)

ADD: Organic use of dynamic lighting. With dynamic lighting and shadows, you can do totally unimaginative setpieces where you have to hide in a guard's shadow or hide in the shadow of moving objects on a conveyor belt. But something else is going on here: with dynamic lighting, open doors and windows become light sources -- and if you can close the door or block the window, you've "extinguished" that light -- but if there's a ramp in front of that window, you can't put anything there to block it because it'll just slide down, etc. That possibility sounds much less horrible than a contrived puzzle that you designed to death.

Design futures: AutoBrushes, levels that build themselves, and the politics of procedurality.

If Bethesda's detailed GDC presentation about modular level design kits for Fallout / Skyrim showed me anything, it's that modularity is actually a huge pain in the ass -- and not the good kind of ass pain either. Why should we keep building 3D levels in this slow, totally unnecessary way, with a workflow that's at least a decade old?

I remember a time when level design was slightly faster, and that time was the time of the brush. What if we could combine the benefits of modularity (variety / adaptability / abstract detail out of design) with the benefits of a brush-based workflow (simplicity / speed / focus on "platonic forms" of design)?

Game narrative as improvisational theater / negotiation.

The current narrative systems prototype Shakespeare has been somewhat disappointing so far: the director switches, seemingly erratically, between 5-6 different plot threads, and nothing seems coherent. I need a way of (a) allowing the player to influence story pacing / scope, and (b) a way for the system to push back, to try to force some story pacing / scope.

For this, I'm looking at how improvisational comedy generates and upholds structure. You might've heard that improv is about "always saying yes," but there's a lot more to it, apparently.

Specifically, longform improv comedy involves actors cooperating to "find the game" -- to find the core of a joke. Each actor makes "offers" to expand upon a premise and move action forward, hopefully toward a funny destination, and usually, actors err on always accepting offers ("saying yes") and building upon it since "blocking" offers frustrates your scene partners. However, it's very possible to "say yes" to a premise while still "blocking" the "game."

Here's an explanation from an NYC improv comedy personality, Will Hines:

A smoother triplanar shader for Unity.

To review: procedural UVs are amazing and you should consider using them in your games. Now, the old triplanar shader I posted was great at hard-edged cubes, but it didn't handle the transitions between textures very gracefully; curved surface like cylinders and spheres were forbidden.

So I took a look at how James "@farfarer" O'Hare handled the blending in his triplanar terrain shader, and how Tom "@quickfingerz" Jackson grabbed normals in his own triplanar shader (but the blending in his shader would "blow-out" a lot, I found) and I combined their respective strengths. I also added different handling for top vs. bottom textures, since grass rarely grows on ceilings. (Textures in the shot above are from Farfarer's pack.) One last change: I let Unity's built-in surface struct calculate world normals instead of calculating my own.

So far, I've been unable to get normal maps working with it, so if any enterprising blog readers would like to instruct me how to do it, and share that technique, then I'd be much obliged.

Here's my shader so far. Do what you will with it:

Narrative systems workflow; using Fourier analysis and level design metaphors to systemize stories.

This assumes familiarity with Shakespeare, a procedurally-branching narrative system that I'm designing. For an overview / introduction, read "More talk, more rock."

I started by arguing that interactive fiction's narrative systems expose too much complexity and detail to its authors and players, or at least more than most people need or want. With Shakespeare, I hope to achieve just a fraction of that functionality, and I think that fraction is enough to be very compelling while facilitating a writer's work.

In engineering Shakespeare, I think of the system in four parts:
a) The real-time system that runs algorithms, interfaces with the game as the player plays.
b) The data / format of narrative itself, how it's structured.
c) The Unity editor interface for generating, editing, or creating the narrative data.
d) The suggested workflow / instructions for using that interface.

Now that I have enough of a base implemented, I'm starting to think more about that last part, the operations design. Roughly, I think the tool could work like this:

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

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...)

Radiator Blog: Three Year Anniversary

Wow, I've been blogging here for about 3 years now. This blog is now approaching the end of its toddler years. Much like last year, and the year before, here's a "greatest hits" compilation of this past year's posts:

(Oh, and feel free to have some cake. Forks and plates are over there, on the table.)

GAME ARCHITECTURE CRITICISM

• Why game architecture matters and the reality / unreality of de_dust. If digital life is real-life, then digital places are real places. QED.
• The shape of crime and escape. Notes from a BLDGBLOG panel / talk on heists and bank design, and me trying to apply it to game architecture. Sort of a sequel to last year's "On the first person military manshooter and the shape of modern warfare" which takes off from another BLDGBLOG talk on military infrastructure as war.
• Infinite Omaha. I went to the real-world Omaha Beach, then compared it to various video game portrayals of Omaha. 
• The shadow of the white cloud: architecture criticism at the 1893 World’s Fair and BioShock Infinite. These days, I'm more reluctant to credit the upcoming BioShock Infinite with intellectual subtlety -- it's a game where you shoot men while riding ziplines -- but still, "City Beautiful" is one of the most influential and distinctly traceable trends in architecture ever. It's also a forerunner to thought on Disneyland, theme parks, and "artificial" architecture.
• A short history of non-monoplanar first person movement. The biggest con of non-monoplanar movement is that it's hard to make giant impressive sweeping landscape levels: you're usually either stuck inside a padded room, or you're running outside on an asteroid, and neither offers a grand vista because you're either inside or outside but rarely just off to the side. The horizon is always shifting.
• What makes good writing on level design? I think writing is best when it's specific, and here I try to articulate what I like about certain writers' styles.
• On Joiner and the cult of greeble. If Sleep No More spams readables to show how much money went into it, then TF2 maps spam meticulous func_detail brushwork to imply the mastery and skill of the level designer. What happens when you automate the writing of readables, or automate the placement of detail? I think indie developers are more conscious of the cult of detail than AAA devs, mostly because detail is expensive to add.

COMMISSIONS

• Level With Me, a post-mortem. A Portal 2 mod I did for Rock Paper Shotgun. The level design is some of my better work, and I like the idea of game journalism in the form of games, but it seemed somewhat cooly received. I have to conclude that it must simply be not as good as I think it is... or that Portal 2 players are super lame.
• The Future of the FPS, written for PC Gamer UK in issue 240. A short essay and list of really cool indie FPS games and how they're changing the genre, kind of the basis for my later RPS series. Thanks Graham!
• A People's History of the FPS. A three-part essay series for Rock Paper Shotgun that argues mods are transcending their video game bodies, becoming genuine culture that is increasingly independent of the products that they're meant to be "modding" and adding value to.

ON GAME NARRATIVE

• The myth of psychological realism in narrative. Argues that thinking of fictional characters as "people" is meaningless for a writer. It is much more useful to write by thinking of a character as a vehicle for plot, and let the player fill-in character for themselves.
• Dishonored fails as an immersive sim in its first minute. The simulation should be "immersive" -- meaning, the scope of it should be consistent and everywhere. Scripting special cases goes against this genre dogma.
• Dishonored uses the Heart to lie to you. You'd expect the Heart to be an unreliable narrator of some sort, but it doesn't lie to you with narrative -- it lies to you through gameplay and psychological framing.
• "Stair K": architecture criticism, Thief, and a coffee maker. Situates Thief as dialog on social class and urban architecture. (e.g. stairs are invisible to rich people who take taxis, not subways, and frequent buildings with abundances of elevators) It argues that in Thief, stealing is framed as an ethical act because the rich deny the truth and infrastructure of cities.
• Thief 1's "Assassins" and its environmental storytelling. I really hate the type of analysis that just thinks of game narrative as a static text that you read -- game narrative is also a game design tool, a way to make the game better to play. Games tell stories, yes, but those stories tell games too.
• What do simulations simulate? Argues that a simulation gap is important for framing a narrative.
• The structure of Sleep No More (part 1, no spoilers) and (part 2, detailed and spoilery). You paid a lot to see this damn show everyone's raving about and now you're inside, on a timer. Are you going to spend your valuable time (a) reading faint scribbles on random pieces of paper under a dim flickering light-bulb or (b) follow the crazy naked people who have an interpretive dance orgy in a blood-smeared disco?
  
  I still think a lot of "game critics on Sleep No More" like the idea of it more than how people actually consume it -- unfortunately, reading is boring and performance is captivating. So I argue the readables function as set dressing to assure you of the production's expense, not to serve as barely coherent narrative in a familiar plot that's hundreds of years old. Of course, the dancing's fantastic, but I guess it's hard to argue for the value of dance to gamer culture.
• Rule Databases for Contextual Narrative. On modding Valve's dynamic self-branching conversation system and using it to author dynamic self-branching narrative, and how Emily Short's already doing something like that, naturally. I think it's one of the more promising directions toward a holy grail of procedural narrative.
• Balls and conversation: let's narrativize the sports genre. I really love baseball movies, but I'm really bored by the focus on statistics, which is probably why Moneyball sucked. There's a rich tradition of sports narratives in film and literature, but in video games it's conspicuously absent. Let's change that.
• "Do you think shooters take themselves too seriously?" We watch blockbusters in a special way, I think, but the gulf between action films and action games is this: the films are structured to be human and sympathetic, but games are sociopathic and mean. This is a game narrative writing problem.

ON GAME CULTURE

• Frog Fractions should really win something at the IGF.
• On appreciating the UV texture flat as fine art. Here, I propose three aesthetic modes for enjoying texture flats on their own merits and glorifying them as authentic game art, rather than the silly concept art we parade as game art. I later re-wrote this piece for Game Developer magazine, as "Loving the Bones."
• Desperate Gods and rules-forcing in games. Pretty recent, but I think it's a good summary of current thought on the issue -- if you can play a game of Starcraft in your head, and Starcraft exists fundamentally more as a mental construct than a product, then why can't we just argue the rules of Starcraft in the same way we interpret and amend the laws of board games.
• On grad school for games / what studying at Parsons was like. Imagine a cohort of game developers from all around the world, and 50% are women, and 10% aren't straight people. Parsons is like the rainforest: diverse, beautiful, and vital to the global ecosystem -- but it's also humid, with lots of insects everywhere, and it's constantly in danger of deforestation. It's not for some people, while others will really grow to love it.

GAME CONFERENCE / FESTIVAL NOTES

• Why Indiecade is the best games conference / festival I've ever been to. It might sound like hyperbole but it really isn't.
• I spoke at Games for Change this past year, on LGBTQ attitudes and developers in games. It went great. I began with "I'm Robert Yang, and I'm a practicing homosexual" -- and the entire auditorium erupted in applause and cheering. It was an amazing feeling.
• Notes on the Games for Change industry. Fun fact: I got into an argument with a G4C speaker in the comments. His stance -- yeah the games suck, but people want to put a lot of money into this, so just accept it. My stance -- art should be a free or reasonably available public good, not a product.
• How the worst part of the game industry uses PAX East to teabag your entire face with its cancerous scrotum. I encourage everyone to go to at least one big mass market game convention, because that's when you will know what "indie" really means and you'll realize how small, puny, and insignificant we "video game intelligentsia" really are. The sheer amount of money being thrown around in this industry is insane -- the money spent on a 20-foot tall Blops booth-complex, blaring out noise at a regular interval, is a huge contrast to the humility and humanity of indie game culture.
• What were the main trends of GDC 2012? A look-back on what happened and what stuck out as significant.

UNITY TUTORIALS / RESOURCES

• Shader-based worldspace UVs ("triplanar") in Unity. The worst thing about BioShock's environments is the cookie-cutter feel of the game architecture, the result of modular building in game engines today. The scale and proportions don't feel human or plausible. To me, one answer is to embrace old school BSP construction techniques with procedural UVs so that you can scale your primitives to arbitrary sizes without texture stretching.
• How to integrate Unity and Twine. Notes on Unity's web player JS hooks, and how that can feed into Twine's JS, or any webpage's JS, really.
• How to dig holes in Unity terrains. How to use depth mask meshes to selectively mask geometry, then disable the terrain collider temporarily.
• The best Unity tutorial writer in the world. He really is. I'd pay him to write a book, in fact, but unfortunately I'm poor.

On why Convo is now a WW2 spy romance, and the myth of psychological realism in fiction.

Short version: I've chickened out, a bit. Long version?

To make some sort of procedural "anything", you have to have an idea of what the building blocks of that "anything" are, or at least what you'll argue they are -- and then either frame your game in those terms or expressly simulate those terms. So if Convo is a game about narrative instead of people, then what's a unit of narrative?

From there, my thinking goes like this...

A bit about Convo.

Convo is a tactical squad romance about applied linguistics and binge drinking.

I remember when I was of legal age (okay, well, of kinda somewhat legal age) and I started going to bars. Who teaches you how to behave at a bar? How do you know how much to tip a bartender if at all ("$1 a drink, usually, in the US") or what tabs are ("you pay when you leave") -- is it weird if you're there by yourself? (Sometimes.) When do you buy a round for everyone? (Sometimes.) When is it okay to check your phone? (It depends.) There are all these rules of socialization that we internalize without thinking, practicing them until they become reflex. Different bars in different places have different rules, and we wordlessly sensitize ourselves to each arena.

But even before we enter bar culture, we get socialized at a much more basic level -- in the art of conversation. How do you know when it's your turn to talk? When can you make a joke? When can I leave a conversation?

My prototyping process has involved a lot of linguistics research along these lines, mainly focusing on an old (now somewhat irrelevant?) branch of applied linguistics called "conversation analysis." It might be really hard to teach an AI just how to time its responses and get into the rhythm of things, but there are 5 year olds who effortlessly achieve gapless conversation on a daily basis. I find that fascinating -- and where there's elegance and an element of timing, there's strategy and a game.

To be clear, my goal isn't to solve "procedural conversation generation" in any way, but rather to sidestep it. Convo is NOT about "what" you say or "how" you say it -- it's mostly about "when" you say it.

I'll post more about Convo as I develop it.

"In Ruins" by Tom Betts

"In Ruins" is a first person procedural platformer-explorer thing. Spoilery critique after the jump:

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:

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.

Levels to Look Out For, June 2012: "Future of the FPS"

I don't normally theme these posts around anything, but these three indie FPS experiments share so much DNA that it's impossible to ignore. They're all very grounded in digital / virtual / "futuristic" aesthetics, but they're confident to sometimes let that futurism be incredibly alien. Also, I'd hazard a guess that few of these designers have worked on many FPS games in the AAA manshoot tradition, but these "outsiders" are the future of the FPS.

(Coincidental but shameless plug: if you pick up a recent issue of PC Gamer UK, there's a "Future of the FPS" feature I wrote, though I guess it's already inaccurate now, seeing as I've neglected two of these beauties...)

Dirac by "Orihaus"

Descriptions offered so far seem intentionally cryptic and foggy -- a multiplayer co-op wandering survival sim (?!) with an emphasis on atmosphere over gameplay, set in a stark Mordor-Tron world, with a little help from Structure Synth. What grabs me most is how the forms are so mechanical yet still incredibly abstract and inscrutable. You always see generic sci-fi corridors with gubbins and doodads embedded in the walls, and they're always encoded as "electrical panel" or "fuel pipes" or something. They're obsessed with being knowable because supposedly that's good design; I think Dirac shows how nice just a shape can be. (Unfortunately I missed the last multiplayer playtest, but there's another open test coming up on May 20th at 8 PM EST, just meet in #merveilles IRC on esper.net. Check the TIGSource thread for the most recent schedule.)

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.