Categories

Welcome to Dev Game Club, where we are beginning a new series on 1992's immersive sim classic Ultima Underworld. As usual, we situate the game in time a bit and in the Ultima series as a whole, before delving into the first few hours of the game. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Sections played: Level 1

Podcast breakdown: 0:40 Underworld 54:54 Break 55:22 Feedback

Issues covered: Brett gets hooked, first person game and a lot of clicking, getting over the initial hump, taking a long time to finish a game, 72-hour game benders, epilepsy and flashing, firsts of their kind year, seeing the walls of the design, branching out with the Ultima series, Ultima Worlds of Adventure, adding simulation to the point of view, not being alone in the first-person space, vector wireframe rendering in the first Ultima dungeons, feeling the presence of the developer, exploration of controls, limited verbs in FPSes, free look, overdesigned mouse interface, not reading the manual, coming full circle to analog controls in the modern day, fine-tuning movement, "this will never catch on," clarity in input, instinct was right but implementation was wrong, poll rates, mechanical mice vs optical mice, Trish the Bard, 80s looking character portrait, innovating on taking a thing from world and dragging into the inventory, the Trello of inventory systems, adding too many things to a bag, UX nightmare, convergence game with systems coming together, top-down design vs bottom-up design, RPG differences between player skill and character skill, gesture-based combat, idea to implementation, fewer barriers to implementation, lack of level designers, taking more risks because of lower costs, dark side of games, using a key in a door, verbs and similarity to adventure games, where the three hours went for Brett, fearing dropping something that you'll need later, traipsing all over, jumping difficulty, factions as an underpinning of the underground society, lack of quest log/journal, does dialogue hint at actions you can take, clarity of the rules, fading fortunes of SSI, playing MGS vs remembering MGS, coloring what follows a good moment, CGI cutscenes painting in the player's impressions of fidelity, the legacy of Lara Croft's portrayal, avoiding blind spots through diverse representation in your development team, preferring Twin Snakes.

Welcome to Dev Game Club, where we are are just finishing our series on 1998's Japanese stealth classic Metal Gear Solid. We talk about the end of the game and some narrative choices there that we like and then discuss our pillars for the game. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: 100 episodes, Tim moving out, extravagant endings in the series, intercutting action scenes, turning codecs into cutscenes later, economic storytelling through codecs and audio diaries, conversational audio diaries, utilizing VO in interesting ways, Brett's new keyboard, the interesting dynamics of the Vulcan Raven battle, cat and mouse, Brett forgets the word "claymore," multiple ways of defeating Raven, using the AI's rules against them, boss/level design/camera synergy, Brett skips a cutscene and has to redo the battle, backtracking and stretching time, cool alloys, keeping a balance between being cool and usability, camera shot of Revolver noticing that Solid is outside the room (sort of a double reversal on the player), hanging out in the cold or hot rooms, Master Miller and throwing Naomi under the bus and yet still being Liquid, Tim recants his feeling that there should be a MGSVI, small universe problem, Chewbacca effect, Naomi and Gray Fox, the Ocelot effect, Ocelot and Liquid reunited, Liquid monologuing outside of Rex, going toe-to-toe with Rex, RoboCop vs ED 209, forcing you to be bold, Liquid as the boss who never dies, Gray Fox confessing his sins, hand-to-hand fighting with Liquid on top of Rex and the uncertain fate of Meryl, the reveal about FoxDie, cloning and the relationship between multiple characters, Dolly the cloned sheep, being the soldier of the century, James Bond themes, Snake Eater, The Man Who Saved The World, two more monkeys jumping on the bed, differences in the endings, jeep battle, low turn rate, tracers, having a third big battle, end-game balance for normal difficulty, Jim Harrison (the politician behind it all), Meryl and Snake riding off into the sunset on their snowmobile, wrapping up themes of love blooming on the battlefield, different endings, juxtaposing the scientific/techy stuff with the philosophical talk, Hal and Dave (joking at the end), post-credits sequence and the Iditarod, writing yourself into corners and cliffhangers, retconning to fit story stuff together, comic book writing and story structure for serialization, commitment to narrative and cinematic presentation, in-engine cutscenes, hardware-acceleration on the PS1, bilinear filtering, best B movies, letting your freak flag fly, all of ones loves and fears being in a game, being generous as an artist, committing to stealth gameplay, high lethality, voice acting, fictional context, experimentation with mechanics, bringing you back through the evolution of mechanics, adding mechanics from a competing or more recent game into a remake, upsetting the balance, new game plus mechanics, new game plus plus and a tuxedo, immersive sims.

