Yoshitaka Murayama

• 1. The Tenure Clock

  ›

  Yoshitaka Murayama finished his computer programming studies at the University of Tokyo in the summer of 1992. He walked into Konami's newly opened Tokyo headquarters to submit a job application that same year. The company hired him immediately for quality assurance and menial tasks. Six months later, he was handpicked along with a few others to create an unproduced game for an internal console project. This early console game never saw release, yet it marked the start of his professional journey. Murayama and designer Junko Kawano were assigned to develop games for Sony's PlayStation instead. They chose to revive their role-playing game concept rather than make a baseball or racing title. His preference leaned toward arcade action titles like Taito's Metal Black, but the RPG path became his legacy.

• 2. A Novel As A Pitch

  ›

  In the winter of 1993, Murayama pitched an idea for a role-playing game featuring a large gallery of supporting characters. He knew his boss was around fifty years old and likely unfamiliar with manga series like Fist of the North Star. To illustrate his point effectively, he decided to use the classic Chinese novel Shui Hu Zhuan as the foundation. The pitch succeeded during this short meeting, and the game received the name Suikoden. This Japanese reading translates directly from the source material. Murayama was tasked with creating one hundred eight characters to mirror the outlaws in the Chinese classic. The first Suikoden released in Japan in 1995 to positive reviews despite an initial lackluster market response. Sales eventually increased as word of mouth spread and a cult following formed. Murayama personally responded to every single fan letter that arrived at his desk.

  15

• 3. Depth Over Polygons

  ›

  Square was developing Final Fantasy VII for the PlayStation while Murayama and his team prepared their sequel. They were certain their game would not be able to stand up commercially against Square's massive production. Fan responses prompted them to concentrate on further developing the world and its characters instead of graphics or mechanics. The decision prioritized emotional depth over graphical fidelity against the competition. Suikoden II released in December 1998 to positive reviews and slow but steady sales. The team focused on making the supporting cast memorable rather than relying solely on the protagonist. This approach defined the strategic direction of the project throughout its development cycle. The result was a game that resonated deeply with players who valued character interaction above visual spectacle.

  46

• 4. The Ten Year Exit

  ›

  A third game in the series was developed, but a month before the release of Suikoden III in July 2002, Murayama left Konami. His name was taken out of the credits for the game due to company policy compliance. In an interview with Swedish gaming magazine LEVEL in August 2009, he clarified that he had been exactly ten years since joining the company. His personal goal had always been to stay no longer than ten years before turning freelance. He claimed that after the success of Suikoden II, his superiors were very supportive. He allowed himself to decide freely how the next installment would be made. Soon after leaving Konami, Murayama set up his own company called Blue Moon Studio. That studio went on to develop the video game 10,000 Bullets known as Tsukiyo ni Saraba in Japan.

  123910

• 5. Coding Guilt And Joy

  ›

  Murayama often preferred supporting characters over the main character in works like Saint Seiya and Captain Tsubasa. He believed the protagonist keeps the plot moving forward while supporting characters remain the most memorable elements. Inspired by a line of code in Enix's 1992 RPG Dragon Quest V, he implemented small details to create realism. The priest character dialog slowed down slightly each time the player died and resurrected. This coding technique gave games a greater sense of emotional depth through subtle interactions. Levelling out skill curves pushed players not to use the same characters exclusively. One instance forced the player to use a recently nerfed character only to have it killed moments later. This design choice aimed to give the player a guilty conscience about their choices within the narrative structure.

  78