Buying Options
| Print List Price: | $17.99 |
| Kindle Price: |
$10.99
Save $7.00 (39%) |
| Sold by: |
HarperCollins Publishers
Price set by seller. |
Follow the Author
OK
Blood, Sweat, and Pixels: The Triumphant, Turbulent Stories Behind How Video Games Are Made Kindle Edition
|
Jason Schreier
(Author)
Find all the books, read about the author, and more.
See search results for this author
|
|
Price
|
New from | Used from |
|
Audible Audiobook, Unabridged
"Please retry"
|
$0.00
|
Free with your Audible trial | |
|
Audio CD, Audiobook, CD, Unabridged
"Please retry"
|
$22.74 | — |
Explore your book, then jump right back to where you left off with Page Flip.
View high quality images that let you zoom in to take a closer look.
Enjoy features only possible in digital – start reading right away, carry your library with you, adjust the font, create shareable notes and highlights, and more.
Discover additional details about the events, people, and places in your book, with Wikipedia integration.
-
LanguageEnglish
-
PublisherHarper Paperbacks
-
Publication dateSeptember 5, 2017
-
File size1355 KB
![]() |
Customers who bought this item also bought
Customers who read this book also read
Editorial Reviews
From the Back Cover
The creative and technical logistics that go into building today’s hottest games can be more fraught with challenges and complex than the games themselves, often seeming like an endless maze or a bottomless abyss. In Blood, Sweat, and Pixels, Jason Schreier takes readers on a fascinating odyssey behind the scenes of video game development, where the creator may be a team of six hundred overworked underdogs or a solitary geek genius. Exploring the artistic challenges, technical impossibilities, marketplace demands, and Donkey Kong–sized monkey wrenches thrown into the works by corporate, Blood, Sweat, and Pixels reveals how bringing any game to completion is more than Sisyphean—it’s nothing short of miraculous.
Examining some of the bestselling games and most infamous failures, Schreier immerses readers in the hellfire of the development process, whether it’s RPG studio BioWare’s challenge to beat an impossible schedule and overcome countless technical nightmares to build Dragon Age: Inquisition; indie developer Eric Barone’s single-handed efforts to grow country-life RPG Stardew Valley from one man’s vision into a multimillion-dollar franchise; or Bungie employees spinning out from their corporate overlords at Microsoft to create Destiny, a brand-new universe that they hoped would become as iconic as Star Wars and Lord of the Rings—even as it nearly ripped their studio apart.
Blood, Sweat, and Pixels is a journey through development hell—and ultimately a tribute to the dedicated diehards and unsung heroes who scale mountains of obstacles in their quests to create the best games imaginable.
--This text refers to the paperback edition.Review
A lively, informative look at how a video game gets made...The author, who writes for the video-game website Kotaku, is clearly a huge fan of video games, and his enthusiasm is contagious.
-- "Booklist"Making video games is one of most transformative, exciting things I've done in my two decades as a freelance writer. Making video games is also an excruciating journey into Hellmouth itself. Jason Schreier's wonderful book captures both the excitement and the hell. Here, at long last, is a gripping, intelligent glimpse behind a thick (and needlessly secretive) creative curtain.
-- "Tom Bissell, author of Extra Lives and Apostle"My only complaint about Blood, Sweat, and Pixels is that there wasn't more to read.
-- "Forbes" --This text refers to the audioCD edition.About the Author
From the Inside Flap
The creative and technical logistics that go into building today's hottest games can be more fraught with challenges and complex than the games themselves, often seeming like an endless maze or a bottomless abyss. In Blood, Sweat, and Pixels, Jason Schreier takes readers on a fascinating odyssey behind the scenes of video game development, where the creator may be a team of six hundred overworked underdogs or a solitary geek genius. Exploring the artistic challenges, technical impossibilities, marketplace demands, and Donkey Kong-sized monkey wrenches thrown into the works by corporate, Blood, Sweat, and Pixels reveals how bringing any game to completion is more than Sisyphean--it's nothing short of miraculous.
Examining some of the bestselling games and most infamous failures, Schreier immerses readers in the hellfire of the development process, whether it's RPG studio BioWare's challenge to beat an impossible schedule and overcome countless technical nightmares to build Dragon Age: Inquisition; indie developer Eric Barone's single-handed efforts to grow country-life RPG Stardew Valley from one man's vision into a multimillion-dollar franchise; or Bungie employees spinning out from their corporate overlords at Microsoft to create Destiny, a brand-new universe that they hoped would become as iconic as Star Wars and Lord of the Rings--even as it nearly ripped their studio apart.
Blood, Sweat, and Pixels is a journey through development hell--and ultimately a tribute to the dedicated diehards and unsung heroes who scale mountains of obstacles in their quests to create the best games imaginable.
--GameZone --This text refers to an alternate kindle_edition edition.Product details
- ASIN : B01NAKSWW1
- Publisher : Harper Paperbacks (September 5, 2017)
- Publication date : September 5, 2017
- Language : English
- File size : 1355 KB
- Text-to-Speech : Enabled
- Enhanced typesetting : Enabled
- X-Ray : Enabled
- Word Wise : Enabled
- Print length : 300 pages
- Lending : Not Enabled
- Best Sellers Rank: #59,013 in Kindle Store (See Top 100 in Kindle Store)
- Customer Reviews:
Customer reviews
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
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.
no real details of personl drama to help you connect. Stardew Valley came closest, but that was a one man show.
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 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!
Top reviews from other countries
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.
Small games company has idea for a great game
They write software which takes a lot longer than planned so many late nights are required
Money is tight so funds need to be raised
Game is finally released to much acclaim
It'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.
I think the book would've been better if it was instead structured according to the typical process and stages of gaming development production. It would have removed some of the repetition, and it would have resulted in a much shorter read, but if the author researched more games, he could've had enough good research for a good 250 - 300 page book.
It is quite the story but when you've read the tenth consecutive version of it you begin to wonder if something is off either in the story or the telling thereof. Without a doubt it's well researched and I was gripped to those first few chapters.
But then it becomes apparent that every story plays out to the same template with some interesting omissions made to fit the narrative. Hit me especially during the Destiny chapter, a story of hope outreaching it's grasp to hear it here.
No real discussion of the business practices that lead to such an incomplete game being released, of the DLC model filling in the gaps or the monetisation that crept in after. Just plucky endeavor and long hours at the code mines. It's quite the story but not really a definitive one.













