In this post, we continue our English translation of Famitsu’s 25th anniversary roundtable with the original Shenmue developers. In Part 1, the team recalled the brutal work culture, the “general election” that decided the lead programmer, and how some staff turned themselves into NPCs.
Part 2 turns to the harsh realities of debugging, with stories of cardboard naps, 24-hour shifts, bizarre bugs, and the obsessive attention to detail that made Shenmue both a nightmare to create and a one-of-a-kind masterpiece.
The Harshness of the Development Environment
Hirai: You really shouldn’t be starting meetings at 10 p.m., right? We did have a nap room, though. That said, my previous company wasn’t very different, so I thought, “Ah, it’s the same here too.” That was just the era we were in. Still, during Shenmue’s development, I felt way more pressure. I remember seeing my timecard showing "XX" hours for a single month.
Note from Switch: The original article did not provide the exact figures; “XX”/“YY” are placeholders for the actual numbers.
Kasahara: If we’re talking about work hours, then it has to be Wada. Like we mentioned earlier, when you looked at his timecard, he’d barely gone home all month. And he wasn’t the kind of guy to fudge the numbers or cheat the system either. His recorded hours for one month were something like "YY" hours.
— (We could only laugh.) I mean, there are only about 720 hours in a month, assuming 24 hours times 30 days.
Hirai: Wada was known as the ‘mainstay’ of the team. He was always present in the office - that’s how dedicated he was. And he wasn’t even a full-time employee! (laughs)
Kasahara: No matter when you showed up, he was always there.
— Mr. Wada, why were you working that much...?
Wada: I was a contract employee, and I originally worked at another company doing various types of development, but I was brought onto Shenmue under contract. And the content of that contract was to “see Shenmue through to release.” So I felt that unless the game shipped, I hadn’t fulfilled my responsibility. I was just doing what I believed was required of me.
To put it simply, I just didn’t go home for two months. (laughs)
Especially toward the end of development, we had about two solid months of debugging, and the team had to operate 24 hours a day. There were times during debugging when the game would crash, and the testers would be stuck, unable to do anything, until morning. That happened several times, but with no programmers around at those hours, the bugs couldn’t be fixed.
Once someone said, “We can’t do any debugging because there’s no programmer here,” I realized I had to be available around the clock. After that, I basically worked 24 hours a day.
 |
| Ryo catches some sleep... unlike some of the developers [Image added by Switch] |
Become a Patron!