Welcome to Dev Game Club, where we are in our third episode of our series on 1998's Japanese stealth classic Metal Gear Solid. We talk about a big choice in the game and the things you're not taught, particularly considering how fourth wall breaking it can be, as well as topics like UI choices. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Sections played: To Vulcan Raven (II)

Podcast breakdown: 0:41 Metal Gear Solid 58:54 Break 59:26 Feedback

Issues covered: Brett's carpal tunnel, Decoy Octopus and the DARPA Chief, animals chosen for code names, keeping Octopus in the game, submitting to the torture, big story splits and Dragon Breaks, tone variety in Eastern action cinema, weird untaught mechanics, negative vs positive reinforcement in teaching, blood tuition (learning through death) vs soft failure, gameplay telegraphing vs realistic environments, the staircase section, contextualizing rather than breaking systemic knowledge, rappelling down from the roof, having to do things too many times in boss battles, player skill vs stretching time, using vector art in various weapon UIs etc, grounding and science fiction, Otakon and the guys in the elevator with you, CQC'ing the guys around the elevator, multiple ways of dealing with Sniper Wolf, love blooming on the battlefield, respecting the soldiers, professionalism, catching a cold, Naomi's grandfather and adding layers of random research, using the codec for storytelling, a sequel for the West, Metal Yorke Solid, stealing time on the PC, lessons from Metal Gear Solid to teens, when some of the audience wants one thing and a larger audience wants something else, evolving with the industry and your player base, bands selling out vs finding a wider audience, having games find their own voice in a changing environment, changing characters with actors, Kojima's prequels, expanding the histories of characters.

Welcome to Dev Game Club, where we are midway through our series on 1998's Japanese stealth classic Metal Gear Solid. We talk about frustration, the various bosses, and a bit about one-offs. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Sections played: Up through the torture scene

Podcast breakdown: 0:40 MGS 1:03:10 Break 1:03:45 Feedback

Issues covered: the history of "snake style," sources of frustration, Brett's psychological makeup, frustration in boss battles, the point of no return, finding the mine detector, using the cardboard box, getting through the lasers, using first person, smoking to reveal beams, gadget use in espionage movies, suddenly encountering a tank, stealth mechanics and the tank, tropes and cultural appropriation, 80s movies, elevating a bad B movie into a good B movie, committing to your melodrama, geopolitical themes and the military-industrial complex, subtext about game development, difficulty and frustration with Cyber Ninja, wall boss, human-sized bosses, grounding the game even in its strangeness, bosses can be characters, breaking the fourth wall with Psycho Mantis, reading the memory card, psychological warfare, cutscene leading up to his face reveal, ridiculous backtracking for the sniper rifle, beating Sniper Wolf and getting captured anyway, limited control in the cinematic, Revolver taunting you, focusing on scenes, voice acting video (link in the notes), briefing cutscene, taking joy in our lives despite their problematic elements, assuaging our guilt, carpal tunnel issues, posture issues.

Welcome to Dev Game Club, where we are beginning our new series on 1998's Japanese stealth classic Metal Gear Solid. We first situate the game in its time, including some personal reminiscences of how we first came to the title, before turning to the stealth gameplay, the cutscenes, and other topics. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: crawling around in ducts, constantly reaching for your phone, previous games in the series, Brett's first year in the industry, good years in games, influences in American film and TV, melodrama and pulp, wholesale commitment to stealth, demo disc for the gaming, preferring systemic games, pre-rendered cutscenes vs in-engine, Carpenter influences (percussion, minimalistic, and synthy), constant camera movement in the cutscenes, choosing CGI vs in-engine (pros and cons), design considerations for streaming video, pixel density/differences in cutscene vs gameplay, being able to tweak a cutscene until right before you ship, setting mood and art direction, camera choice and having a sense of your surroundings, fitting the map to the camera, comparisons with Thief, tactical espionage and choosing the camera to fit, committing to stealth as a primary mechanic, creative risk in the commitment, high lethality and bouncing off, softening failure, unfortunate sexism, Asian influence as far as character choices, introducing the Cold War/extended peace issues, melodrama and big story choices, divisiveness of exposition, tapping walls as a mechanic, good level design choices, out-sized boss characters, solid introductions, allowing the industry to ask whether we can put ourselves forward in this way, breaking the fourth wall puzzle for the CD case, level design writing checks that your camera can't cash, nostalgia as a factor in appreciating a game, hunting through history for Brett's crazy memory, the cut worlds from Anachronox.

