Home Creators Posts Import Register Favorites Logout

Content

The Famicom version of Trojan was Capcom’s first internally developed consumer title. At that time, my desk and F’s—he was in charge of backgrounds—were still on the same floor as the arcade team, working side by side as the fledgling consumer team.

My main task was creating sprites—the moving pixel characters. Since arcade characters differed in both size and number of colors, they couldn’t simply be dropped into the Famicom version. Even if they were pixel art, they had to be completely redone from scratch. Having worked on arcade characters before, I first assumed the reduced color count would make things easier—but that was a mistake.

With arcade hardware, the abundance of colors allowed for shading, giving characters depth and detail in clothing or limbs. On the nearly monochrome Famicom, that simply wasn’t possible. The most troublesome issue was pixel jaggies. Digital images, even today, are all built from dots, but with many colors you can hide those rough edges.

Compared to arcade, the Famicom offered far fewer colors and character slots, making it difficult to achieve the designs I envisioned. Still, drawing out figures and objects in careful detail with just a handful of shades felt almost exactly like the pixel practice I’d done when I first joined the company.

Outlines in pixel art inevitably produce jagged edges. Back in training, we learned a technique to smooth them out by gradually darkening colors into a gradient, making the line appear cleaner. I often got scolded with remarks like, “Your outlines are too blurry.”

“I guess I was leaning too much on gradients.”

Sure enough, gradients could erase jaggies and smooth out lines, but overdo it and the original shape blurred or swelled larger than intended. Looking back, I realized I was finally learning the essence of pixel design.

But now, on the Famicom, there was no such option. No matter how rough the jaggies looked, I couldn’t fix them with gradients. Shapes had to be expressed directly, with only a single flat color. So I worked out my own methods, creating sprites one by one.

Project scheduling was technically my responsibility, but the actual pace of production was dictated by the lead programmer. F and I kept making graphics nonstop, trying to ensure the lead’s work didn’t stall.

In the meantime, I came up with several new ideas unique to the consumer version. The play environment was different: arcade games demanded coins and short bursts of play, while the Famicom allowed endless hours at home. To reflect that, I added new features—rooms beneath manholes where hidden items could be found, and even original enemies placed before the final boss—ways to differentiate the Famicom version from arcade.

As a planner, I felt every day that working on the Famicom version of Trojan was a valuable experience. Of course, I dreamed of designing my own game project from scratch someday, but since this was a port, there was no need for the difficult process of building a plan or structure from zero. I could learn how to produce a game by working from an existing model.

At the desk right next to mine, characters from the arcade game Legendary Wings were displayed on screen. Those sprites, built with many colors, looked far more lavish compared to our consumer graphics.

Staring absently at those arcade sprites, I suddenly remembered what M.K. had once said to me:“Are you really okay with being dumped onto consumer games?”

I hadn’t thought that way at all—but his words still surfaced at times, catching me off guard. Sometimes it was triggered by a colleague’s offhand comment or even just a glance. Even if I knew it was just my imagination, when I spoke with arcade staff, I felt an unspoken sense of pity in the air.

Eventually, the differences between arcade and Famicom sprite production grew so wide that I stopped even getting advice from my seniors. The methods were just too different—the scales, the palettes. I had no choice but to figure it out myself.

Each planning office had its own small group of consumer staff, but they were on different floors, so we rarely interacted. Little by little, I found myself isolated within the room.

Even so, the Famicom version of Trojan was finally finished and delivered for ROM production. “ROM submission” meant bringing the completed game data, burned into ROM chips, to Nintendo’s designated factories. At that time, so many Famicom games were in production nationwide that even after delivery, cartridge manufacturing still took three to four months.

In the end, most of the critical parts were handled by the lead programmer, leaving me slightly unsatisfied as a planner—but still, it had been an invaluable learning experience.

Meanwhile, the Famicom craze only grew stronger, becoming a full-blown social phenomenon. Not just veteran game makers like Capcom, but companies from all sorts of industries began jumping into the consumer market. Those with popular children’s anime or manga IPs churned out hit after hit.

* * *

One day, after things had finally settled down, the department head called me in. My next assignment, he said, would be to make a game for the Famicom Disk System.

The Disk System had been released just before we started on Trojan, and Nintendo was pushing it hard as their new add-on hardware.

