The Switch 2 emulator scene has five names for one codebase

Open the Lichii README and the first element on the page is a warning. A red heading states that the project has no official website. Below it, a caution block names one anyway: lichii.org. Builds from that domain are not built by the project, the README says, and one has been reported to install malware, with issue #545 as the citation.
Everything else comes after that. The logo, the description, the download instructions. A repository with 9,296 stars as of 15 November 2026 has decided its scarcest asset, the first screen, belongs to a warning about a domain it does not control.
That decision is the story. Switch 2 emulation is being built by people who inherited a decade of other people's code, and the inheritance came with a naming problem nobody has solved.
Five names on one chain
The lineage is not hidden. Lichii's README says it builds on Eglantine, Eden, yuzu and Sudachi, preserving their contributions while this fork works on game compatibility and renderer fixes. It calls itself an independent fork, not an official release of those upstream projects, and states that it is not affiliated with Nintendo.
Eglantine's README describes a free and open source Switch 2 emulator derived from Eden, Yuzu and Sudachi, started by developer Camille LaVey, written in C++ with builds for Windows, Linux, macOS, Android and FreeBSD. It carries 4,168 stars as of the same date and is licensed GPLv3.
Put those two paragraphs next to each other and you get the shape of the scene: yuzu, then Sudachi, then Eden, then Eglantine, then Lichii. Five names, one codebase, and a license that made the whole arrangement possible. GPLv3 permits forking. It expects it.