Welcome to Dev Game Club, where we present our interview with Tom Hall, Project Lead of 2001's quirky Western-built Japanese-style RPG Anachronox. We talk about the team, the labor of love, what got left on the cutting floor, and various other bits and bobs. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: the game's science fiction underpinnings, JRPGs and adventure games, the surprise of having the adventure game elements, the lore bible and map of the Universe, generating the background information to make characters sound consistent, creating alphabets, the black and white pirate world, PAL-18's digital home world and cel-shading, knowing what happens next, writing and cinematic direction with tools (PLANET), programming the mini-games (APE), in-depth cinematics and facial animation and mitten hands, getting a story in the bathroom (and starting with the name), talking process with Terry Gilliam, little ideas coming together to unite a concept, having a poisoned past, Nick Danger and radio plays, coming up with the most surprising things you could think of, Democratus having its origins in John Carmack's D&D campaign, a planet walks into a bar, playing with expectations, feeling episodic, making characters come first to drive those episodes, loyalty missions in Mass Effect, hidden content, having different levels for different choices, renaming characters, origin of Paco's and Rho Bowman's names, Stiletto Anyway's origins, crunching too much and team size, team cohesion, structure of ION Storm, Dream Design, doing one take of Walton Simmons, thirty years into the industry, being just a bit ahead of time for mobile, directing Gordon Ramsay, missing the big references to Hitchhiker's Guide, talking about the black and white world, talking crunch, potential achievements for Anachronox, adding achievements to remastered adventure games.

Welcome to Dev Game Club, where we are having our fourth and final discussion about 2001's quirky Western-built Japanese-style RPG Anachronox. We talk quite a bit about the specifics of the end of the game, with a diversion into ION Storm, and then talk about our takeaways. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Sections played: Through to the end!

Podcast breakdown: 0:42 Anachronox!

Issues covered: that final battle, splitting up the party, Rho Bowman's adventure on Democratus, Stiletto Anyway's adventure on Democratus, Tim mansplains Star Wars to Brett, we do no work in figuring out the Elementor, Paco's adventure makes a mockery of the military, locks and keys through a million variations, Paco's minigame, party variety, why have unique levels for party members, end of the credits sequence, replayability as an issue in early 2000s games, ION Storm history, splitting off to be a rebel developer, how did this get made, game development rock stardom, Brett's film nerddom, going to Limbus and getting historical and religious context for the whole Chaos/Order thing, character design on Limbus, going to talk to Rowdy, circularity in the story, facial animation system, splitting up the party, heist movie, long car chase scene and Fatima's death, Kuleshov effect, what can and should games notice about player behavior, the final battle, how the Elementor crosses over or whether it does, area effect abilities, post-battle walk out scene, letting your freak flag fly, keeping players guessing, focus on writing and characters, being more playful, humor in games.

Welcome to Dev Game Club, where we are having our third discussion about 2001's quirky Western-built Japanese-style RPG Anachronox. We talk quite a bit about the specifics of this section of the game, including the combat elements and leveling, before turning to feedback. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: resolutions (or lack thereof) and taking stock, flying towards the Hive and having a railgun shooter, abstracting away from player skill in RPGs, hybridization, lack of loot, finding new offensive stuff in the environment, using the Elementor, colored bugs and finding them all over, the Hive Queen, saving Democratus and having it... join your party?, tonal shifting every couple of hours, movie tone management, no shackles, could you do this today?, indie studios doing widely different games, how would you do a sequel to this game?, drug missions in Far Cry 4, optional nature of diverse gameplay lending them less force, whether a pure episodic model could work, theoretical possibility of continuing the series, choice between Hephaestus vs Red Light District, Pumping Station, broader humor, introduction of Stiletto Anyway, Stiletto's special ability, tricky design problem -- locking off areas, Rho's description of what's going on quantum physics/astrophysics/temporal physics, moving mass between universes, incorporating the game's ideas all the way down into the UI, the Hephaestus mystery, characters moving around in the environment apart from you, useless randomization, getting the elementor, Krapton comics universe and Rictus the villain, storytelling with comic panels, hologram puzzles, the weird hero capture room, committing all the way to a planet as a party member, the electoral college mockery in 2000, hyperdiegetic lore issues, content coordination, the "dragon break", content coordination and licensing, listening out of order, book club.

Welcome to Dev Game Club, where we have a very special, year-end blast where we talk about some top take-aways and interview moments from the past year. And it's been a busy one, with six interviews and ten games discussed. Thanks for joining us this year. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: defeating Darth Vader, the complexity of the world and reflecting that in TIE Fighter, taking a twist on the Chosen One, developing the character of Gordon Freeman and ultimately cutting the cutscenes, having a scene of level designers competing with one another and also with other companies, making single-player content be moment-to-moment excellence, the enemy AI playing against you in X-COM, flying under the radar, adding dynamic difficulty at the last possible moment, Tim loses his X-COM save file, thematic and story integration, holistic design (between control/mechanics/camera/space), less is more, individual effort shining through, homogenization of game development, nailing the 3D camera, shipping your experiments.