“What, the Disk System?” I couldn’t help blurting out—not because I meant to complain, but because I was genuinely surprised.

From the developer’s side, the Disk System was considered a hassle. The biggest worry was load speed. As I mentioned before, when switching stages you had to reload graphics and music. With a cartridge, the ROM chips could provide data instantly, but with the Disk System, data had to be read from a proprietary magnetic disk card—and it was painfully slow.

Even today, some games take time to load data, but for players back then—accustomed to the instant response of cartridges—the load times felt interminable.

There was another issue: there wasn’t an arcade game lined up for porting. Capcom’s consumer releases were usually arcade conversions, but Legendary Wings, the next candidate, wasn’t finished yet. Still, it had already been decided we had to make something for the Disk System.

“Well, maybe you could just whip up a simple puzzle game.”

The department head understood the difficulty of porting from arcade, but he still floated this as a way to at least get a disk title made.

I was caught off guard. The whole thing felt like a stopgap project, a way to fill time. I had no idea what larger sales plans the company had, but I certainly hadn’t expected this.

Capcom’s strength was in porting its powerful arcade games to home consoles. There had never been a puzzle game under the Capcom brand. It was hard to imagine a company with such a “hardcore” image suddenly putting one out.

Back at my desk, I gazed absently at everyone working around me. Just recently I had been just as busy, running myself ragged with deadlines, creating Famicom sprites for the first time. Those hectic days had been exhausting but fulfilling.

Legendary Wings was nearly complete. I had naturally assumed my next assignment would be to port that game. I’d even been checking its memory size and considering how its characters might be adapted.

Now, watching the arcade staff working through their final crunch, their weary expressions seemed oddly nostalgic—and even enviable.

“…Looks like M.K. was right all along.”

Between scheduling issues and memory limits, I realized more and more arcade titles might not be portable to the Famicom. Maybe M.K.’s instincts had been sharper than I admitted—but until this moment, I hadn’t really felt it.

Trying to shake off my unease, I started cleaning up the leftover notes and reference materials from my last assignment.

“A puzzle game, huh…”

I muttered, then laughed at the absurdity of it. The idea left me uneasy, as if everything I’d done up until now might suddenly be wiped away.

“Maybe the department head had his eye on you…”

M.K.’s words still wouldn’t leave my head.

As I lifted a stack of books and files from my desk, a small box slipped out and thudded to the floor. It was a Famicom Disk System game I’d bought recently and forgotten about.

“Wait… this is—”

Castlevania (Konami). Still unopened. I had picked it up because its character sizes were similar to Trojan, and I thought its color use and stage layouts might be useful references.

I tore open the package, rushed into the meeting room, and slid the disk card into the Disk System.

The dark atmosphere and game design reminded me of Ghosts ’n Goblins. The backgrounds, the player character, the sound—everything was crafted with incredible care. Sure, the load times were there, but aside from that, it was flawless real-time action.

“See? It can be done. Even on the Disk System, it can be done!”

I shouted to myself alone in the meeting room.

Then I suddenly remembered something and ran back to my desk. Everyone around looked at me with curiosity.

When I returned to my desk, I pulled out a file that had been tucked away at the very bottom of the drawer.

It was that very planning document, never shown to anyone, that I had rewritten as practice.

(Automatic translation by AI)

Files

Comments

Sheacu

May I ask you. Do you and your team study other video games and how do they work or everything done was an entirely new concept?

AK’s Blueprints

Which game are you referring to? The NES version of Trojan was a port of the arcade game. Since most of the settings were carried over as they were, there was no need for an entirely new concept.

Sheacu

I was thinking about Super Mario Bros. I watched a documentary where Shigeru Miyamoto had to overcome limitations of the Famicom. I was asking because I notice some parallels between the two works.

AK’s Blueprints

At that time, I was still inexperienced, and simply understanding the NES hardware specifications was all I could manage. Later, through the development of Mega Man, I gradually acquired various techniques and theoretical knowledge. The one thing that might have set me apart from others was that I didn’t see hardware limitations as something negative. Many people believed that having more memory and a more powerful CPU was what allowed their ideas to come to life. But for me, the real challenge—and the fun—was in seeing how interesting a game I could create within the constraints I was given. Perhaps it was this mindset that allowed Mega Man 2 to evolve so significantly.

Sheacu

I see. Thank you for the advice.