The paper trail is in the comments
You do not have to trust the prose. Both READMEs open with an HTML comment block that nobody cleaned up. One line reads "SPDX-FileCopyrightText: Copyright 2025 Eden Emulator Project" above a GPL-3.0-or-later identifier. Another reads "SPDX-FileCopyrightText: 2018 yuzu Emulator Project" above GPL-2.0-or-later.
Those headers are the chain, written by a build system rather than a person. A file that passed through Eden and yuzu carries both stamps, and when it lands in Eglantine or Lichii the stamps stay, because deleting them is a licensing problem and editing them is work.
Other seams show the same thing. Lichii's README section on reporting issues links to the Eglantine repository. The README also admits that some inherited documentation and internal build target names still use upstream names, while the GUI target itself is lichii. Renaming a project is a morning. Renaming its history is not.
What a fork inherits, and what it has to earn back
Code moves at the speed of a git clone.
A fork inherits renderers, audio paths, input handling, the accumulated fixes of everyone upstream. Eglantine's donation page is unusually specific about where money goes: Switch consoles to reverse-engineer the hardware, Switch games for testing, hosting, GPUs and CI. That list describes a project paying for access to the thing it emulates. A fork of it starts with the results of that work already in the tree. Lichii's README is also plain that games, keys and firmware are not included, and that only legally obtained content should be used.
What does not travel is the part users actually lean on, which is knowing whose binary they are running. Eglantine keeps its central repository and most of its development on its own git server at git.eden-emu.dev, with mirrors elsewhere, and translations run through Transifex. The parent project has a home it can point at. A fork of a fork of a fork has a GitHub account and a subdomain.
Lichii's 9,296 stars against Eglantine's 4,168 are worth sitting with. The fork is more visible than the project it came from. Stars measure attention, and attention follows whichever repository the last video linked.
Where the compatibility numbers stop
Every emulator README makes a claim about compatibility, and the careful ones spend a paragraph qualifying it. Lichii's does. Compatibility and performance vary by game, hardware and driver. Rendering errors, stutters and crashes remain possible. Passing automated tests does not establish that a game renders correctly. The project makes no universal frame-rate guarantee.
That last sentence is the one to keep. An automated test can prove that a game boots, that a function returns, that a texture upload does not crash. It cannot prove that the frame on your screen looks like the frame on a console.
Reporting has its own edges. Desktop compatibility reporting needs a build containing PR #303, and build 88 does not have it. Nothing uploads automatically. The native v1 reporter does not read or upload logs or files, which is a privacy statement and a limit on what those reports can tell you.
So when a compatibility site shows a green entry for a game you own, read the build number and the hardware beside it. The report is one person's machine on one driver version, submitted by hand.
Your saves live in a folder named after the project
Both projects keep per-project data, and that is the detail that turns a bad download into a bad week.
Lichii uses its own profile: %APPDATA%\lichii on Windows, and directories under $XDG_DATA_HOME, $XDG_CONFIG_HOME and $XDG_CACHE_HOME on Linux and macOS, defaulting to ~/.local/share/lichii, ~/.config/lichii and ~/.cache/lichii. An existing portable user/ directory still takes priority and is not touched by the setup wizard.
On the first non-portable launch the GUI offers to import Eden and other detected profiles. The README is careful here in a way that suggests someone lost data once: back up %APPDATA%\eden first, close the source emulator, then choose Keep Old Data to copy without changing the source. Move keeps a backup of the source until you remove it yourself. Link deliberately shares settings and saves. Existing data at the destination goes to a backup directory instead of being merged, and an interrupted import offers recovery on the next launch. eden-cli refuses to initialize configuration at all, including --help and --version, until you import or explicitly choose Start fresh.
Now put the same folder names in the hands of a repack. Same %APPDATA%\lichii, same saves, same config, written by a binary nobody audited. The directory layout that makes migration convenient is also what a hostile build would target.
How to check a build in under a minute
| Signal | What it actually proves |
|---|---|
| The download sits on the repository's releases page | The file came from the account that controls the repository |
| The domain appears in the README that project maintains | The project acknowledges the domain |
| A compatibility entry on the project's own site | Someone ran that build and filed a report |
| A domain the README never mentions | Nothing at all |
| An icon that matches the official artwork | Nothing at all |
The icon row matters. Lichii ships its logo, icon and library artwork in dist/branding, and generates the Windows, Linux and macOS icon resources with a PowerShell script in tools. Copying a logo takes less effort than writing one line of C++.
Four habits cover most of it. Download from the releases page of the repository, and check that the repository is the one the project's own documentation links to. Use the project's compatibility site for compatibility, which for Lichii is lichii.zortos.me and is described as compatibility reports only. Treat any "official site" the project does not link to as hostile until proven otherwise. Back up your profile directories before you run a build you have not run before.
None of that requires reading source code, only noticing which links the project is willing to own.
There is no registry for emulators. No store, no signing authority, no review queue. What exists is a GitHub account, a releases page, and a README that says which domain is real.
The difference between lichii.zortos.me and lichii.org is that one of them appears in a document controlled by a specific account and the other does not. Anyone can register a domain. Anyone can copy a logo and a green compatibility table. What resists that is a hyperlink the project is willing to put its name behind, which is why Lichii spent its first screen on one, and why the warning reads less like marketing and more like a boundary marker.
Before you double-click anything, the check is one question, and you can answer it without trusting a word of this piece: is the URL you are on the one printed in the README you just read?
Related articles
Six Amateurs, 1,113 Episodes, a Thousand Yuan of Compute an Episode: How an AI Drama Got Hand-Built
The first ten seasons of Armed Into Song run to roughly a thousand episodes and have passed ten billion cumulative views, with six core creators and not one of them film-school trained. Compute runs 1,000–2,000 yuan an episode; a normal shot takes three rolls, a battle twenty-plus, and anything that looks flat is graded a sixty and thrown out.
One server, one AI streamer: inside the code that runs a nightly livestream
open-yoki is the production code behind an AI host who streams nightly on Binance Square, with the persona, voice and money features stripped out. Headless Chrome draws the frame, ffmpeg pushes RTMP, a folder of Markdown decides what she feels and what she posts.
Pinky lets an agent drive your phone, and holds the Send button until you click Allow
Pinky connects any MCP agent to a real iPhone or Android phone and enforces approval in its own gateway rather than in a prompt. Banking apps are invisible, password fields are off limits, and on Android 13 the agent gets a hidden second screen.
ByteDance's SeedRealtime takes two frames a second and decides when to speak
Doubao-Seed-Realtime-1.0 folds camera frames, screen frames and speech into one full-duplex session, at no more than two frames per second. The interesting decisions are the frame rate, the proactive speaking, and the audit reply that ships switched on.