Welcome to Dev Game Club, where we are in the midst of our discussion about 2001's quirky Western-built Japanese-style RPG Anachronox. We talk about the writing and humor, how those may have developed, and also discuss the characters and their characterization, among other topics. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: etymology of sly boots and other forms of boots, the writing style, broad and referential humor, the quest for a size five helmet, comedic space opera, particular interests in the humor, dark humor, lack of boundaries to the writing, Grumpos's Yammer ability, going back and forth with your party on Votowne, having to have Sly in your party, drifting in space conversations, walking a thin line of humor and menace, hinting at Detta before you meet him, is PAL's voice getting in the way?, lip-synching and fully-voiced cinematics, recording all actors in the same room, length of space cutscenes, edited together machinima, paying off on team and technical investments over multiple games, use of multiple locations, feeling like a television series, political commentary, gaining confidence in comedy, individualism in Votowne and Rho Bowman, use of space and environment in combat, combat speed, stone sentinel fight and combat design, figuring out the JRPG rock-paper-scissors stuff, combat challenge and depth (or lack thereof), enabling character dialog based on quest state, Sender Station Station, NPC state or location changes based on quest, boss battles, jeep battle section at end of MGS 1, marker system challenge in SWRC, air steering in Tomb Raider.

Welcome to Dev Game Club, where we are beginning our new series on 2001's quirky Western-built Japanese-style RPG Anachronox. We set it in its time, and discuss how we decided to play it and then spend a lot of time on its world-building. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: Games of the Year, how we came to choose Anachronox, 2001 in PC games, mash-ups, lack of character creator, is the character a Chosen One, possible character antecedents, world-building in simple ways and picking up things as you go, avoiding the lore bombs, dialogue trees vs continuing dialogue, progenitor race tropes, technology we don't understand but make use of, more character antecedents, film noir tropes, Boots as sad sack, layout of the introductory area and not getting lost, mix of architectural styles, moving city blocks around, putting ideas into games more quickly, investing in mechanics to make them pay off multiple times, boat action sequence, mini-games, shifting audience expectations, less forgiving audiences, changing suspension of disbelief, character names, a codex with all the names of stuff, potential fragility of scripting, thank yous, German B-thing, Tim's phone audio, musical touches in Mario 64, Brett's favorite Mario 64 levels, games we replay, Brett and Freud, picking games and timing, interviews, difficulty in getting Japanese devs, next time.

Welcome to Dev Game Club, where we are closing our series on 1996 3D platforming sensation Super Mario 64. We start at the end, discuss Koji Kondo's iconic music and finally, our takeaways, before turning to listener feedback. SM64 Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: the boss battle, getting better at the game, getting those red stars, finding a backflip shortcut, throwing Bowser and figuring out a pattern for yourself, listening for audio cues, desperation, difficulty of the final Bowser fight, having a one-up nearby, building that Bowser battle around the controller, training you for that final battle, ending games, weird final cake, the last few levels, Tiny Huge Island and finding Wiggler, Tim learns you can choose one or the other image to jump into Tiny Huge Island, secret stars, sliding down the ramp, the music, our John Williams, adapting simple melodies across multiple titles, the stickiness of a few Mario musical themes, pulling these melodies forward into modern games, comparing film music to game music, limitations of hardware influencing musical choices, the 3D camera working so well with the level design, accommodating a camera in your level design (vs not), the abstraction that allows exploration of 3D ideas and experimentation, decision paralysis, the hub and spoke structure revisited, not holding up as consistently, green cap, variant gameplay should be easy, endings of games are hard, new combinations of skills, appreciating the game as an adult, more developed critical skills, importing an N64 and renting it out, reconfiguring the levels, speedrunning Mario 64, Brett uses the F word, teleporting out of the world, extending the play of the world, getting to the unreachable coin, swimming in 3D platformers, wish fulfillment in games, octogenarians and nostalgia, physical competence, VR potentially having a role when we are old, targeting wish fulfillment to only one demographic, power fantasy, mobile fantasy fulfillment.

