Pokémon Legends Z-A landed on Nintendo Switch and Switch 2 in October 2025, and within weeks the emulation scene had a working boot path for it. The catch is that the two emulators most players relied on for years, Yuzu and Ryujinx, no longer exist after Nintendo’s 2024 legal actions shut both down. Their replacements fractured into several forks, and by September 2026 the field has settled into a smaller set of active projects: Eden, the original Citron codebase (now largely dormant), and Citron Neo, a revival fork that picked up Citron’s abandoned commits and started shipping builds again in April 2026, with a fresh nightly dated September 6, 2026. This tutorial walks through setting up Citron Neo specifically to play Pokémon Legends Z-A and Pokémon Scarlet/Violet, from key extraction to save migration to multiplayer trading, using only content you already own.
Why Citron Neo instead of Eden or the original Citron
If you have followed Switch emulation coverage on this site before, you already know Eden is the most actively developed fork overall, with cross-platform builds for Windows, Linux, FreeBSD, Solaris, OpenBSD, and Android, and a self-hosted Git instance the team stood up after GitHub pulled the repository following a Nintendo DMCA notice in March 2026. Eden is a legitimate first choice for most players.
Citron Neo earns a place in this guide for three narrower reasons. First, the original Citron project’s commit activity dropped off sharply after late October 2025, and its last labeled stable build, Release 0.12.25, dates to late December 2025. Second, Citron Neo is explicitly built to pick up exactly where Citron’s development stopped, according to the project’s own changelog notes, and its CI pipeline has published tagged releases and nightly builds continuously since April 27, 2026. Third, Citron Neo keeps Citron’s original interface and configuration layout, which matters if you already have a Citron profile, keys directory, and save structure from 2025 that you don’t want to rebuild from scratch. If you are starting from zero with no prior Yuzu, Ryujinx, or Citron install, Eden is still the safer default. If you already have a Citron setup or specifically want the CI-published nightly cadence Citron Neo has kept up since April 2026, this guide is for you.
One technical detail matters before you go further: Citron, Citron Neo, and Eden all emulate the original Nintendo Switch hardware, not Switch 2. Pokémon Legends Z-A shipped as a cross-generation title, so you need the Switch 1 game dump, not a Switch 2 Edition upgrade pack, for any of these emulators to have a chance of booting it.
What Pokémon Legends Z-A actually changed, and why it stresses emulators harder
Pokémon Legends Z-A moves the Legends sub-series out of the semi-open zones of Legends Arceus and into Lumiose City rendered as a single, continuous, real-time open world rather than a series of loading-screen-separated areas. That structural choice is exactly what makes it harder to emulate than Scarlet and Violet, which — despite their own well-documented performance issues on real hardware — still rely on more conventional zone streaming. A continuous city means the GPU has to keep far more geometry, NPCs, and lighting data resident at once, and it means shader compilation spikes hit constantly as the camera pans across new building facades and street-level detail instead of clustering around discrete loading transitions.
For context on the wider franchise, Bulbapedia’s Legends Z-A entry documents the game’s Mega Evolution-focused battle system and real-time combat, both of which lean on physics and animation blending that older turn-based Pokémon titles never asked an emulator to handle. None of this is a knock on Citron Neo specifically — Eden and every other Yuzu-derived fork face the identical challenge, since they all share the same underlying GPU and CPU emulation approach inherited from the same codebase lineage.
Prerequisites: what you need before you start
Gather everything below before touching the installer. Missing keys or firmware is the single most common reason first-time setups fail.
- A Nintendo Switch console you own, with homebrew access (Atmosphère or equivalent CFW) already configured, used only to dump your own encryption keys and firmware
- A legally purchased copy of Pokémon Legends Z-A and/or Pokémon Scarlet/Violet, either as a cartridge you dump yourself or a digital NSP you own
- Citron Neo build dated September 6, 2026 or newer (tagged release 2026-04-27 is the minimum functional baseline, but later nightlies fix Pokémon-specific shader and audio bugs)
- Windows 10 64-bit or newer, or a modern 64-bit Linux distribution (Citron Neo also ships Android builds, but this guide focuses on desktop)
- A CPU with at least 6 physical cores and AVX2 support (Ryzen 5 5600 / Intel Core i5-12400 class or better recommended for Legends Z-A’s open-world areas)
- A Vulkan-capable GPU — NVIDIA GTX 1060 or AMD RX 580 as an absolute floor, RTX 3060 / RX 6700 XT class or better if you want Lumiose City to stay above 30 fps
- 16 GB of system RAM (8 GB will boot the emulator but you will see swapping and stutter in busy areas)
- An SSD with at least 20 GB free for the game dump, shader cache, and firmware files
- A USB or Bluetooth controller — Citron Neo maps well to Xbox and DualSense-style pads
A legal note before you proceed: dumping keys, firmware, and game files from hardware and cartridges you own is what makes this setup legitimate. Downloading someone else’s keys, firmware, or ROM dumps from a forum or Discord is piracy and unrelated to the process described here.
Step 1: Download Citron Neo
Citron Neo’s binaries are published exclusively through its GitHub CI pipeline and tagged releases, per the project’s own download instructions — there is no separate “official mirror” to trust or distrust, which sidesteps the fake-mirror problem that has plagued Yuzu and Ryujinx clones since 2024. Go to the Citron Neo project site and pick the build matching your OS. Windows users want the “windows-nightly” zip; Linux users can build from source or grab the AppImage where available.
Recommended folder structure (Windows):
C:ToolsCitronNeo
├── citron.exe
├── keys
│ ├── prod.keys
│ └── title.keys
├── firmware
│ └── (extracted firmware .nca files)
├── games
│ └── Pokemon Legends Z-A.nsp
└── shader_cache (created automatically on first launch)Extract the archive to a short, non-cloud-synced path. Citron Neo’s own setup notes flag OneDrive and similar sync folders as a common source of file-lock errors during firmware installation, and the same advice applies if you use Dropbox or Google Drive to sync your Documents folder.
Step 2: Dump your encryption keys
Every Switch emulator in this lineage needs prod.keys and title.keys pulled from your own console — these are unique per-console encryption keys, not something that can be legitimately shared or reused between users. If you already ran Yuzu, Ryujinx, or the original Citron before either shut down, you almost certainly have these files sitting in an old AppData or config folder already, and you can skip straight to Step 3.
If you’re starting fresh, use Lockpick_RCM (or the newer Lockpick fork compatible with recent firmware) from your Switch’s homebrew menu. Boot into RCM mode, launch Lockpick_RCM from Hekate or your CFW’s homebrew launcher, and let it dump keys to the SD card. Copy the resulting prod.keys and title.keys into the keys folder shown in Step 1’s structure.
Reusing keys from a previous emulator install
If you’re migrating from Yuzu or Ryujinx, your keys are typically sitting in one of these locations on Windows:
%APPDATA%yuzukeys
%APPDATA%Ryujinxsystem
%APPDATA%citronkeysCopy both files into Citron Neo’s keys directory rather than moving them, in case you still want the older emulator around for other games.
Step 3: Dump and install Switch firmware
Firmware gives Citron Neo the system modules it needs to boot any game, and Pokémon Legends Z-A specifically requires a reasonably recent firmware version because of features it shares with late-2025 system updates. Dump your firmware using a homebrew tool like hekate’s built-in NAND backup feature or a dedicated firmware-dump homebrew app, which extracts the relevant .nca files from your console’s system partition.
Inside Citron Neo, open Tools → Install Firmware (the exact menu wording may read “Configure → System” on some nightly builds — the feature moved around during Citron’s original development and Citron Neo hasn’t fully standardized menu text yet). Point it at the folder containing your dumped firmware files and let it import. A successful import looks like this in the log console:
[System] Installing firmware...
[System] Found 108 firmware files
[System] Installing NCA 0100000000000816... OK
[System] Installing NCA 0100000000000817... OK
...
[System] Firmware installation complete
[System] Detected firmware version: matches current baselineIf the log stops partway through with a “file in use” or permission error, that’s almost always the cloud-sync issue mentioned in Step 1 — move the folder out of any synced directory and retry.
Step 4: Add your game dumps
Dump Pokémon Legends Z-A and/or Scarlet/Violet from your own cartridge using a dumping homebrew app (NXDumpTool is the standard choice), or locate the NSP files from a digital purchase you’ve backed up yourself. Place the files in the games folder from Step 1, then in Citron Neo go to File → Add Game Directory and point it at that folder. The game list should populate with box art pulled from Nintendo’s title database and a compatibility badge if Citron Neo has crowd-sourced test data for it.
| Pokémon title | Platform target | Citron Neo status (Sept 2026) | Typical bottleneck |
|---|---|---|---|
| Pokémon Scarlet / Violet | Switch 1 | Playable, inherited from mature Yuzu-era code | Shader compilation stutter on area transitions |
| Pokémon Legends: Arceus | Switch 1 | Playable, well-tested since 2022 | Minor frame pacing in snowstorms |
| Pokémon Legends Z-A | Switch 1 (cross-gen) | Boots and runs, early-playable | Lumiose City open-world areas, GPU-bound |
| Pokémon Sword / Shield | Switch 1 | Playable, long-standing compatibility | Wild Area frame drops on weaker GPUs |
Treat the Legends Z-A row as a moving target. Citron Neo’s nightly cadence means compatibility improves week to week; check the project’s changelog before assuming a bug you hit in August is still present in a September build.
Step 5: Configure the graphics backend for Legends Z-A’s open world
Open Emulation → Configure → Graphics and set the API to Vulkan if your GPU supports it — it’s the more stable and generally faster path on both NVIDIA and AMD hardware for this generation of emulator, and the original Citron team, Eden, and Citron Neo all treat it as the primary backend rather than a fallback.
Graphics settings recommended for Legends Z-A:
API: Vulkan
Resolution scaling: 1.0x (native) on first boot
Anisotropic filtering: Automatic
Async shader compilation: Enabled
Use disk shader cache: Enabled
VSync mode: FIFO (avoids screen tearing without adding input lag)Leave resolution scaling at native for your first playthrough of any new area. Legends Z-A’s Lumiose City is the most demanding zone in the game because of NPC density and reflections, and pushing resolution scaling above 1.0x before you’ve confirmed a stable native framerate usually just trades one bottleneck for another. Once you’ve walked through Lumiose without crashes, you can experiment with 1.5x scaling in quieter areas like routes and interiors.
Step 6: First boot and shader cache building
Double-click the game entry to launch it. The first boot after installing a new game or updating Citron Neo will be noticeably choppy — this is expected. The emulator is compiling shaders in real time and caching them to disk so subsequent boots are smoother. Expect the first ten to fifteen minutes of Legends Z-A to stutter every time you enter a new area or menu; this settles down considerably by your second session as the shader cache fills in.
A healthy first-boot log looks roughly like this:
[Loader] Loading Pokemon Legends Z-A...
[Kernel] Booting title 010052E00157C000
[Renderer_Vulkan] Selected physical device: NVIDIA GeForce RTX 3060
[Renderer_Vulkan] Compiling shader batch (1/240)
[Renderer_Vulkan] Compiling shader batch (240/240)
[Audio] Initialized audio backend: cubeb
[Service] am: Application launched successfullyIf the log stalls at a specific shader batch for more than a minute or two, that’s usually a driver issue rather than an emulator bug — see the troubleshooting section below.
Step 7: Migrate saves from Yuzu, Ryujinx, or the original Citron
If you’ve already put hours into Scarlet/Violet or Legends Arceus on a now-defunct emulator, you don’t have to restart. Save files are tied to your title ID and account, not to the specific emulator binary, so copying the save folder across usually works cleanly.
# Windows example: copying a save from Ryujinx to Citron Neo
robocopy "%APPDATA%Ryujinxbisusersave000000000000000<title-id>" ^
"%APPDATA%citronnandusersave000000000000000<title-id>" /E
# Linux example
rsync -av ~/.local/share/Ryujinx/bis/user/save/0000000000000000/<title-id>/
~/.local/share/citron-emu/nand/user/save/0000000000000000/<title-id>/Back up the destination folder before overwriting anything — if the title IDs don’t match exactly (Scarlet and Violet have different IDs from each other, and Legends Z-A has its own separate from Legends Arceus), you’ll end up with an empty save rather than a corrupted one, which is the safer failure mode but still worth avoiding with a backup.
Step 8: Set up controller input
Go to Emulation → Configure → Controls. Citron Neo auto-detects most USB and Bluetooth-paired controllers; select “Pro Controller” as the emulated device type for the best button-mapping compatibility with Pokémon’s menu-heavy interface, since it maps closest to what Legends Z-A and Scarlet/Violet expect for camera controls and quick-menu shortcuts. If you’re using a DualSense or DualShock 4, enable the “Use motion controls” toggle only if you plan to use gyro aiming in Let’s Go-style catching sequences — otherwise leave it off, since some builds report minor input lag when motion processing is active but unused.
Step 9: Configure specifically for Pokémon Scarlet and Violet
Scarlet/Violet run on more mature emulation code than Legends Z-A because they’ve been targets since 2023, so most of the rough edges have already been filed down across the Yuzu-derived forks. A few settings specifically help this title:
- Set CPU accuracy to “Unsafe” (not “Auto”) once you’ve confirmed the game boots cleanly — Scarlet/Violet don’t rely on precise floating-point edge cases the way some older titles do, and the unsafe mode recovers meaningful performance in the open-world Paldea region
- Enable “Ignore missing services” under Debug settings if you see the game hang on the Nintendo logo splash — this is a known workaround for a specific service call Scarlet/Violet make that isn’t fully implemented in every nightly
- If NPCs or Pokémon models flicker or disappear at range, try disabling “Use asynchronous GPU emulation” temporarily — it fixes the flicker at a moderate framerate cost, useful for screenshots or slower-paced exploration
Step 10: Multiplayer and trading emulation
Local wireless and online trading are the hardest features for any Switch emulator to replicate, since they depend on Nintendo’s real network services. Citron Neo supports ad-hoc “room” style multiplayer between two Citron Neo instances on the same network or over the internet via a room code, which is enough to trade and battle with a friend also running Citron Neo — but it does not connect to Nintendo’s actual online infrastructure, so trading with someone on a real Switch or a different emulator generally won’t work.
To set up a trade session: both players go to Multiplayer → Direct Connect, one player hosts and shares their room code, and the other joins using that code. Once connected, launch the same game on both ends and use the game’s normal in-game trade or Link Trade flow exactly as you would on real hardware.
Step 11: Install QoL mods and cheat files
Citron Neo reads cheat files in the same plain-text format the Yuzu/Ryujinx ecosystem standardized on. Community-maintained cheat databases for Pokémon titles are widely shared on GBATemp and similar sites; treat any specific code you download the same way you’d treat any third-party file — verify the source and don’t blindly trust codes that claim to modify save data structure rather than runtime memory.
# Cheat file location
%APPDATA%citronload<title-id>cheatsdefault.txt
# General format used by Citron Neo's cheat engine
[Cheat Name Here]
04000000 XXXXXXXX YYYYYYYYEnable cheats per-game under Properties → Add-Ons → Cheats in the game list, right-click the title, and toggle individual entries on or off. Disable all cheats before trading with another player — mismatched cheat states between two Citron Neo instances are a common cause of desync during a Link Trade session.
Step 12: Verify everything with a clean test run
Before committing hours of playtime, run through this checklist:
- Game boots past the Nintendo logo and reaches the title screen within a reasonable time
- Save file loads correctly if migrated, or a fresh save creates without errors
- Controller inputs register in the options menu test screen
- Frame rate stabilizes to a consistent range after the first few minutes of shader compilation
- Audio plays without crackling or desync from video
If all five check out, you have a working setup. If Legends Z-A specifically still struggles, remember it’s the newest title in this compatibility list and the one most likely to need a Citron Neo nightly update before your specific bug is fixed.
Realistic performance expectations
Nintendo has never published, and never will publish, official performance targets for a Switch game running on unauthorized third-party emulation software, so any framerate figures you see for Citron Neo running Legends Z-A come from community testing shared across GitHub issues, Discord servers, and forums rather than from a controlled benchmark suite. Treat every number in this guide, and every number you see elsewhere, as a directional community estimate rather than a guaranteed result on your specific hardware.
With that caveat, the general pattern reported by players since Legends Z-A gained early boot support is consistent with what you’d expect from a demanding, GPU-bound open-world title on Yuzu-derived emulation code: interiors, battles, and lightly populated routes tend to hold a stable framerate close to the emulator’s target on mid-range hardware, while Lumiose City’s busiest districts are where frame times spike and the GPU becomes the clear bottleneck regardless of CPU headroom. Scarlet and Violet, by contrast, have had three years of cumulative fixes across the Yuzu, Ryujinx, Citron, and Eden lineages, so their performance profile is far more predictable and generally holds up better on the same hardware tier than Legends Z-A currently does.
Practically, this means the single biggest lever you have isn’t a Citron Neo setting at all — it’s patience. A build that struggles with Lumiose City today is very likely to run meaningfully better in a few months as the CI pipeline continues shipping fixes, the same way Scarlet and Violet went from rough to solidly playable across their first year on Yuzu-derived emulators.
Common pitfalls to avoid
- Using a Switch 2 Edition game dump. Citron, Citron Neo, and Eden all target the original Switch hardware. A Switch 2 Edition upgrade pack for Legends Z-A will not boot on any of them.
- Installing firmware and keys inside a cloud-synced folder. OneDrive, Dropbox, and Google Drive can lock files mid-write, producing partial firmware installs that fail silently until you try to boot a game.
- Mixing keys from different console revisions. If you’ve ever restored your Switch from a NAND backup on different hardware, make sure the keys you dump match the console generating the game dumps you’re using.
- Judging performance from the first boot. Shader compilation stutter on a fresh install looks like a serious performance problem but usually resolves after the cache builds — don’t tune graphics settings down based on your very first session.
- Trading between different emulator forks. A Citron Neo player and an Eden player generally cannot trade directly with each other’s multiplayer room systems; both sides need to run the same fork and build family.
- Skipping the firmware version check. Legends Z-A needs a reasonably current firmware baseline. An outdated firmware dump from early 2025 may cause the game to hang at launch even with correct keys.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Game won’t appear in the library after adding the folder | Citron Neo scans folders non-recursively by default in some builds | Point the game directory setting directly at the folder containing the .nsp file, not a parent folder |
| “Keys not found” error on boot | prod.keys or title.keys missing, corrupted, or in the wrong folder | Re-dump keys with Lockpick_RCM and confirm they land in the exact keys directory Citron Neo expects |
| Firmware install hangs partway through | File lock from cloud sync, or antivirus quarantining .nca files | Move the install folder out of any synced directory and add a Windows Defender exclusion for the Citron Neo folder |
| Black screen after the Nintendo logo | Missing or corrupted firmware, or a title-specific service call issue | Reinstall firmware; if the issue persists on Scarlet/Violet specifically, try the “Ignore missing services” debug toggle |
| Severe stutter that never improves after multiple sessions | Shader cache is being cleared on every launch, often from an antivirus real-time scan deleting temp files | Whitelist the shader_cache folder in your antivirus settings |
| Legends Z-A crashes specifically in Lumiose City | Known open-world memory or GPU driver interaction on this specific nightly | Update to the latest Citron Neo nightly; if it persists, lower resolution scaling to 0.75x as a temporary workaround |
| Controller inputs don’t register at all | Emulated controller type mismatch, or a second input driver (like Steam Input) intercepting the device | Close Steam or disable Steam Input for the controller, then re-detect in Citron Neo’s control config |
| Audio crackles or drops out during battles | Audio backend buffer underrun, common on Windows with certain USB audio interfaces | Switch the audio backend from WASAPI to cubeb (or vice versa) in Emulation → Configure → Audio |
| Multiplayer room connects but the trade never completes | Mismatched game version or active cheats on one side | Confirm both players are on the same game patch version and disable all cheats before trading |
Advanced tips for better performance
Once your base setup is stable, a few deeper tweaks help specifically with Legends Z-A’s open-world demands. Pre-building the shader cache by walking through Lumiose City’s main districts once at native resolution, before pushing any upscaling, front-loads the worst of the stutter into a single session rather than spreading it across every future play session. Some players report that capping the frame rate at a fixed 30 instead of letting it float produces a smoother perceived experience than an uncapped frame rate that swings between 25 and 45 — that’s a personal preference worth testing rather than a universal fix.
On the CPU side, if your processor has fewer than eight threads, check whether Citron Neo’s multicore option is enabled under Emulation → Configure → CPU. Multicore emulation splits guest CPU work across host threads and generally helps open-world titles more than linear, corridor-based ones — Legends Z-A benefits more from this setting than, say, a turn-based dungeon crawler would.
Finally, keep an eye on Eden’s release notes even if you’re committed to Citron Neo. Because both projects descend from the same Yuzu-derived codebase, fixes that land in one fork frequently get ported or independently discovered in the other within a few weeks — Citron Neo’s changelog often references specific upstream fixes it pulled in from parallel forks.
Sharing shader caches across a household
If more than one person in your household plays on the same PC, or you’re running Citron Neo across a desktop and a laptop, you can copy a fully-built shader cache folder between installs instead of rebuilding it from scratch every time. Shader caches are tied to your specific GPU driver version and model, though, so copying a cache built on an NVIDIA card onto an AMD system (or even a different NVIDIA driver branch) usually does nothing useful and can occasionally cause visual glitches until the emulator detects the mismatch and rebuilds anyway. Keep a dated backup of your shader_cache folder after any long Legends Z-A session so a bad Citron Neo update doesn’t force you back through the first-boot stutter.
Where the community tracks compatibility
Citron Neo doesn’t run its own centralized compatibility database the way the original Yuzu project once did, so the most current information tends to live across GitHub issue trackers, the project’s own changelog entries, and general emulation references like the Arch Linux emulation wiki, which tracks the broader Switch emulator landscape including package availability across forks. Cross-checking a bug against Eden’s tracker is also worthwhile before assuming it’s unique to Citron Neo — because the two forks share so much lineage, a Legends Z-A crash reported against Eden often describes the exact same underlying issue you’re hitting on Citron Neo, just with different log formatting.
Citron Neo vs Citron vs Eden: a quick reference
| Emulator | Latest build (Sept 2026) | Platforms | Maintenance status |
|---|---|---|---|
| Citron Neo | Nightly, September 6, 2026 (tagged release April 27, 2026) | Windows, Linux, Android | Actively maintained via CI since April 2026 revival |
| Citron (original) | Release 0.12.25 Stable, late December 2025 | Windows, Linux, Android | Commit activity slowed sharply after late October 2025 |
| Eden | v0.2.1, July 2026 | Windows, Linux, FreeBSD, Solaris, OpenBSD, Android | Actively maintained, self-hosted Git after March 2026 DMCA |
None of these three is objectively “best” for every player. Eden has the broadest platform support and the largest active community. Citron Neo has the most direct lineage to the original Citron interface and configuration files, which matters if you’re migrating an existing setup. The original Citron project is worth mentioning mainly for historical context at this point, since its last labeled stable build predates both Legends Z-A’s release and most of the compatibility fixes the other two forks have shipped since.
Building a complete Pokémon emulation setup around Citron Neo
A finished setup looks like this: Citron Neo installed to a short local path, keys and firmware dumped from your own console, your Legends Z-A and Scarlet/Violet dumps organized in a dedicated games folder, saves migrated from whatever emulator you used before, a controller mapped and tested, and cheat files disabled by default so trades don’t desync. From there, the emulator itself mostly gets out of the way — updates roll in as nightlies, and the biggest remaining variable is how quickly Citron Neo’s Lumiose City performance improves relative to Eden’s. If you also play older-generation Pokémon titles, pairing this setup with a 3DS-era emulator like the one covered in our Azahar, Citra, and Lime3DS comparison or a save-editing tool like PKHeX rounds out a single PC into a full-generation Pokémon library spanning handheld cartridges through the newest Switch releases.
If you’d rather compare every option side by side before committing to Citron Neo specifically, our Pokémon emulator rankings walk through the full field system by system, and our handheld hardware comparison is worth a look if you’re wondering whether a dedicated gaming handheld handles Switch-era Pokémon titles better than a desktop PC.
Frequently asked questions
Is Citron Neo legal to use?
The emulator software itself is legal in most jurisdictions, including the United States, because it doesn’t contain Nintendo’s copyrighted code. What makes a setup legal or illegal is how you source your keys, firmware, and game files. Dumping them from hardware and cartridges you personally own is the legitimate path described in this guide; downloading someone else’s dumps is piracy regardless of which emulator you use.
Can Citron Neo run Pokémon Legends Z-A at full speed?
On recommended-tier hardware (RTX 3060 or AMD RX 6700 XT class GPU, 6-8 core CPU), most areas run acceptably, but Lumiose City’s dense open-world sections remain the hardest test for this emulator generation as of September 2026. Expect the game to run well below console-native framerate in the busiest districts on anything less than high-end hardware, and treat Legends Z-A as the least mature title on Citron Neo’s compatibility list compared with Scarlet/Violet or Legends Arceus.
Do I need a different set of keys for each Pokémon game?
No. Your prod.keys and title.keys are tied to your console, not to individual games, and work across every title you add to Citron Neo once installed correctly.
Why won’t my Citron Neo trade with my friend’s Eden install?
Citron Neo’s multiplayer room system is not cross-compatible with Eden’s, since the two forks implement their networking layers independently. Both players need to run the same emulator fork, ideally on close to the same build version, for Link Trade and local wireless features to work reliably.
Is Citron Neo better than Eden specifically for Pokémon games?
Neither has a clear, documented lead specifically for Pokémon compatibility as of September 2026. Eden has more active development resources and broader platform support; Citron Neo has a more direct lineage to Citron’s original codebase and interface. Players migrating from an existing Citron setup will find Citron Neo faster to configure, while new users starting from scratch may prefer Eden’s larger community and documentation base.
What happened to the original Citron project?
The original Citron repository’s commit activity slowed sharply after late October 2025, with its last labeled stable release, 0.12.25, dating to late December 2025. Citron Neo emerged in April 2026 specifically to continue development from that stopping point, publishing tagged releases and CI nightlies since.
Can I play Pokémon Scarlet and Violet with online raids on Citron Neo?
No emulator in this lineage connects to Nintendo’s real online infrastructure, so features that depend on Nintendo’s servers — online Tera Raids, GTS trading with real Switch consoles, and ranked online battles — are not available. Local room-based multiplayer between two players both running Citron Neo is the extent of the networking features currently supported.
How often should I update Citron Neo?
Given Legends Z-A’s early-playable status, checking for a new nightly every week or two is worthwhile while compatibility is actively improving. For Scarlet/Violet and Legends Arceus, which are already well-tested, updating monthly is generally sufficient unless you’re chasing a specific bug fix mentioned in the changelog.
Will a Switch 2 game dump of Legends Z-A work on Citron Neo?
No. Citron Neo, the original Citron, and Eden all emulate the original Nintendo Switch’s architecture, not Switch 2. Pokémon Legends Z-A was built as a cross-generation release with a separate Switch 2 Edition upgrade pack, and that upgrade content specifically targets hardware none of these emulators currently support. You need the base Switch 1 version of the game dumped from a cartridge or purchased digitally for the original console.
My Pokémon models look wrong or textures are missing — is my dump corrupted?
Not necessarily. Missing textures and incorrect models are also a known symptom of an incomplete firmware install or a shader cache that got interrupted mid-build, both far more common than a bad game dump. Before re-dumping the cartridge, try clearing the shader_cache folder for that specific title and letting Citron Neo rebuild it, and double-check the firmware install log from Step 3 completed without errors.