Eglantine builds
Seventy-eight releases were on the public list. Every mainline release was marked prerelease, so “latest” does not mean stable.
Four names, four meanings
A numbered name such as build-212 is a CI build that received a release. A daily name such as daily-20261106 is the day’s package. A branch name such as branch-nx2-experimental-efb9fb18 is an experimental test snapshot, and it can be newer than the daily. Its publisher says it is not a release and the next branch push replaces it. v0.1.0-rc1 was published on 2026-11-04 with the title “DONT USE”.
The package 9.0.2-av1-mingw-1 is an FFmpeg archive for CI. Its title says it is not an emulator build. I leave it out of download advice.
Numbers skip. Build 167’s notes say builds 159–166 have no release because those numbers were CI run ids. A higher number can also be older code: build 163’s notes say build 163 is older code than build 158. I do not sort “best” by the integer.
build-219 was not among the 78 releases. I do not offer it as a download.
Names people search
build 47 is mainline build-47, published 2026-10-30, titled as a fix for a crash when stopping the emulator.
build 31 is also on the mainline list: build-31, published 2026-10-30, titled as an experimental build. A Lichii history name uses “build 31” as well. I do not merge those into one file.
2.1.0 is not a mainline tag. It belongs to the PokeDinner fork (2.1.0a, 2026-10-31).
v96, v60 and 23.0.1 do not appear in the 78 mainline release names I read. I have no public file to attach to those queries.
| Tag | Kind | Date | Emulator files | Note |
|---|---|---|---|---|
| branch-nx2-experimental-efb9fb18 | branch | 2026-11-07 | 12 | Files attached |
| branch-fix-oot-blackscreen-17ac56ed | branch | 2026-11-06 | 7 | Files attached |
| branch-exp-nx2-welcome-tour-1121-86e84297 | branch | 2026-11-06 | 12 | Files attached |
| 9.0.2-av1-mingw-1 | not-emulator | 2026-11-06 | 0 | Skip — not an emulator package |
| daily-20261106 | daily | 2026-11-06 | 12 | Files attached |
| branch-switchbrew-names-736c1d29 | branch | 2026-11-05 | 12 | Files attached |
| v0.1.0-rc1 | rc | 2026-11-04 | 12 | Files attached |
| daily-20261105 | daily | 2026-11-05 | 12 | Files attached |
| build-212 | numbered | 2026-11-04 | 12 | Files attached |
| build-206 | numbered | 2026-11-04 | 12 | Files attached |
| build-205 | numbered | 2026-11-04 | 12 | Files attached |
| build-204 | numbered | 2026-11-04 | 12 | Files attached |
| build-203 | numbered | 2026-11-04 | 12 | Files attached |
| build-202 | numbered | 2026-11-04 | 12 | Files attached |
| build-196 | numbered | 2026-11-04 | 12 | Files attached |
| build-194 | numbered | 2026-11-04 | 12 | Files attached |
| build-189 | numbered | 2026-11-03 | 12 | Files attached |
| build-188 | numbered | 2026-11-03 | 12 | Files attached |
Questions
Why does my build number not exist?
Some integers were CI run ids and never got a release. Check the release list for the tag, not the gap between numbers.
Is a higher build always newer code?
No. Build 163’s own notes say it is older code than build 158. Read the title before you assume the integer is a timeline.
Should I use v0.1.0-rc1?
The release title says DONT USE. Prefer a later numbered build or daily. Use an experimental branch snapshot only for a specific fix; it is replaced on the next branch push.
Sources
Links from the same publisher count as one source; a community compilation counts as one source even when it contains many reports.
| Source | Status | Checked |
|---|---|---|
| Eglantine releases | Public page · 1 source | 2026-11-07 |
| PokeDinner upstream | Public page · 1 source | 2026-11-07 |