Welcome to Dev Game Club, where we are in the midst of our series on 1996 3D platforming sensation Super Mario 64. Tim intros the 'cast for the first time and we discuss both macro and micro design. SM64 Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: likening Brett to a car, increasing difficulty of stars within a hub, Brett getting all the stars for a bunch of worlds and figures out how he got there, red coin challenges, rising frustration but increasing skill, getting access to the second Bowser battle, hub and spoke structure, choices and exploration, building a sense of place by allowing players a bit of choice of which path to follow next, linearity as a review trope, sacrificing narrative for non-linearity, player choice reducing narrative urgency, abstraction of narrative helping with non-linear stories, avoiding stress and soft gating, finding stars out of order, dynamic difficulty built into design, maintaining order for consistency and communication's sake, courses as missions, wanting the clues to the other stars earlier, telling stories via stars, tagging the current star, move set with many possibilities from few inputs, triple jumping in place, gaining height, 100 coin stars, profound impact of the game, finding every way to die in Shifting Sand, adding new stuff that doesn't work as well, swimming in 3D character games, variant gameplay should be easier, the difficulty inherent in the flying controls and not making the transition well from 2D, experimentation, mods and getting in, the paintings and the world of 2D, maintaining some jankiness, leaving bugs in, giants killing you in Skyrim, adventure games and intentional blind alleys, motion sickness, being software driven vs hardware driven, gambling and children, not all characters created equal, matching loot box mechanics to the property.

Welcome to Dev Game Club, where we are in the midst of our series on 1996 3D platforming sensation Super Mario 64. We talk about level design, what permits its density, and then fall into a long chat about Nintendo's innovations in controls. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: whether or not Mario is a plumber, how many stars to get, "not every star is created equal," the different blocks and where you need them, roomier spaces and how level design is overlaid to have multiple goals in a single space, clarity of options but less clarity of use, gating stars based on preceding actions, underestimating the balance and tuning of the designers, progression of difficulty of the stars, best of both worlds, getting later stars by luck and the sense of discovery, quest-like nature of the stars (and did the names come first), camera setting up where you are, layering exploration in 3D and space and time to play and figure things out, analog nature of space, pulling your attention, getting through a challenge the first time (when you come back), neuroscience digressions avoided, integrating skills with time away, getting over the skills threshold, Whomp's Fortress and level design density, lessons for 3D level design, abstraction vs realism and context, basing design on mechanics and metrics, little digression of Super Mario Odyssey, the 7th star, values of each coin, finding the 7th star, mechanical depth with stealth sections, teaching the player fine motor control, designing to the controller, Wii Sports as a tech demo for the controller, teaching people to use the controller, a list of Nintendo's firsts, game makers vs toy makers, tangibility and holism and aesthetics of the total experience, taking risks with hardware, camera controls making more sense as buttons, camera attempts to work with your intentions based on Mario's facing, 8 red coin elevator and facing, discovering intentionality, partnership between player-camera-level design, mismatching level to camera, camera designers, using camera as cinematography to convey emotion but be playable, claustrophobic camera work in Tomb Raider 2013, centering the camera on a point you're circumnavigating, the first 3D platformer, the horror of children, whether AAA games are sustainable on $60 per unit cost, microtransactions in mobile, the Star Wars tax, IP secondary product monopolies, team size and content scale, boxed product cost, design against used games, closures, generation shifts, hit-driven business, pro controller, Nintendo solves my carpal tunnel problems.

Welcome to Dev Game Club, where we are just beginning a new series on 1996 3D platforming sensation Super Mario 64. We set the game in its time and then discuss the big up-front issues, particularly the camera and how new elements and mechanics sometimes require fictional underpinnings before turning to other issues, including listener feedback. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: situating the game in 1996, cover shooters, fully integrating new mechanics, carrying forward 2D mechanics to 3D mechanics, the physics implementation, momentum and friction, 3rd person camera and control, animation control vs player control in 3D vs 2D, dust effects, shadow circle for depth perception (not realism), the hedge maze and following a rabbit to develop the camera, putting control on the player and punting on difficulty, Brett's history with 3D Mario and other 3D platformers, waiting for the camera to catch up, micromanaging the camera, centering the camera behind Mario, splitting attention with the camera and easing up on difficulty as a result, simpler levels, fictionalization of mechanics, introduction of the camera, controlling a second person, Hong Kong cinema, other examples of fictionalizing mechanics, the uses of the Force, holograms in RepComm, big transitions in games history, commitment to solving the camera, various framing with the camera, level design of camera control, Tim's OCD approach, hats, snow physics, having difficulty with the pulled out 3D, analog level design, tighter difficulty in more 2D levels, macro loop of setting you back to the hub level, knowing how much the player has played via door gating, masters of onboarding, reinforcing 3D-ness via boss battles, forgiving damage wheel, Tim's theory of red squares, red mirrors mythology, achievements from a developer perspective, optionality of achievements, console ecosystems, not usually driving development, a trend we were forced to implement, trend towards game length, pricing models, Brett's music-deafness, horror music not calling attention to itself, ambient soundtrack vs score, suspending disbelief and buying into horror combat difficulty, repetition in combat, the possibility of threat, Final Fantasy XV block mechanic, P. T. as playable trailer, Maria ending, history of the 120 stars run, speedrunning record breaking.

