The remake, relaunched for modern hardware, is scheduled to launch on Thursday, November 5.
Background and context
Originally released for the Nintendo 64 in 1998, The Legend of Zelda: Ocarina of Time is widely regarded as a landmark in 3D action-adventure design.
For the Switch 2 remake, Nintendo and the internal development team revisited core systems and pacing to balance fidelity to the original with modern expectations.
Eiji Aonuma, long-time series producer, led oversight on the project and spoke about design decisions that shaped the remake.
Why warp points were proposed and ultimately removed
Aonuma explained that the team considered adding warp points to the remake after observing how players navigated the original game.
In the N64 version, players commonly used the forward roll to move quickly across Hyrule Field, a behavior he felt the remake should address.
Drawing on the modern Zelda precedent—The Legend of Zelda: Breath of the Wild, which features numerous fast-travel locations—Aonuma initially asked the team to implement warp points that did not exist in the original.
After testing, however, the team found the warp points changed the player experience in undesirable ways.
Aonuma said that when warp points were enabled, players missed the incidental discoveries that occur while traversing the world and stopping to investigate unexpected sights.
Those unplanned moments of curiosity and discovery, he said, are fundamental to Ocarina of Time’s structure, so the added warp points were removed from the final build.
Developer perspective and launch details
Aonuma acknowledged he was the one who proposed the change but ultimately agreed the warp points “weren’t working” for this remake, and the feature was rolled back.
The decision underscores Nintendo’s emphasis on preserving the original game’s pacing and exploratory mechanics even when updating controls and visuals for Nintendo Switch 2 hardware.
The remake’s November 5 launch marks the latest high-profile return of a classic Zelda title, and Nintendo’s iterative design process—testing new systems and reversing course when they compromise core experiences—remains central to how the company updates legacy IP.