Welcome to Dev Game Club, where we this week we turn to the start of our bonus content about DOOM. We look at 2016's re...boot? Reimagining? Re...launch? of DOOM and talk about its modernization of mechanics and its resource loop, before turning to catch up on the mail bag. Dev Game Club looks at classic video games and plays through them over several episodes, providing commentary.
First few levels
0:41 DOOM talk
Issues covered: Tim likes to get into the lore and how this supposedly ties all the DOOMs together, Tim's free time, what it's like rebooting something, how do you deliver a modern version of a classic game, infinite interconnected positive reinforcement resource skill loops, drawing you in with glory kills, combat stats and finite enemies, how DOOM feels visceral, risk/reward in the glory kill mechanic, the limits of long-range combat in other shooters, dealing with the Hell Knights and being forced retreat, orthogonal enemy design, being put off by the demo, leaning into the heavy metal, corridor/arena design and length, having characters to interact with, thinking about the game when you're not playing, difficulty, how the game improves as level design starts to get more abstract, being a little at odds with itself, lack of aim-down-sites, lower maximum ammo, appreciating tight tuning, the NPC similarities, influence of art direction, having a space make sense as a place you've been, not stopping to think, playing as a designer, Tim vs Brett as how they play and disconnect if they can, WASD becoming a thing, what control schemes and controllers might work, VR controls, MOBAs and ability triggering, naturally using your hands, eye-tracking as another improvement in interfaces, finding the one game that encapsulates all sorts of play, player-created narrative vs authored narrative, "welcome to the Nether," teaching game design, using analysis to get at mechanics and their connection to dynamics and aesthetics, source ports, multiplayer being important to a campaign, being in communication with players through knowledge vs social media, the uniqueness of SIGIL, games as products, having multiple player types, figuring out your relationship with players, .plan files, designer/developer interaction through plan files, Usenet, art and games as a gift, being able to give more to your players, Brett's Book Recommendation, expansion and contraction in game design, the natural rhythm of play matching breathing, natural pacing, AI story direction to manage tension, focusing on a single enemy as a contraction.
Games, people, and influences mentioned or discussed: id Software, Prey, Dishonored, Call of Duty, Zenimax/Bethesda Game Studios, Republic Commando, Rage, Quake (series), Wolfenstein (series), Machine Games, Raven Software, Half-Life 3, Bioshock, Terminator 2, Total Recall (1990), Viktor Antonov, Unreal Engine, Cry Engine, The Evil Within, Resident Evil, Tacoma, Gone Home, System Shock 2, Austin Powers (series), Logan's Run, Michael York, Gilmore Girls, LucasArts, Daron Stinnett, Tomb Raider, Mike Vogt, Apogee, Dark Forces, GOG, Ingar Shu, Valve Software, Kinect, DoubleFine Studios, StarCraft, WarCraft, Facebook, Oculus, Horizon Zero Dawn, Mass Effect, Mikkel Lodahl, Minecraft, Nintendo, Legend of Zelda (series), Mario (series), Metroid (series), Disney Infinity, Project Spark, Little Big Planet, This War of Mine, Sam Thomas, SIGIL, Unreal Tournament, LEC-Quake, Ryan Troock, John Romero, Mario Maker, Halo (series), Ken Levine, John Carmack, SiN, Levelord, George Broussard, 3DRealms, John Yorke, Masters of DOOM, James Franco, The Disaster Artist, Tom Bissell, Paul Reiser, Mad About You, Oscar Fiasco, Link's Awakening, Day9, Super Mario 64, Starfighter, Left 4 Dead, Silent Hill 2, Thief: The Dark Project, Eternal Darkness, Nathan Martz, Alan Wake, Control.
Either a guest... or a bit of Eternal Darkness, check your local listings (i.e. Twitter)
https://twitch.tv/brettdouville, @timlongojr, and @devgameclub