Welcome to Dev Game Club, where we have made our way to that hotel in Silent Hill 2 and then wended our way homeward. We discuss the climactic events of the game, our theories on who represents what, the multiple endings, and a host of other issues including takeaways and listener feedback. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: the chainsaw and why I didn't use it, Tim's last bit of the prison (getting stuck in the Purgatory room), the dumb keypad puzzle, Tim admits again that Brett is smarter, puzzle opacity, actually moving the room around, puzzles with thematic elements, the gallows area and the scary audio, Brett's play time and Tim's, finding Maria again, attract mode and Maria scene, Tim wanting more from the Maria moment, Brett's theory of Silent Hill and guilt, distinctions in Western vs Eastern horror, Eddie and Angela failing to escape their inner guilt, James maybe getting out, Silent Hill as private hell, Laura as potentially a desired child, psychology of a victim, evidence supporting Angela as molestation victim, the lack of rationality of the space, developers intentions toward surrealism/abstraction, is this room pumping out fog?, Eddie's psychotic break, the weird design choice to have long hallways and empty rowboat sections, James's water plane, similarity of hotel structure to apartments, the shelf and the elevator, the disappearing letter, "They Metroided you," the stealth mechanic, the tin can of light bulbs (and phoning it in), choice of environments across the game, watching the video tape and how Mary died, the use of the radio in the room, overly subtle choices, hotel degrading further, supporting multiple endings, what James needs vs whether Mary is in some sense real, the various endings and how to trigger them, commitment to symbolism and themes, Pyramid Head as most iconic horror figure, economical design, fog and lighting technology vs longer draw distances, flashlights, focusing on a few things rather than longer draw distances, indie games drawing from Silent Hill 2 rather than Resident Evil, Tim doing the intro, difficulty settings and mechanics, surfacing mechanics poorly, resource management, lack of threat, vulnerability.

Welcome to Dev Game Club, where we are in the middle of our three-episode series on Silent Hill 2. We spend a lot of time talking about the section in the hospital and the potential meaning or personification of Pyramid Head. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Sections played: Up until the Labyrinth

Podcast breakdown: 0:34 Single segment this week!

Issues covered: Tim's Halloween costume, picking favorite moments, Pyramid Head first interactive encounter, his reputation, character design, ninja/tabi boots, wading right off into the water, following Pyramid Head, water as a theme, the drowned people under the lake, possible subtext, anthology rather than series, New England horror vibe, "something's up with that kid," differences between Maria and Mary, madonna/whore complex, James's reactions, the uncanny valley of character motivations, an "adult game," having different versions of Laura Palmer, influence of David Lynch's films, companion AI, game over if you kill Maria accidentally, running into Eddie in the bowling alley, seductively posing Maria in various locations, turning companion AI into strengths, a place more terrifying than the apartments, "ugh, the nurses," discomfort with sexuality, being uncomfortable in a hospital with his dead wife, is it all in your mind?, the doctor's note and the "other side," Pyramid Head as a personification of an idea rather than a character, map mechanics though they could be better, lack of distinction between rooms you must have to visit and those you don't, what's the use of an empty chest or a mimic in RPGs, Maria lying down and the breathing in the other side, the rooftop weirdness, does Pyramid Head trigger the radio, silly keys, best key in a video game: hair and bent needle, James turns his head at items of interest, green goop, RE training you to follow the science, Laura knows Mary from the hospital, maintaining the pieces that fits and dropping the clues that don't, the creature design of the Flesh Lips, tilting camera, how Brett measures space, map reset, production value foul, question of when Maria comes to the other side, Tim kills Maria, losing Maria to Pyramid Head, unnecessary combat working against horror, descending down down down, do you want to jump down the hole?, the weird hotel game show, humor in Asian horror, fidelity in horror games, lethality and vulnerability, embracing style, a handful of scary lo-fi games, less is more.

Welcome to Dev Game Club, where we are just beginning a new and shorter series on Silent Hill 2. We set the game in its time period, and dive in quickly to the madness that brings us to that quaint little town, Silent Hill. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Sections played: Up through the end of the apartments

Podcast breakdown: 0:37 Silent Hill 2 51:15 Break 51:45 Feedback

