Skip to main content
Back to All Projects
Open Source Verified Architecture

Lichii

Lichii is an open‑source, ultra‑experimental emulator targeting the upcoming Nintendo Switch 2 console. Hosted on GitHub, it’s a proof‑of‑concept effort that dives into the new hardware’s architecture, inviting contributors to explore and expand its early‑stage emulation capabilities and lay groundwork for future compatibility testing.

9,177 Stars 1,482 Forks

Core Technologies & Frameworks

C++

Technical Architecture & Specifications

### Project Overview & Lineage Lichii is an experimental, open-source C++ emulator designed to execute Nintendo Switch and Switch 2 software. Rather than building core execution abstractions from scratch, Lichii branches off a long lineage of modern Nintendo switch emulators. Specifically, it builds upon codebase foundations from Eglantine, Eden, yuzu, and Sudachi. As an independent fork, Lichii concentrates its core engineering efforts on game compatibility patches and targeted renderer fixes. ### Security & Binary Distribution Model A critical operational note for developers and users: Lichii maintains no official website for binary distribution. * The only official domain managed by the project is `lichii.zortos.me`, which serves exclusively as a community compatibility database. * Official binaries are strictly released via the project’s GitHub repository releases page. * Unofficial sites (such as `lichii.org`) are unauthorized and have been flagged for serving malicious binaries. --- ### Architecture: File System & Profile Migration Lichii strictly separates configuration, user data, and cache, adhering to platform-native conventions unless forced into portable mode. #### Directory Layout * Windows Profile Root: `%APPDATA%\lichii` * Linux/macOS (XDG Base Directory Spec): * Data: `$XDG_DATA_HOME/lichii` (defaults to `~/.local/share/lichii`) * Config: `$XDG_CONFIG_HOME/lichii` (defaults to `~/.config/lichii`) * Cache: `$XDG_CACHE_HOME/lichii` (defaults to `~/.cache/lichii`) If a `user/` directory exists directly within the executable root directory, Lichii enables portable mode. Portable mode overrides all environment variables and standard OS paths, bypassing automatic profile imports. #### Profile Import Logic During its initial non-portable GUI execution, Lichii triggers a setup wizard designed to ingest data from existing Eden installations or similar detected legacy environments. The migration engine offers three distinct operational strategies: 1. Keep Old Data: Performs a deep copy of configuration files and save states to the new `%APPDATA%\lichii` target while retaining source directory backups. Existing destination data is backed up to separate folders rather than merged. 2. Move: Transfers data to the Lichii target root while keeping a temporary safety backup at the source location. 3. Link: Creates explicit directory links between the original target and Lichii paths to maintain shared state execution. If an import process breaks mid-transfer, state recovery is offered on the subsequent launch. Note that the command-line interface (`eden-cli`) explicitly hard-blocks configuration initialization until an explicit import or setup step is satisfied. --- ### Setup Guide Lichii does not bundle system keys, firmware, or game dumps. Ensure you have legally dumped system components before setting up the runtime environment. 1. Fetch Binary: Download the archive corresponding to your OS strictly from the official GitHub Releases page. 2. Extract: Fully uncompress the build archive to your preferred working directory. 3. Execution (Windows): ```cmd lichii.exe ``` 4. Profile Setup: If migrating from an existing Eden setup, close the source emulator and back up `%APPDATA%\eden` (Windows) or your Unix data paths. Launch `lichii.exe`, choose Keep Old Data when prompted by the wizard, and verify your save data path structure.
Reviewed by DevTechPulse Editorial Board

All listed blueprints, repositories, and case studies are verified against public documentation and LTS container environments. For inquiries or updates, view our Editorial Policy.