Skip to content
ThreadOut
PabloMK7@Pablomf6 · Aug 18, 2026

Yesterday, a Breath of the Wild demake showed up on the internet. Some 3DS homebrew devs have been looking into this…

10 tweets1 min read♥ 3.7Koriginal

Summary

A Breath of the Wild demake for Nintendo 3DS surfaced online, but analysis by homebrew developers reveals it was likely AI-generated rather than genuinely old, with compilation dates from 2026 and suspicious AI-style logging patterns. The build doesn't work on real hardware due to a missing logo section and faulty GPU commands, though it runs in emulators.

Summarized by ThreadOut AI from the full thread. May miss nuance — read the thread below.

  1. #1

    Yesterday, a Breath of the Wild demake showed up on the internet. Some 3DS homebrew devs have been looking into this and data mining it. I'll dump in this thread the current status and information that we have about this mysterious build. 🧵

    NGT@nintygametube · Aug 17, 2026

    Somehow, someone put Breath of The Wild on 3DS... sure why not. It appears to be some sort of demake. Currently playing it in Azahar. reddit.com/r/3dshomebrew/…

  2. #2

    First of all, the project origin. It seems to have been created using homebrew tools, including devkitARM + citro3D + citro2D. There are even references to the toolchain in the code.

  3. #3

    In fact, we can see from that reference that this project was compiled against newlib 4.6.0, which was released January 23th 2026, and adopted by devkitPro in February 2026.

  4. #4

    This conflicts with the author's claim that this build was sitting in a hard drive of a friend for years. Unless they had a time machine it is just impossible. However, the date on the newlib version doesn't make sense: December 5th 2014. Back then, newlib was still in 2.0.0-ish.

  5. #5

    Currently distributed newlib 4.6.0 builds by devkitpro shows the proper date. Honestly, I'm not sure what to think about this, but I'd trust the 4.6.0 version more than the date.

  6. #6

    This raises the question on whether this demo was vibe coded, and looking at the strings, sadly it looks like it... There are em-dashes used as log output strings, something that AI agents likes to do.

  7. #7

    I think this lines up with why the author lied and claimed that the build came from the hard drive of a friend and that it was made years ago, to try to hide the fact that the build was vibe coded.

  8. #8

    Putting that aside, let's talk about why the build does not work on real hardware. The first issue is that the application file was not built correctly, it has a missing logo section in the exefs. Adding back the logo section allows it to boot on real n3ds consoles.

  9. #9

    But don't get hyped up, just after selecting new game the console freezes, due to the build submitting a faulty GPU command list, which causes a GPU crash. Emulators are more permissive here, so it works there. Further research and fixing is needed to make it bootable on real HW.

  10. #10

    Another minor detail, taking a look at the RomFS it shows that it was created on MacOS, due to the big amount of hidden files.