TL;DR
The Legend of Zelda: Breath of the Wild (2017) and Tears of the Kingdom (2023) run on Nintendo EPD's proprietary engine plus a modified version of Havok physics, not Unreal or Unity. That boring-sounding choice powers a second, homegrown layer Nintendo calls the chemistry engine. Together they sold 35.76 million (BOTW, by June 2026, the bestselling Zelda ever) and 22.71 million (TOTK, by June 2026, including 10 million in three days) on hardware that peaks at only 197 GFLOPS undocked. BOTW Wikipedia TOTK Wikipedia Switch specs
Most explainers stop at "great physics, very emergent." My argument is sharper: Nintendo used weak hardware as a design filter, split simulation from meaning, and shipped a verb-first sequel. TOTK reuses the same Hyrule map but triples what you can do — Ultrahand, Fuse, Ascend, Recall, Autobuild — instead of building a bigger map. If you are an indie dev, that is the lesson to steal.
The bet in one table
| Question | Zelda answer | What AAA usually does |
|---|---|---|
| Engine | Nintendo EPD proprietary + modified Havok | Unreal Engine 5 |
| Second system | Homegrown chemistry engine (fire, wind, electricity, temperature, material tags) | Scripted triggers |
| Hardware target | Wii U / Switch (Tegra X1, 4 GB LPDDR4, 197 GFLOPS undocked, 393 GFLOPS docked) | PS5 / high-end PC first |
| Map strategy | Reuse Hyrule, add Sky + Depths + construction verbs | New, larger map |
| Prototype | Playable 2D Zelda-like to test physics puzzles first | Vertical slice with final art |
Nintendo EPD led both games under director Hidemaro Fujibayashi and producer Eiji Aonuma after a five-year rethink that started right after Skyward Sword (2011). Monolith Soft, veterans of Xenoblade open worlds, assisted with landscape and topography. BOTW development
What Havok actually does (and does not do)
The final game uses a modified version of the Havok physics engine. That line matters because people over-credit Havok. BOTW development
Havok is middleware for real-time collision detection and rigid-body dynamics, now owned by Microsoft since 2015 and explicitly optimized for Nintendo Switch. Havok's own pitch is telling: it is made to be embedded in countless proprietary engines. Havok software Havok official
In Zelda, Havok handles the dumb, honest work:
- boxes slide, boulders roll, ragdolls tumble
- Ultrahand assemblies hold together or shear apart
- paraglider lift, shield-snowboarding friction, stasis launches conserve momentum
Havok does not decide what fire means. That is the chemistry engine.
The chemistry engine is the real engine
BOTW introduced a consistent physics engine plus a chemistry engine that defines the physical properties of most objects and governs how they interact. BOTW gameplay
Concrete examples from the game:
- metal attracts lightning in thunderstorms — drop a sword near enemies and let the sky do the work
- wood burns, spreads fire, creates updrafts; grass + wind + fire = a flying machine
- cold + heat + food = timed buffs; wooden shields catch arrows but also catch fire
- rain makes cliffs slippery, which quietly nerfs climbing and forces a new plan
My framing, clearly labeled as opinion: Havok simulates, chemistry interprets. Havok says "this box moved." Chemistry says "this box is wooden, wet, electrified, on fire, and uphill from dry grass." That separation is why Zelda feels systemic while many Unreal open worlds feel scripted. Unreal can do all this, but Nintendo built the meaning table first and let Havok do the math.
At GDC 2017 the team called this Change and Constant — Breaking Conventions. They showed the 2D prototype they used to prove physics puzzles were fun before any 3D art existed, and Aonuma recalled walking into a test area to find everything blown away by wind. That bug became a pillar: keep the world legible, keep wind real. BOTW development
Why not Unreal or Unity? The 197-GFLOPS answer
Switch is a tablet: Nvidia Tegra X1, quad-core ARM Cortex-A57 at 1.02 GHz, 256 Maxwell CUDA cores, 4 GB RAM. Docked you get 393 GFLOPS; undocked you get about 197 GFLOPS. Switch hardware
On that budget, photoreal Nanite-style geometry is suicide. Nintendo's trade was:
Gain: a stable sandbox where every object follows the same 10 rules, so players can invent solutions (octo-balloon rafts, mine-cart catapults, log bridges).
Cost: blurry textures, pop-in, frame-rate criticism that followed both games, especially TOTK. Reviewers praised scale and mechanics while flagging frame rate. TOTK reception
Here is my contrarian take: weakness was a filter, not just a limit. Because they could not win on fidelity, they had to win on interaction density. Most AAA open worlds add square kilometers; Nintendo added verbs. TOTK's concepts even started as BOTW DLC ideas that exceeded scope — instead of a new map, they built Ultrahand, Fuse, Ascend, Recall, Autobuild plus Zonai devices (fans, rockets, sleds) and two new layers, sky islands and the Depths. TOTK development
That is a verb-first sequel. Same Hyrule, triple the grammar. I think this is the opposite of industry wisdom, and I think Nintendo is right. Players remember what they did (fused a rocket to a shield to fly), not how many acres they crossed.
Two other unpopular opinions:
Weapon durability is memory management disguised as philosophy. Breakable weapons force rotation. If you could hoard one perfect sword, you would stop experimenting with fire, magnetism, and gravity. Breaking is the garbage collector for creativity.
Loose Ultrahand snapping is intentional bad UX. Strict grid snapping would look cleaner but kill comedy. Wobbly, slightly-off vehicles that collapse hilariously teach statics better than a tutorial. Nintendo preserved failure because failure is searchable — clips of failed mechs sold more copies than trailers.
BOTW vs TOTK: what changed in the stack
BOTW gave you Sheikah Slate powers: remote bombs, Magnesis, Cryonis, Stasis. You could climb nearly anything, glide with the paraglider, cook for buffs, and trade Spirit Orbs for hearts/stamina. BOTW gameplay
TOTK keeps that open-world foundation but replaces Slate powers with five construction verbs: Ultrahand (grab + glue), Fuse (weapon + material), Ascend (swim up through ceilings), Recall (rewind motion), Autobuild (reprint a saved design, spending zonaite if parts are missing). Add Korok seeds, shrines, Lights of Blessing, and Zonai parts, and you get a survival-crafting game inside a Zelda game. TOTK gameplay
Tech consequence nobody talks about: Autobuild is basically version control for physics. It serializes your contraption, then re-materializes it. That only works because every part has clean chemistry tags + Havok constraints. Indie takeaway: if your objects do not have stable IDs and material tags, you cannot do "save my build."
TOTK also shipped enhanced Switch 2 editions in June 2025 for both games, proving the stack scales up when hardware finally arrives. BOTW release TOTK release
What indie devs can steal this weekend
You do not need a Havok license. Use Jolt, Rapier, or even Box2D + a tiny chemistry table.
Prototype in 2D like Nintendo did. One screen, one magnet, one fire tile, one metal box. If it is not fun flat, 3D art will not save it.
Write a 10-row chemistry table before you write quests. Example: wood=flammable, metal=conductive+magnetic, ice=meltable, wind=force. Every puzzle is then a row combination, not a script.
Budget verbs, not acres. One new verb (glue, rewind, ascend) beats 2x map size for clips and retention.
Make breaking generous. Durability, zonaite costs, stamina — all force tradeoffs. Give players Autobuild-style favorites so loss stings less but still teaches.
Keep physics legible at 30 fps. Cap rigid bodies, sleep idle objects, use simple colliders. BOTW's readability (bright outline, clear sound when Ultrahand connects) matters more than accuracy.
Train the same muscles in your browser
You cannot practice Ultrahand without a Switch, but you can practice the thinking: fast building, resource budgeting, and treating physics as a tool.
If you like TOTK's freeform construction, warm up with quick-build duels in BuildNow GG. Its Freebuild island is perfect for drilling 90s, box-peeks, and ramp rushes — the same snap-glue-edit loop as Zonai building, just faster and with shotguns.
For slower, Minecraft-style planning, try Mine Clone. Creative vs Survival forces the same choice TOTK forces with zonaite: infinite imagination versus budgeted gathering, plus day-night triage.
If you want cozy, detailed building with 300+ blocks and furniture, Craft World trains the decorator half of TOTK — layering textures, using vertical space, and rebuilding without penalty.
And for pure emergent messing around — ram zombies on wide roads, hop out to loot, toggle slow-mo for stunts — Sandbox City is the closest browser vibe to BOTW's "no single forced path" Hyrule. Drive to a hotspot, park, finish on foot, reposition by car: that is exactly how I clear BOTW camps with boulders and lightning.
None of these replace Hyrule, but together they build construction speed, material intuition, and a habit of asking "what if I glue this to that?" instead of "where is the intended solution?"
FAQ
Did Zelda use Unreal Engine?
No. Both games use Nintendo EPD proprietary tech plus modified Havok physics. There is no Unreal or Unity in the core loop. BOTW development
What is the chemistry engine?
Nintendo's internal ruleset that gives objects material properties (wood, metal, fire, ice, electricity) and lets them interact consistently, on top of Havok rigid-body simulation. BOTW gameplay
How big were they really?
BOTW: March 3, 2017 (Wii U + Switch launch), 35.76M by June 2026, Game of the Year at The Game Awards 2017 and D.I.C.E. TOTK: May 12, 2023, 10M in 3 days, 22.71M by June 2026. BOTW sales TOTK sales
Why does TOTK reuse the same map?
My read: reusing Hyrule let EPD spend budget on verbs (Ultrahand, Fuse, Ascend, Recall, Autobuild) and vertical layers (sky + Depths) instead of terrain. Familiar geography makes new powers feel stronger because you can compare old vs new routes.
Bottom line
Unreal sells you fidelity. Nintendo EPD + Havok + chemistry sells you consequences. On a 197-GFLOPS handheld, that was not nostalgia — it was arithmetic. Build fewer acres, build more meanings, prototype flat, let wind blow your level away once, and keep the part where players surprise you.
Top comments (0)