Date: October 18th, 2026 8:55 PM
Author: cowgod
Couldn’t make this stuff up.
The best material comes from former Sega executives and developers who worked with him directly.
1. The time Naka went ballistic because Sega wanted mature games
Mike Fischer — Sega of America executive, May 2026 interview
Around 2002–2003, Sega was transitioning into a third-party publisher. Fischer was sent to Japan by Peter Moore to explain what was happening in the American market.
He delivered a presentation sometimes called the Gamer's Manifesto, emphasizing three developments:
American gamers were getting older, and M-rated games were increasingly important.
Multiplayer features were becoming valuable for retaining customers.
Short arcade-style games were vulnerable to used-game trade-ins and resale.
Fischer wasn't demanding that Sega abandon its identity. He was explaining that its products were drifting away from American consumer preferences.
According to Fischer, Naka exploded in anger, accusing him of wanting Sega to produce pornographic games.
Fischer described Naka shouting:
"How many games have you made? How many hits have you delivered?"
He also claimed that Naka was so furious that saliva was foaming at the corners of his mouth.
The remarkable part is that Fischer identified Toshihiro Nagoshi as someone more receptive to the presentation. Nagoshi subsequently developed Yakuza, although Fischer explicitly said he wasn't claiming credit for influencing that game's creation.
Source: Mike Fischer's original Sega-16 interview.
2. Naka allegedly wanted to name Billy Hatcher something obscene
Mike Fischer — same interview
This might be even funnier.
During the development of Billy Hatcher and the Giant Egg, Fischer recalled that Naka initially wanted a title along the lines of Giant Eggs.
The American marketing people objected, explaining that laying an egg in English could imply failure.
The American team proposed Billy Hatcher, identifying the actual protagonist. Naka disliked that too, according to Fischer.
Then, during a visit to America, Naka supposedly suggested another title based on the fact that a rooster could be called a cock:
Giant Cock.
Fischer insisted that two other witnesses could corroborate the incident. It's his recollection, rather than an independently verified transcript of the meeting.
After telling that story, Fischer called Naka:
"The most miserable person I have ever worked with"
And said his opinion extended beyond the games industry to everyone he'd worked with in his life.
The Absolute State of Sega Marketing, 2003.
3. He allegedly demanded an all-Japanese Sonic 3 team behind locked doors
Craig Stitt — Sonic 2 artist, 2001 and 2025 interviews
This one is especially revealing because Stitt says he personally lost an opportunity because of Naka's demands.
After Sonic 2, STI boss Roger Hector told Stitt that he would become a lead artist on Sonic 3.
But according to Stitt, Naka refused to continue unless Sega gave him an exclusively Japanese development team, a separate office, and separate access cards.
The result: Sonic 3 was developed in offices across the hall that the American developers couldn't access.
Stitt recalled that Naka repeatedly threatened to quit whenever management resisted him.
In his 2025 interview, Stitt described Naka as a dick who disliked working with Americans. By contrast, he spoke warmly about Hirokazu Yasuhara and Yasushi Yamaguchi, the other Japanese developers.
In fact, he said that if Yasuhara or Mark Cerny contacted him about returning to game development, he'd agree.
Naka? Absolutely not.
Sources: Craig Stitt's 2025 interview and his 2001 interview.
4. He effectively terminated Sega's Japanese-American development experiment
Peter Morawiec — Sonic Spinball and Comix Zone designer, 2007 interview
Mark Cerny founded Sega Technical Institute partly to combine Japanese technical expertise with emerging American development talent.
The idea was that the Japanese veterans would mentor and collaborate with American employees.
After Sonic 2, according to Morawiec, Naka effectively ended that experiment.
Morawiec attributed the conflict to Naka's sense of ownership over Sonic, perfectionism, and dissatisfaction with the American team's skills and working practices.
He also acknowledged that many American hires were inexperienced compared with the accomplished Japanese programmers and artists.
This is an important qualification: Morawiec wasn't simply portraying Naka as irrational. He recognized genuine technical disparities and production pressures.
But the consequence was that STI's American and Japanese developers increasingly operated as separate teams.
Cerny's grand plan for transferring Japanese game-development expertise to America had run into one extremely uncompromising programmer.
5. He allegedly helped kill Sonic X-treme by withholding the NiGHTS engine
Mike Wallis — Sonic X-treme producer, 2002 interview; disputed by Naka
Sega of America desperately needed a flagship 3D Sonic game for Saturn.
Development was chaotic and badly behind schedule. Producer Mike Wallis believed his team could save time by using Sonic Team's NiGHTS into Dreams engine.
Bernie Stolar arranged access to the technology, and the American developers began familiarizing themselves with the tools.
According to Wallis, Naka found out and objected so forcefully that he threatened to resign if the Americans were allowed to continue using it.
Sega subsequently withdrew access.
The team lost precious development time, and the game was eventually canceled.
But there's a significant dispute here. In 2022, Naka denied the story, arguing that the NiGHTS engine was undocumented assembly code and couldn't practically be reused by a C-based development team. He suggested that the developers were blaming him for their own failure.
And Sonic X-treme had serious technical and organizational problems independent of the engine dispute.
So Wallis's account is firsthand testimony about the project, but Naka's alleged ultimatum isn't an established, undisputed fact.
Sources: Mike Wallis interview and Naka's 2022 response.
6. The Dreamcast project allegedly destroyed by a conversation Naka thought nobody understood
Mark Subotnick — Sega producer, 2021 interview
This might be the most damaging account of all.
Sega of America was developing Geist Force, a Dreamcast rail shooter inspired by Star Fox.
According to producer Mark Subotnick, the project was progressing reasonably well when Naka visited the studio with his team.
The American developers had created proprietary technology that impressed the visitors.
Subotnick alleges Naka began speaking Japanese, apparently assuming nobody on the American team could understand him.
Unfortunately for Naka, several developers spoke fluent Japanese.
According to Subotnick, Naka discussed taking portions of the project's technology for Sonic, then dismissing almost the entire development team after the game shipped, except for one engineer who could support the technology.
The engineers heard the conversation.
Five key engineers subsequently left the project.
Subotnick said replacing them would have required months of recruiting and training, on top of an already expensive development budget. The project was canceled.
This is Subotnick's account; I haven't found independent confirmation that Naka actually had an approved plan to fire those employees.
But if his recollection is accurate, the irony is enormous: a technical leader allegedly destroyed an engineering team by discussing its future in a language he assumed its members didn't speak.
Source: Mark Subotnick's account and interview excerpts.
7. He publicly erased Sonic's character designer from a photograph
July 2022 — documented public incident
This isn't merely a former employee's recollection.
In July 2022, Naka celebrated the anniversary of NiGHTS into Dreams by publishing an old photograph of the development team.
Except someone was conspicuously blacked out.
That person was Naoto Ohshima, Sonic's original character designer.
Naka subsequently referenced the breakdown of his relationship with Ohshima during Balan Wonderworld development.
Fischer also recalled an earlier incident at an Xbox One event where Naka allegedly refused to sit in the same row as Ohshima because of a dispute over credit for Sonic.
8. Even Square Enix eventually removed him from directing Balan Wonderworld
2020–2022 — Naka's own public account of his dismissal and lawsuit
Naka reunited with Ohshima on
Balan Wonderworld
.
Six months before release, Square Enix removed Naka from the director position.
Naka later sued Square Enix and publicly complained about its handling of the project.
Naka claimed that the dispute arose partly because he objected to unresolved bugs and a promotional music arrangement.
He also described court documents indicating that his comments to developer Arzest had damaged the working relationship. The decision to remove him involved multiple senior personnel, including HR.
Naka maintained that he was simply fighting to improve the product. The internal complaints weren't publicly adjudicated in the sources I found.
It's another case of Naka's uncompromising approach to game development colliding with the organization employing him.
9. The insider-trading conviction
Unlike the workplace anecdotes, this is a court-established matter.
In July 2023, a Tokyo court convicted Naka of insider trading involving shares purchased using nonpublic information obtained during his time at Square Enix.
He received a two-and-a-half-year prison sentence, suspended for four years, along with financial penalties totaling approximately ¥172 million.
Game Informer
This doesn't substantiate the workplace allegations, but it is part of his later professional history.
What's particularly interesting about the pattern
Three people from substantially different phases of Naka's career independently described recurring problems:
Source
Era
Principal complaint
Craig Stitt
1992–1994
Exclusion of American developers and resignation threats
Mike Wallis
1996
Refusal to share technology, disputed
Mark Subotnick
1998
Alleged plan to appropriate technology and eliminate jobs
Mike Fischer
Early 2000s
Hostility to market feedback and disputes over creative credit
Naka's own account
2020–2022
Breakdown with project partners and removal from directorship
There's a distinction worth preserving, though.
Mark Cerny consistently acknowledged that Naka was an extraordinary programmer. In one interview, Cerny recalled Naka constructing a 3D tunnel-chase engine on the Master System almost spontaneously, while Cerny was away on holiday.
And Cerny described Sega's mistreatment of Naka after the original Sonic: comparatively low compensation, harsh criticism, and little recognition of how valuable his contribution had been.
Time Extension
That helps explain why Naka might have become highly protective of his work, without excusing the behavior others alleged.
What makes the history fascinating is the contrast with Hirokazu Yasuhara. Former colleagues repeatedly spoke warmly about Yasuhara while describing Naka as extremely difficult. And Yasuhara was responsible for much of the actual level design that made the Genesis Sonic games so satisfying.
The technical brilliance was real. So, apparently, was the inability to get along with people.
The Absolute State of Sega Internal Development.
(http://www.autoadmit.com/thread.php?thread_id=5913832&forum_id=2...id.#50196001)