Home Creators Posts Import Register Favorites Logout

Content

Up until that point, most of the project proposals had come from the section heads, who would take the lead in production. However, when a large number of planners—including those of us who had joined the company at the same time—were suddenly hired, it created several times more production lines.

Along with that, multiple consumer lines with completely different distribution models from arcade games began to operate in parallel. Compared to the steady production flow of earlier arcade titles like Section-Z and Trojan, there was now a distinct sense that time itself had begun to move differently—as if the great ship called Capcom had suddenly set sail at full speed.

In the midst of that atmosphere, the company planned an employee training trip to the United States. It was an enormous undertaking that included everyone in the company, though we would go in two separate groups. The first group consisted of the president, key members from each department, and among the newly expanded development teams, the section heads and planners were chosen to accompany them.

Although I had traveled abroad before, this would be my first trip to America. I had long been captivated by Western music and deeply admired its art and culture, so the thought of finally going there filled me with excitement.

Despite the company’s rapid expansion, the perception of consumer games within the organization was still not very favorable at the time. Arcade games were evolving with larger circuit boards and more chips, resulting in increasingly powerful and spectacular titles. By comparison, the Famicom seemed, both technically and graphically, like a regression by several generations.

Typically, arcade projects began from a planner’s original idea, whereas Famicom titles were mostly ports of those arcade games. Naturally, that gave the consumer division an image of being somewhat “lower-tier.”

When the section head said, “If you can make it work on the Disk System, that’s fine,” he approved the change of my project from a puzzle game to an action game. Since it wasn’t a major company-defining project, the approval went smoothly. The main objective, after all, was to develop and release a title for the Disk System.

At first, I felt disheartened when I heard that we’d be making what could only be described as a half-hearted puzzle game—simply because there were no suitable candidates for Famicom Disk titles. But as I examined the Disk System games released by other companies, I began to realize the potential within its limitations, and my excitement slowly returned.

By a twist of fate, I eventually found myself developing an original action game for the consumer line—a rare occurrence at the time.

To be honest, when M.K., who had joined the company at the same time as I did, said he had been “Dumped,” I understood exactly how he felt. When I first received the puzzle game assignment, I couldn’t help but think, “Why me?” My fellow planners from the same intake were working on independent arcade projects, some even developing sequels to Ghosts ’n Goblins. In our own department, Legendary Wings was an original title conceived by a senior planner and another colleague who had joined with us.

Though I had genuinely looked forward to creating consumer games, that initial enthusiasm was starting to waver. But when the new project finally took shape, the passion I had felt at the very beginning came back to life.

When I reread the proposal I had once written as practice, the first thing I noticed was that it was designed for an arcade format. While the ideas and general content could be restructured for a consumer release, there was a critical flaw in the gameplay itself.

The player wielded a giant pair of scissors as a weapon—not only to fight enemies, but to slice through trees and buildings while advancing through the stages. However, having understood the limitations of the Famicom from working on Trojan, I quickly realized that such mechanics were impossible to implement. The exhilarating feeling of charging through the stage, cutting down everything in your path, simply couldn’t be reproduced.

Ironically, the bold and unconventional ideas that had once seemed exciting were now hindered by the hardware’s limitations. My experience designing characters for Trojan meant I knew the Famicom’s specs inside and out, and during the planning stage I was forced to discard idea after idea.

The protagonist—a man with a giant pair of scissors attached to one arm. Why had he become that way? Why was he fighting? Who was the enemy? With the very premise of the main character falling apart, I had to rethink the entire game system from the ground up.

“Maybe I’ll just have to go back to a conventional player character after all…”

Still, I couldn’t bring myself to accept it, and found no effective way to resolve my frustration.

But that wasn’t my only concern. I was still a newcomer—barely a year into the job. Capcom had built its reputation by porting hit arcade titles to the Famicom, and now here I was, making something uncertain, fumbling in the dark. Could such a game really be released as a Capcom product? The thought alone was enough to crush me with pressure.

Would a disk game made by an unknown rookie like me receive the same advertising treatment as our previous titles—magazine spreads, television commercials, promotional support? Looking back on how new employees were usually treated, I couldn’t help but fear my project might simply be neglected and forgotten. That anxiety stayed with me constantly.

Still, when I was first told I’d be developing a consumer title, I literally jumped for joy. As M.K. had said, even if it was seen as “lesser” than the arcade division, even if I was treated as an outsider, to me it was the best place I could be. Back when I worked at a design agency, my job was to make clients’ products look appealing in advertisements. Now, I was part of creating the product itself—a thrilling, almost overwhelming feeling. Yet at the same time, I found myself facing invisible obstacles I couldn’t quite grasp.

* * *

One day, M.K. invited me and two other colleagues who had joined the company at the same time to his place to check out a PC game he’d mentioned before.There, sitting on his desk, was a personal computer—the NEC PC-8801. After a bit of small talk, he inserted a game disk, a five-inch floppy if I recall correctly. The game was Jesus, a space adventure released by ENIX (now SQUARE ENIX CO., LTD.).