Issues covered: revisiting our interview with Julian Gollop, Julian's mum, PlayStation 2 year one, dividing the critical audience with The Room, Konami firing Kojima and turning to other industry, Tim not knowing what the game was, campiness of Resident Evil, walking through the apartments in the dark, the fog and short draw distance, how the game starts, elegant narrative, putting you in the mind of the protagonist, grief, "early walking simulator," immediate tension and danger, psychological thriller and horror elements, the camera -- fixed vs semi-fixed, build-up of tension, no cognitive dissonance between player and character, id/ego/superego, economy of design, bold choices in controls, intention through controls, audio terror and musical stingers, PlayStation technology, fog particles and fill rate, interior darkness, Tim's television environment, complicity, bloody footprints, jump scares in RE vs knowing something's coming (via the radio), learning through failure with a jump scare, Riddle Difficulty, lock and key puzzles, Harry Mildred Scott, case of canned juice, examining objects, save game representation, red handkerchiefs, Pyramid Head's blood and gore, psychosexuality, the enemies with the legs top and bottom, Pyramid Head as Id, Ego in James hiding from the Id, fear of confronting the primal, contra Nemesis or other RE enemies, the other characters, hallway reuse, description of PT, difficulty and usability, building a game for yourselves, wider demographics, more conservative finances, maintaining the young perspective, finding the right difficulty for your goals, size of the space in Souls games, Silent Hill remaster, some technical concerns, horror is about what you can't see, emulating the original experience, streaming stuff over the web, playing on a CRT, having a lot to respond to, layering in unexpected variables in X-COM, picking classics, the stuff that sticks with you, the complexity of the Oblivion leveling system, Skyrim as aspirational leveling system.

Welcome to this special bonus interview episode of Dev Game Club, where we welcome Julian Gollop into X-COM Base Provolone for a chat. We delve into the genesis of the game, how a publisher saved the game and itself, and many other topics surrounding the development of the game. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: Julian's ludography, genesis of X-COM, adding isometric rendering, Microprose's demands of the Gollops, interceptions, bolting on a strategic layer atop the tactical model, having more intelligent aliens and reverse engineering, men in black not making it in, intrapublisher competition, tabletop boardgaming and influence, miniature wargaming, simultaneous movement games, division of labor, geoscape rendering, going to the pub with the producer, getting canceled and not knowing about it, being developed under the radar, QA standing up for the game, working in-house, seeing through the cruft, advancing the alien agenda (mission counts), scaling difficulty, game not being played through before ship, small QA team, adding a difficulty scaling system last-minute, the save game bug, enjoying a simulation of intelligence (of an alien nature), how the alien tech tree works, deployment tables for mission types, save-scumming, theorizing about the difficulty curve, difficulty as draw and happy accidents, "When gamers were gamers," QA as a critical team element, explicit research goals, research as storytelling, procedural generation of level tile placement, descriptions of Phoenix Point, 4X with a declining population, explicit story, the Phoenix Project.

Welcome to Dev Game Club, where we are quickly going over the beginning of X-COM: Enemy Unknown. Surprisingly, although we both liked it, we preferred the original. Stockholm Syndrome? Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: Firaxis's recent history, preferring the original, investment bias, hitting a stride in the original, usability improvements, holding your hand a bit, flowchart for learning stuff, complete hand-holding, constant camera cutting, a lot of loss of drama, dynamic cameras, camera cutting and immersion, base management, playing the original right next to the remake, playing chess, the rules you make up for yourself, reducing squad size, increasing depth, subclassing characters, ability trees, how do you determine what class a guy should be, tactical improvements due to classing, reducing the time unit complexity, more intuitive opportunity fire and movement, streamlining and removing the jazz improvisation, how far do you streamline?, discrete time units, making a game more shallow to broaden the audience, being explicit about the geopolitical game, board game nature of panic monitor, you can see interesting decisions coming from the geopolitical game, interesting and hard choices, having to pick one or the other, puzzle aspect of balancing choices and rewards and panic, panic and DEFCON, abstracting time management, hitting a stride with the original, Metal Gear naming, Big Boss on the Memorial Wall, getting into game development, a bit of horror discussion, games not existing in a vacuum, loss of context for the creation of art.

Welcome to Dev Game Club, where we are in our third in a series of episodes about 1994's X-COM: UFO Defense. We wrap up our discussion of the game, covering save-scumming and difficulty, and talk about some pillars and takeaways. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: the terror mission that kicked Tim's butt, getting under your skin, "super-gratifying," difficulty curve a bit too steep, quitting the game early, interceptor trouble, plasma clips, the United States pulling out, powered armor, aliens I have seen, experimentation and determining enemy behavior rules, negative connotation of save-scumming, fairness, save-scumming to survive, aggressive play, discovery and save-scumming, setting up the second playthrough, smoke inhalation, planning around the 88% shot, forcing improvisation, figuring out elevations and other rules for line of sight, pacing and rhythm and controls, waiting on research and manufacture, endless learning curve, sending out the rookies to die, how medkits work, motion scanner use, the first two turns, flanking more, chain reactions, multilayered interdependent systems at the tactical level, having to deliver on the tactical combat, alien autopsies, player-driven stories, escalation of the game, invasion story to counter-invasion story, wish fulfillment of being a government bureaucrat, "they said yes to a lot of things," generosity in game design, scaling generosity because it's a sim, why games didn't incorporate time in calculations, Bad Designer No Twinkie, modding in games, unique ability of games to mod, why Vagrant Story is so good, restoring Brett's blog, horror games,

