Blood, Sweat, and Pixels: The Triumphant, Turbulent Stories Behind How Video Games Are Made Kindle Edition

I've been a reading of Kotaku and a listener of SplitScreen for some time, and I was very excited when I found out Jason was writing this book. The book does not disappoint. The stories of each game's development is well crafted and told expertly. Each story had its own twists, its own suspense, sometimes ending in triumph, other times ending in sadness. Even for the games for which I knew the basic story, I was already surprised by new information and I felt as though I didn't know what was going to come next. That's the sign of a great storyteller, and Jason is certainly that.Two points that stick with me as I think about this book that I hope help you decide whether to read it (which I highly recommend you do). One is that I have a much greater respect for game developers at all levels of the process. Making video games is a cruel, life-sucking process, whether you work for a big studio or are a single developer trying to make the next big thing. The studios that strive to put out good work are busting it every day, and for those studios and individuals that really care about making good games, this book will illustrate why they deserve that praise even if they make a game that doesn't come out great. The other point that sticks with me is that the video game industry seems incredibly broken. Jason talked about this on the podcast and the overall sustainability of the industry, but it certainly seems like something is going to give soon given what game developers have to endure just to get something done. I don't know what that will look like or when it will happen, but this book clearly shows that something has to change.There's only one thing that bugged me about the book, though not enough to knock it down a star. I wish the last two chapters had been switched. Star Wars 1313 is such an incredibly sad story that having that finish off the book left me feeling really depressed about the book as a whole and almost colored the book more negatively as a result. The story of Shovel Knight, on the other hand, with a scrappy team with a huge vision was a much more uplifting, inspiring story even if it doesn't have a perfect ending. I wish the book had led into the epilogue with that ending. I understand why 1313 was put in last: it's the story everyone wants to get the inside scoop on, so save it to the end. Still, I think the book could have ended on a more positive note, and switching the last two chapters I think would have done the trick. That's pretty nit-picky and a bit of a personal preference though.Overall, I highly recommend this book for anyone who likes history, likes videos games, or just likes good stories. Props to Jason on this excellent book. I look forward to his next book, whatever it may be.

most of the stories seem the same. a group is super pumped about an exciting unprecedented game idea. it takes longer than expected. they crunch. they take even longer. they finish.no real details of personl drama to help you connect. Stardew Valley came closest, but that was a one man show.

Overview – Jason Schreier’s Blood, Sweat and Pixels is a fascinating look at how videogames are made from a production standpoint. Taking ten games, ranging from indie-darlings to the most high-profile games made in the last decade, he investigates the production process to determine what does it take to make a hit game. Written as a series of exemplars, Jason Schreier highlights how each game’s development is different but experience common challenges.Each exemplar is well-written and an unexpected page-turner. Part history and part business textbook, each exemplar has lessons for those outside the gaming industry. While each of the 10 games are a good read, Jason Schreier leaves it to the reader to identify the good project practices and lessons. Project management is incredibly difficult, Scherier illustrates how high profile games have multiple teams that are interdependent (for example: the art team is reliant on the tech team and vice-versa). Recommended.The Good – Each of the ten games that Jason Schreier uses as examples are well known. He goes into how each were developed, the problems, and how they may have been overcome. Few of the games were 100% successful, with many of the production problems dragging down the game’s final reviews and sales. He is sympathetic to the designers and that shines through.The Bad – Jason Schreier loves videogames – and this book is an ode of those in the industry. The book reads like a series of vignettes as opposed to a unified whole. Each vignette is interesting but if the reader is looking for a book more focused on the business and project management of videogames, than it will be a disappointment, but still a fascinating book. It would have been valuable if Schreier highlighted some of the games that appear to have a less rocky development process (such as Call of Duty or Madden) to illustrate successful production methods.

I gotta say, I'm a sucker when I comes to a biography or documentary. ESPECIALLY one that delves into the world of game creation. I'm a avid read of Kotaku, so when this gem popped up in the "about me" at the end of a Jason Schreier article, I knew I had to check it out! I will say that I'm not typically as interested in the "AAA" game development process as I am an indie game, but these chapters give enough information that I found reading those almost as interesting. But that's me,...nothing to do with Jason's writing style. That beings said, my two favorite chapters were "Stardew Valley" and "Shovel Knight". I'll admit, Stardew Valley really isn't my style of game (I tried it once), but the story behind it was amazing! Also, Shovel Knight I've never actually played, but this book made me get the game, so it does a really good job there! Each chapter tells a different story of the "creation" of a particular game. It doesn't go into all the details about what programs are used of where the workers got start in the industry (does tell backstories of a few during different chapters, but no particulars). It basically starts from where the game idea began and how it unfolded,...for better or worse.I can only hope that Jason Schreier continues with more of this in the future. I'd love to hear about Five Nights at Freddy's, Ori and the Blind Forest, and Inside!Final Verdict: If you enjoyed  Indie Game: The Movie , this is a must read! If you enjoy reading anything about the creative process of video games, this is a must read! You know what, just read it! You won't be disappointed!