It began with a simple visual display and progressed through typed commands. Having grown up with arcade games and, later, real-time character movement on the Famicom, I was struck by how different this was—the slow image rendering, the limited colors, everything.

“Well, it’s not exactly a computer made specifically for games,” M.K. said with a laugh as he tapped the keyboard.

The loading speed from the floppy disk felt incredibly slow—just like what we would soon face with the Famicom Disk System.

Since M.K. had already cleared the game, he watched while we played, occasionally offering hints for the puzzles. He was careful not to spoil too much, though, since we wanted to experience it for ourselves rather than as a reference.

Although we had all started out on the same floor when we first joined, we’d been assigned to different planning rooms since then, so gatherings like this had become rare. Playing together again brought back a warm sense of nostalgia.

I was especially looking forward to spending time with this same group during the upcoming training trip to America. When we first joined, we had struggled with unfamiliar development tools but still enjoyed the challenge. After practicing dot design and getting approval from our superiors, we were finally allowed to join active projects—so we’d all been competing to create characters. Now, with each of us responsible for our own titles, it felt deeply rewarding to be able to talk about our work from new perspectives.

M.K. no longer insisted on sticking to arcade projects and was now busy preparing his next Famicom game.Since he was working with ROM cartridges, his storage capacity was smaller than the arcade boards but allowed for much more freedom than the Disk System.

“If you can make an original game on the Disk System, that’s great, isn’t it?” he joked, half teasing but also clearly a bit envious that my project wasn’t just an arcade port but an original concept.

Jesus was entering its climax. After moving back and forth between the ship’s crew rooms countless times, we finally drove the monster outside the ship—and then had to switch to another disk for the next part.

Because the Famicom Disk System also had slow loading times, it was important to decide carefully when the data should be read during gameplay. Poor timing would force players to constantly swap disks, breaking the flow.

Since it wasn’t a real-time action game, everyone was relaxed, immersed in the story and the mystery. But as we approached the finale, everyone leaned forward, fully focused. The last key pressed was mine.

It was my first experience with an adventure game. It left a different kind of impression from an RPG like Dragon Quest, which had been released just a few months earlier. There were many aspects that could serve as reference points, especially since both were disk-based games.

I realized that even game structure required setups and payoffs, much like in comics or novels. It wasn’t just about moving a story emotionally; even in action games, the way a weapon’s function ties to the narrative, or how a unique stage design connects to earlier gameplay elements, could give players a sense of coherence and immersion.

Perhaps, I thought, these techniques could even help mitigate the slow loading times of the Disk System. If we could present story hints or information during the wait for the next scene—perhaps right before a major enemy appeared—it could turn that delay into part of the experience.

I wasn’t sure what kind of Famicom game M.K. would make next, but knowing his love for film and theater, I had a feeling he’d excel at story-driven adventures like this rather than pure action titles.

* * *

Then, one day, the section head unexpectedly came over to my desk. That alone was unusual, but what he told me was even more surprising.

He said I’d been reassigned from the first group of the U.S. training trip to the second group, which would go later with the rest of the development staff.

At the time, there were three development rooms, each with two planners—except ours, which had one senior planner and two of us who had joined at the same time. Only two planners per room could join the trip, which meant I would be the one left behind.

The sudden decision shook me, but I accepted it as inevitable. After all, both the section head and the other two planners—including my senior and the colleague who had joined with me—were working on arcade projects. It only made sense. Still, I didn’t have the courage to ask why I had been the one excluded.

(Automatic translation by AI)

Files

Comments

Omar

AK-sama, I have a question regarding Rockman. A common magnum revolver pistol holds six bullets. The stage select screen of Rockman 1 features six robot masters, and are arranged in a circular fashion like the six bullets in a revolver cylinder. Furthermore, "Roku" (六) means "six" in the Japanese language. Was the name "Rockman" originally intended to be "Six Man" or imply some inspiration from the cowboy's magnum revolver? Thank you very much for your time!

AK’s Blueprints

In the original design, there were eight boss enemies. However, due to limited data capacity, we had to remove two of the stages. So, the number isn’t related to the shape of a revolver’s cylinder. I’ve always loved rock music. I used to listen to American rock when I was young. The name Rockman comes from “rock ’n’ roll” music, but there’s actually another reason behind the name. In Osamu Tezuka’s manga, there’s a character named Rock — a nihilistic, sharp-edged young man. As someone who admires Tezuka, the name “Rock” has always had a special meaning to me.

Sheacu

Its interesting to see you guys brainstorm your ideas and having to organize them. It makes think that Rockman is mix of an RPG and action game at the same time. Can I ask during your first trip to America, do you remember the difference between Western games and Japanese games?

AK’s Blueprints

This was nearly forty years ago, but the first thing that struck me was the difference in color. In Japan, when the number of available colors increased, we tended to use many intermediate tones to create more natural-looking scenes. However, in America, I felt that impact was considered the most important factor, which led to the use of bold and clearly defined colors. These observations were based on arcade games, but once video games moved to home consoles, developers in every country began to pursue realism. As a result, the differences in color expression gradually disappeared, becoming more a matter of artistic direction than regional style.