RDR dev: Crunch was for the show not fixing bugs

The pursuit of video game perfection often comes with a steep cost, but for some developers, the most taxing experience isn’t the coding itself—it’s the relentless pressure of the crunch. Kris Roberts, a figure deeply embedded in Rockstar’s history, offers a candid look at how corporate demands can warp the definition of dedication, especially when aiming for cinematic masterpieces.

Roberts’ journey at Rockstar began with tuning vehicles for the Midnight Club games, a foundation that would later lead him to lead the design of multiplayer modes for the epic Red Dead Redemption. As his role evolved, so did the expectations placed upon him. Initially working as an hourly employee, Roberts transitioned into a position described as “full-time,” navigating a shifting landscape of mandated working hours.

The definition of ‘core hours’ at the studio was not static. What began as specific daily commitments gradually expanded, evolving from standard workdays to mandatory Saturday sessions, and eventually, even Sundays became encouraged, if not entirely optional. This gradual expansion set the stage for the intense, all-consuming environment that characterized the final development stages of major titles.

However, the narrative of crunch took a particularly grueling turn during the final six months of Red Dead Redemption. Roberts described this period as a blur, where sleep deprivation led to a state of amnesia regarding the exact sequence of events. More frustrating than the lack of quality rest was the feeling that the overtime was not driven by a desire to improve the game, but rather by a performance requirement for executives.

Roberts pointed out that the overtime felt less like necessity and more like putting on a public demonstration. He recalls specific instances where management would mandate presence, using executive visits as justification for demanding extended hours. He recounts being told to be present on Sunday, regardless of the actual development needs, simply to facilitate a display of corporate attendance.

“It wasn’t about fixing bugs or addressing critical issues,” Roberts explained. “It was about putting on the show of appearance that everybody’s here all the time, because we had an executive visiting or something.”

As the multiplayer design lead, Roberts found himself tasked with communicating these increasingly artificial expectations to his team. This realization proved to be a significant turning point. He felt conflicted about voicing these long-held frustrations, particularly since he had previously engaged in “self-directed” crunch on earlier projects. The realization that the pressure stemmed from external performance metrics, rather than creative necessity, contributed to his eventual decision to step away from the studio.

Roberts’ experience underscores a larger debate within the gaming industry regarding work-life balance and developer well-being. While some employees found ways to mitigate the strain, others, like Roberts, found that the structure of the work itself became the source of profound frustration, prompting a search for a more sustainable environment where creativity and quality are prioritized over mere corporate spectacle.