Welcome to Dev Game Club, where we are in our third in a series of episodes about 1994's X-COM: UFO Defense. We talk about our plans of attack for the game, whether the game is reacting to our plans, and how sim games make an argument. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: Tim's death of dysentery, Tim's approach and Brett's approach, reserving time for opportunity fire, how time units scale, ranking soldiers and hierarchy, mastery of sims, taking down a much larger UFO, is it dynamically scaling?, algorithms and tables, board game systems, complexity from simplicity, how a simulation makes an argument, visibility of rules and systems, how X-COM promotes anxiety, lack of telegraphing, wasting a player's time, the RNG and drama, strategy and planning and percentages, entertainment vs anxiety, do aliens panic?, flocking/herding/schooling behaviors, learning the AI's rules, looking forward to a modern version, exploits vs learning behaviors, empowerment of setting a trap, naming your troops and telling stories about them, streaming's impacts on games development, increasing player customization as a means of authoring, MOBAs as streaming games, shooters having difficulty crossing over, randomness in games, rewarding success because of the possibility of failure, RNG and the level layout, accessibility vs complexity and depth, transparency and mystery, over-indexing on accessibility working against aesthetics, diving deeper into games, thinking ahead to making a sim game of my own.

That week, the Dev Game Club podcast welcomes special guest Ken Levine, founder of Irrational Games and designer/writer of System Shock 2! Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: "Shock" prototype, Looking Glass relationship and Ken's early career there, Irrational Games beginning, business structure, imagining your audience and what you'd like to make, fingering .plan files, emergence and immersion, simulation, persistent world, personal ownership of experience, engine strengths and weaknesses, making fish stew, the benefits of constraints and happy accidents, polish, sense of place, naturalism in a science fiction setting, making the most of minimalism, turning a weakness into a strength, economical design, race track design/nooks and crannies, lack of time for level review, "spreading the butter thinner over the bread," elevator as storage chest, balancing, player skill vs. character skill, the "genius of the novice," story influences and groundedness, leaning on the audio space, writing towards the voices you have, bringing everything you have to the party, single-player squad shooters, letting people figure things out, crunchier design, the pendulum of accessibility, dealing with player frustration as a resource, what next

Welcome to Dev Game Club, where we are in our third in a series of episodes about 1994's X-COM: UFO Defense. We talk about the ways in which procedural generation and written generation interact a bit, as well as detailing our playthrought a bit. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Issues covered: opportunity fire cost, reserve time units, how much things cost, how we did on our goals, Brett starting over and why, researching yourself into a whole, games are a a series of interesting decisions, what are we willing to live with, difficulty knowing how you're doing, failure conditions, Tim's rocket launcher opener, alien mental effects, tile generation algorithm for terror attacks vs downed UFOs, procedural generation at its best, an engine for wonderful moments, tuning procedural generation, multiple states for tiles, persisted state of tiles, telling a story via your swath of destruction, screaming deaths of civilians, center of the UFOs, determining when to reload a save, procedural vs written content (e.g. tech trees), Brett's base management, how does science and research work, Monty Haul problem, providing two ways of thinking about/explaining a problem, psychology in game design, tricks in game design, board game popularity.

Welcome to Dev Game Club, where we are beginning a series of episodes about 1994's X-COM: UFO Defense. This week, we talk about terror attacks, game tension, gratification, and a bit of base management. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.

Sections played: A few hours past the first ground mission

Podcast breakdown: 0:38 Segment 1 41:18 Break 41:47 Feedback

Issues covered: managing the clock speed, difficulty of the game and having to get better, failure screens, terror attacks, meeting different alien types, starting over again and getting more ground missions, learning the dynamics of covering one another, being unable to understand line of sight, infiltrating an UFO, contributions to tension, researching tech tracks, being unable to capture an alien alive, the use of radar dishes, recruiting scientists and soldiers, base building, the research loop and discovering what's out there, weapon lists, no storage of time units, energy costs, soldier stats, deep management, saving mid-ground mission, AI difficulty balance towards fairness, developing difficulty more towards numbers changes than behavioral ones, real-time flight combat, finance game, QAing a game like this, QA and developer skill and having trouble identifying how difficult to make your game, gratification of mastery or partial mastery, pin and fork moves in chess, fire propagation, learning how to use grenades, losing bodies and artifacts to grenades, alien deployment curve, tutorials, incorporating lessons without folks knowing they're being taught, underestimating tutorial building time, taking your time to build skills over multiple small levels, layering in simulation.