Making video games is hard work, whether you're a solo operator developing an indie game inspired by a Nintendo classic or an experienced team of 200 working with a budge in nine figures. In this book, video game journalist Jason Schreier investigates the making of ten different video games: Pillars of Eternity, Uncharted 4, Stardew Valley, Diablo III: Reaper of Souls, Halo Wars, Dragon Age: Inquisition, Shovel Knight, Destiny, The Witcher 3: Wild Hunt and Star Wars: 1313.Most people know that the making of video games is a difficult, long-winded and expensive process. But just how long-winded and expensive that task is remains mind-boggling. This book explores some of those stories. A single cancelled contract almost destroyed veteran video game studio Obsidian Entertainment, until they launched a successful Kickstarter for an old-skool RPG called Pillars of Eternity that was a big commercial hit and saved the company. Naughty Dog Studios had already delivered three critically-acclaimed Uncharted games and were a well-oiled machine, but still almost crashed into ruin whilst making the fourth game in the series. Blizzard Entertainment had been a 20-year veteran of game development with almost 100 million games sold but still managed to release Diablo III in a chaotic and divisive state, forcing them to save the game with an expansion pack that revamped a lot of how the game worked. Star Wars: 1313 was a game that looked absolutely amazing and was playing very well when it was abruptly cancelled when Disney took over LucasArts in 2012, flushing several years, tens of millions of dollars and thousands of hours of work down the toilet.Schreier recounts the story of each game in a well-researched, intelligent manner based on interviews with the people involved and, in some cases, spending time embedded at the studio in question. Arguably the most fascinating chapter is on the development of Stardew Valley, a rare modern game created by just one person (Eric Barone), showing the insane work required to bring what is apparently a very simple game idea to the masses. The most explosive is certainly about the development of Destiny, an online game created by Bungie Studios to escape the treadmill of developing Halo games until the end of time, but that was easier said then done and by the end of development most of those who had been pushing for abandoning Halo had left the company, leaving a lot of anger and bitterness behind (which is an ongoing story, through the problematic release of Destiny's expansion and sequel). The most frustrating story is that of 1313, a genuinely exciting-sounding game that was killed in its infancy.If there are any negatives to the book, it's probably the lack of depth. The book can only give about 25 pages to each project, and often the chapter ends just as the story gets interesting and we're moving onto the next game. There could also be better context: the Diablo III chapter focuses on the expansion, but we learn nothing about the ten-year development of Diablo III itself and why the game ended up being released in such a chaotic state. The Witcher III chapter also lowballs the game's reportedly hellish crunch period, which led to many people leaving the company (also it also resulted in arguably the greatest video game of the last twenty years). You occasionally feel that Schreier pulls his punches - at least a little - to retain future access to the companies involved.That said, if you play video games but have no idea how they're made or the workload involved, this book (****) will be revelatory. Well-written, informative and entertaining, it marks a good beginner's guide to the crazy world of making video games.

I'm only halfway through but this isn't a book hinging on it's ending so I'm comfortable writing a review (if Paltrow's head is in a box in the final chapter, it will be a bonus). The book is well written, full of nifty details about the industry that feel refreshing and eye opening rather than depressing. The kindle version I purchased is great as it lets you jump straight to the linear notes (via a blue star) then jump straight back to your page. Some people prefer the tactile nature of a hardback but this linear note hot-swapping is a godsend for this type of book. I look forward to reading the rest and finding out who this pesky Keyser Soze really is.

Mostly a quite enjoyable read overall but each chapter was very similar:Small games company has idea for a great gameThey write software which takes a lot longer than planned so many late nights are requiredMoney is tight so funds need to be raisedGame is finally released to much acclaimIt's not a technical/geeky book, so if you're into the nuts-and-bolts of writing games or how to develop a game, this isn't the book for you. It's pretty high level and while quite interesting as to how these gaming companies managed to release their games, there's nothing that exciting here.

This is my first book based on games and it was definitely a great introduction to the gaming industry. Each chapter is based on a different game and how the developer sought to deliver it to he public without getting too heavy on politics or specific knowledge of the games in question. One lesson I have learnt from this book is how many developers over promise and under deliver and it’s a shoddy practice that needs calling out a lot more. The interviews with staff and team members are insightful but for each chapter I wanted a little more meat on the bones of it all. This might be a bit of a stretch given game companies don’t really want to talk about their struggles publicly, however the author has certainly received some good sources for the material. A good book and would happily recommend to anyone interested in games.

An incredibly in depth and interesting look into the development process of some of the most popular video games out there, which didn't fail to keep me hooked to each page, I highly recommend Blood Sweat and Pixels.With each chapter focusing on the story of a particular game, the book is perfect reading I'm bite size chunks, ie whilst commuting, or in one sitting. The stories behind the games are entertaining, enlightening and surprisingly emotional, and while a cynical mind may say they could have been an article on a video games website, the long form format offers the author a chance to go deeper into each development story, and it's an opportunity which has clearly payed off, interviews and painstaking research intricately woven together to forming a compelling narrative. I couldn't put this book down, and am already planning on gifting it to friends and family so they can experience it for themselves.I look forward with great interest as to what is next for Schreier, with stories like that behind the troubled development and release of Mass Effect Andromeda the perfect fodder for a sequel.Tl;Dr - if you like games, read this book. If you don't play or like games but know someone who does, buy it for them, and read it before giving it to them. You won't regret it.