Categories

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.