The safest bet for a long-running game series is often the least interesting one: find the thing that worked, put it in a shinier box, and assure everyone that the familiar bits are back. Hidemaro Fujibayashi’s comments on The Legend of Zelda suggest Nintendo’s creative question is pointed in the other direction. Rather than treating Ocarina of Time, Breath of the Wild, or Tears of the Kingdom as templates to be reheated indefinitely, he argues that Zelda should remain a place where developers can pursue ideas that genuinely sound fun.
That does not reveal the next Zelda game, and it should not be read as an announcement of a particular structure, mechanic, setting, platform, or release plan. It does, however, offer a useful glimpse of the design philosophy around a series whose history includes major shifts in how players explore, solve problems, and move through its worlds.
Fujibayashi has directed the Capcom-developed Oracle games and The Minish Cap, then went on to work at Nintendo on Skyward Sword, Breath of the Wild, and Tears of the Kingdom. That makes his point more meaningful than a broad “change is good” slogan. The games named in the discussion are not distant relics to him; they are projects and design legacies close to his own career.
Zelda as a foundation, not a formula
Fujibayashi describes Zelda as a foundation or arena in which a development team can bring promising ideas to life. The distinction matters. A foundation is a base that supports something new. A formula, by contrast, is a prescribed set of steps designed to produce a familiar result.
Franchises need some continuity. A Zelda game without the series’ identity would raise an obvious question: why call it Zelda at all? But Fujibayashi’s framing suggests that continuity does not have to mean copying a previous game’s headline attraction. The recognizable identity can be the invitation to explore, experiment, and interact with a newly imagined set of possibilities—not necessarily one specific map structure, one style of progression, or one signature toolset.
This is an important difference for players reading the series through its most recent successes. Breath of the Wild established an open-world approach, and Tears of the Kingdom expanded on that approach. It is understandable that many people would expect Nintendo to continue along that route. Successful ideas generate expectations, and expectations have a way of arriving at the studio door carrying a clipboard.
Yet a successful design is not automatically an endlessly reusable one. Repeating an idea can make it more polished, but it can also make its surprises predictable. The first encounter with a new design premise has a special force because players must learn what the game permits, what it rewards, and how its systems fit together. Simply reproducing that premise risks preserving the surface while losing the sense of discovery that made it exciting.
“Is that going to be fun?” is the central question Fujibayashi says he raises with younger staff.
Related coverage includes Hidemaro Fujibayashi Says Zelda's Future Should Be Built on New Ideas, Not Recycled Ones.
It is a deceptively plain question, but it carries practical weight. It moves the conversation away from “Has Zelda done this before?” and toward “What will a player actually enjoy doing?” The former can encourage a museum-like approach to a franchise, where every cherished exhibit must be carefully preserved. The latter asks whether a proposed feature earns its place through play.
Why avoiding repetition is harder than it sounds
“Do something new” is easy advice to say and tough advice to use. Newness by itself is not a virtue. A mechanic can be unprecedented and still be awkward, unclear, or simply not enjoyable. Fujibayashi’s reported process pairs the push against recycling with a specific test: does the idea sound fun?
That is where his comments become more concrete. He says discussions with younger staff can include pointing out when an idea has already appeared in games such as Breath of the Wild or Ocarina of Time. The purpose is not presented as banning all similarities. Rather, it is to make sure the team does not feel obliged to draw from an existing storehouse of Zelda ideas.
In development terms, that is a form of creative review. A team examines a proposal, identifies its antecedents, and asks whether it brings something worthwhile beyond what players have already experienced. The desired outcome is not novelty for novelty’s sake. It is a deliberate reason for an idea to exist.
That approach also places unusual value on fresh perspectives. Familiarity with a classic can be useful: it reveals why a design has lasted and which details players remember. But excessive reverence can become a constraint. A team that sees a beloved entry only as a sacred checklist may feel pressure to replicate it rather than investigate the needs of the new project in front of it.
The same tension applies to recent games. When a modern entry reaches a huge audience and becomes many players’ defining Zelda, its influence can be especially powerful. Designers may be tempted to assume that its broadest traits are mandatory in every sequel. Fujibayashi’s remarks push back on that assumption. They leave room for a future game to learn from recent work without being chained to it.
The Ocarina of Time remake detail is revealing
The discussion arrives alongside reported comments about an Ocarina of Time remake. Eiji Aonuma has said that not every developer on that remake team had played the original Nintendo 64 game, and that the remake worked in part as an exercise for staff who had not experienced it to discover what insights it might offer.
That detail can sound surprising, especially because Ocarina of Time occupies an enormous place in the series’ reputation. But it aligns with the broader idea that Zelda history is material to be studied and understood, not a rulebook that every creator must absorb in exactly the same way.
There is a useful creative tension in rebuilding an older game with team members who do not carry identical memories of it. Developers with firsthand affection may recognize the original’s landmarks immediately. Developers approaching it with less personal history may ask different questions about its design, its flow, and the aspects that still communicate clearly. Neither viewpoint automatically produces a better result; the point is that each can reveal something the other overlooks.
It is also important not to stretch this observation further than the available information allows. The reported comments do not tell us how the remake is structured, what changes it makes, which staff worked on which elements, or what conclusions the team reached. They do indicate that engaging with the original was treated as a learning process, rather than merely a matter of copying an established classic.
What players should—and should not—take from this
The clearest takeaway is philosophical: future Zelda projects may be judged internally by whether their ideas are fun and fresh enough to justify themselves, rather than by how faithfully they extend the best-known features of older entries.
That does not mean open worlds are ruled out. Fujibayashi does not say that Nintendo is abandoning the approach used in Breath of the Wild and expanded in Tears of the Kingdom. It also does not mean a future game cannot reuse an idea at all. Game design often builds through iteration, and the remarks describe a probing discussion, not an absolute prohibition.
Instead, the comments resist a simpler claim: that the next Zelda must look like a repeat of either the Nintendo 64 landmark or the recent open-world pair. The series can retain its identity while changing the shape of the experience around that identity.
For players, that is both exciting and inconvenient. Exciting, because it preserves the possibility of surprise. Inconvenient, because it offers no neat checklist of what to expect next. There is no confirmed answer here about world size, dungeon design, playable characters, visual style, or systems. Anyone confidently predicting a direct continuation of a specific format is moving beyond what has been said.
Still, uncertainty is arguably appropriate for Zelda. The series’ appeal has often rested on the feeling that a new journey might ask players to see its world differently. Fujibayashi’s comments suggest the internal goal is to protect that potential—not by pretending past games do not exist, but by refusing to let them become the only imaginable future.
The industry lesson behind the green tunic
There is a broader lesson here for any established game property. Familiarity can reduce risk, but it can also turn an ongoing series into an exercise in feature preservation. The balance between creative experimentation and recognizable identity is a continuing issue throughout games, including debates around access models and long-term design choices such as those explored in the business of free-to-play games and loot boxes.
Zelda’s situation is distinct because the supplied comments focus on game ideas rather than monetization or market strategy. Even so, Fujibayashi’s stance emphasizes a useful principle: a franchise’s past should give creators a platform, not a cage. A revered game can be a source of insight. A recent hit can show what audiences embraced. Neither has to become a compulsory blueprint.
For now, the future of Zelda remains unspecified. The open-world format may evolve again, another structure may emerge, or the next project may combine familiar and unfamiliar elements in a way no one can responsibly predict. What Fujibayashi has made clearer is the standard he wants ideas to meet: they should not survive simply because they appeared in a famous Zelda before. They should survive because the team believes they will be fun.
