Nintendo 3DS

The first problem that all kinds of people involved in making games in 3D encountered and had lots of trouble with is the axes not aligning when two characters go to face each other. But the two of you found a solution when you went to Toei Kyoto Studio Park.

Yeah. I remember something else with regard to Z-targeting. When we were making a prototype of battle targeting, we wanted to make it easy to see which enemy you're targeting, so we made a marker.

Uh-huh.

An upside-down triangle.

Like the one appeared above the targeted opponent's head.

Yeah. But I was a designer, so I didn't want to use such a simple marker. I wanted to make something else, so I came up with a fairy. After all, it was The Legend of Zelda.

So first you went to make a marker, and later you made the fairy?

Right. Usually, if you were to make a fairy, you would make a cute girl, but that wasn't possible with the Nintendo 64 system, so I just made a ball of light with wings.

Uh-huh.

I called it the Fairy Navigation System, took it to Osawa-san, and asked, "How's this?" He immediately said, "Let's name it Navi." Because she navigates! (laughs)

Osawa-san called on his simple naming sense. (laughs)

Navi—from "navigation." (laughs) The Legend of Zelda games have a lot of names that show their origin. Link means to bind together. We give a lot of names that serve as functional symbols.

Functional symbols are important to Miyamoto-san.

I think so. I didn't just name her Navi out of my simple sense for naming. Rather, I thought I should name her that way out of respect for The Legend of Zelda naming tradition.

But when I heard the name Navi from Osawa-san, I was really happy. I had thought of it as a system, but…

Naming it had breathed life into what had been an impersonal marker.

Right. I thought, "This is Navi," and ideas started coming to me one after the other. Like being able to tell by color whether the person you're facing is good or bad, and if Navi talked, she could be an important guide for the story. So naming the system Navi really helped it grow.

Navi also gives strategy tips.

So the text that Osawa-san had to write increased a lot.

(laughs) Yeah. (laughs) The addition of Navi had merits with regard to the script as well. We were able to expand the story around the idea of meeting and saying good-bye to a fairy.

Ahh, I see!

And not only the script, but the game mechanics benefited as well. The first location is Kokiri Forest. The village has lots of trees and lots of people live there, but it was difficult to display them all at once.

The Nintendo 64 system had limitations making it difficult to display many characters at the same time.

I came up with the idea of having each person living there followed around by a fairy. That way, even if we just showed the fairies…

I see. If you see the fairy, you know its owner is there, too.

Right. We solved the problem by having it so that the owner appears when you get close to the fairy.

It also led to the scenario surrounding Link not having a fairy at first.

Which led to the whole idea of meeting and parting from a fairy—in which you start by finding a fairy and in the end you say good-bye.

Hmm, I see.

We didn't determine most of the settings at first, but just made them up as we went.

Yeah. (laughs)

But I think that is an important part of our work.

With regard to that, it is often said that when it comes to making Zelda game, the game mechanics come first and the script later. Osawa-san, thinking up the script was your job, right?

Yes.

For example, was the division into Young Link and Adult Link something you were thinking about from the start?

No, at first there was always Adult Link.

Only Adult Link showed up?

Yes. At first, we were just going to have him in an adult form. If you think about the chanbara element, that only made sense. With a child form, the sword would be small and his reach too short, so he would be at a terrible disadvantage, especially against large enemies.

And it wasn't like you could just make the enemies small.

Right. But partway through development, Miyamoto-san and others on the staff started saying they wanted to see a cute little Link.

That would change the script a lot.

Yes. we thought about how we could have both the child and adult forms appear in the same game and came up with the device of going seven years into the future by drawing the Master Sword and then returning back to his child form when he returns it to the pedestal.

He travels back and forth in an instant.

Yes. That was a scenario we added later.

It's amazing that such a big change didn't cause the whole project to collapse.

(laughs)

Huh? You're all laughing. Does that mean it did sort of collapse? (laughs)

It didn't exactly collapse, but we did have some heated exchanges!

We got into it every day. I would write the script and everyone would point out problems, saying, "This is weird," and "That's impossible." Then I'd come up with a revised script and say, "I changed this. What do you think?" I remember going around showing it to each and everyone to get their okay.

Huh? I don't think you went quite that far, but…did you?

You didn't go quite that far.

Huh? I thought I did, but…

You just feel like you did! (laughs)

Perhaps your memory has been overwritten! (laughs)

(laughs)

Hmm…

Everyone back then was busy with what was right in front of them. When it came about that the Young Link was going to appear, what caused the most trouble for me was the modeling and animation for Link.

The amount you had to make doubled.

Right. My work doubled. I was the one making him, so I was like, "What'm I gonna do?"

When did talk of making Young Link come up?

I think it was about the second year after development started. Do you remember, Iwawaki-san?

Yeah, I think it was about one and a half years before release.

Oh, so that's when it was.