FufuLauncher: a third-party Genshin Impact launcher with injection, check-in and account switching

What FufuLauncher solves, and who it is actually for

The official Genshin Impact launcher does one thing: it starts the game and patches it. Everything around that, switching between two accounts, claiming daily check-in rewards, tracking resin, reading wish history, is either done in a browser or not done at all. FufuLauncher collects those tasks into a single desktop application. The README lists account management with QR, password and SMS login, one-click game, community and cloud-game check-ins, a reward calendar, in-app download with diff update and file verification, custom launch parameters, a daily note for resin and commissions, gacha analysis, achievements, backpack inspection and a plugin store.

The target user is someone who runs more than one account, or who plays daily and wants the routine parts automated. The README's own onboarding sequence assumes this: agree to the user agreement, set the game path in Settings, log in to a Miyoushe account on the Account page, then use check-in from the home page. That is a service account, not a game account, which is worth noticing. Check-in and the daily note depend on Miyoushe credentials, while launching and injection work against the local game installation.

The project describes itself as for learning and communication purposes and asks users to support the official game. That framing matters when you decide whether to put it on a machine you care about.

How the pieces fit: launcher, Miyoushe account, injection module

FufuLauncher is a .NET 8 desktop application with a Webview2-based interface. The repository layout shows a solution file, FufuLauncher.sln, alongside three project directories: FufuLauncher/ for the main application, FufuLauncher.Installer/ for installation, and UpdateFufuLauncher/ for the updater. That split is the clearest architectural signal available: updating is a separate executable rather than a self-replacing process, which is a common way to avoid file locks on Windows.

The injection feature is not implemented in this repository. The README points to a separate open source repository, FufuLauncher.UnlockerIsland, for the injection module. So the main launcher ships the hook and the module lives elsewhere. If you care about what injection does to the game process, the code to read is in that second repository, not this one.

Data flows in two directions. Locally, the launcher reads the game installation to detect paths, verify files and apply diff updates, and it reads game data files to populate the backpack, achievements and gacha views. Remotely, it talks to Miyoushe for check-in, the daily note and account login, and to a plugin store with mirror acceleration. The README does not describe the network protocol, the endpoints, or what is stored where. PRIVACY.md exists at the top level, so that is the file to read if credential handling matters to you.

Installing FufuLauncher and getting to a first launch

The README does not give a command-line install procedure. It states the prerequisites: any version of .NET 8.0 or above, plus the Webview2 runtime. Both are Microsoft redistributables, and the README treats them as things you install before running the project. Because the repository contains FufuLauncher.Installer/, the intended path is the installer, and releases are published under version tags such as 1.6.0.3.

Once the prerequisites are in place, the README's own sequence is short. First launch shows a user agreement that must be accepted. Then you set the game path on the Settings page, and the README advises agreeing with the auto-detected path. Then you log in to a Miyoushe account on the Account page, and return to the home page to use check-in. Finally, the main interface has a button to start the game.

The README gives one ordering rule that is easy to get wrong: do not select the game path while running in administrator mode. Select the path first, then run as administrator. Two other features require elevation: switching accounts, and injection. If you launch elevated and then try to point the launcher at your game directory, you are working against the documented flow.

The notes also flag that dynamic video backgrounds are relatively unstable while images work normally. That is a documented limitation, not a bug report, and it is the kind of detail that saves an afternoon if you read it before setting a wallpaper.

Elevation, injection and the cases where this is the wrong tool

The most consequential constraint is administrator privileges. Account switching needs them, injection needs them, and the README warns against selecting the game path while elevated. That combination produces a workflow with a specific order: configure first, elevate second. Anyone who treats the launcher as a normal user-level application will hit failures that look like bugs but are documented behaviour.

Injection is the second constraint, and it is a design choice rather than a defect. The README describes it as an optional injection module for extended in-game customization, and hosts it in a separate repository. Running a third-party process that injects into a live game is a different risk category from running a launcher that only reads files and calls an API. The README does not describe anti-cheat interaction, detection risk, or account consequences. It is silent on all three. If those questions matter to you, the silence is the answer you have to work with, and the honest position is that this is unverified territory.

There is also a scope limit. The launcher is a Windows desktop tool built on Webview2. Nothing in the README or the repository layout suggests a Linux, macOS or headless deployment. If you need check-in automation on a server, this is not the shape of tool you want.

Finally, version currency matters more here than in a typical utility. The README opens by asking users to check whether they are on the latest version before asking questions, which tells you the project expects frequent client-side changes to break older builds.

How FufuLauncher differs from BetterGI

The search data around this project points at BetterGI, so the comparison is worth making explicitly. BetterGI is a separate Genshin Impact automation tool, and the two do not approach the problem the same way. FufuLauncher is organised around the launcher itself: accounts, check-in, downloads, patches, launch parameters, and a set of read-only views into game data such as the backpack, achievements and gacha history. Its automation is narrow and scheduled, meaning check-in and the daily note.

BetterGI is oriented toward in-game automation, running scripted behaviour inside the game rather than managing the installation and the account around it. The practical difference is what you install it for. If your problem is that you have three accounts and forget to check in, FufuLauncher addresses that directly. If your problem is that you want the game played for you, that is a different category of tool, and FufuLauncher's README does not claim to do it.

The two are not mutually exclusive in principle, but they do overlap on injection and on the question of what runs alongside the game process. This article covers only FufuLauncher's side of that overlap.

Maintenance, licence and what upgrading costs you

The repository is not archived, and the last push was on 2026-08-19, the same day as the 1.6.0.3 release. The two prior releases, 1.6.0.2 and 1.6.0.1, landed on 2026-08-13 and 2026-08-12. That is a tight release cadence in the weeks before the last push, which is consistent with active work on the 1.6.0 line. It is also a snapshot: nothing in the repository shows activity after 2026-08-19.

The licence is MIT, which permits use, modification and redistribution with the licence and copyright notice preserved. MIT says nothing about the game's own terms of service, and this project is a third-party client that talks to Miyoushe and injects into the game process. Those are separate questions from the software licence, and the README's own framing, for learning and communication purposes, is the project's position rather than a legal conclusion. If you need a legal opinion about using it with your account, that is a question for a lawyer, not for the licence file.

Upgrade cost is shaped by the prerequisites. .NET 8.0 and Webview2 are external dependencies the launcher does not bundle, so a machine that has never run a .NET desktop application needs both installed before the first launch. The presence of UpdateFufuLauncher/ as a separate project means updates arrive through their own executable rather than through the main binary, which reduces the chance of an update failing because the running application holds a lock on its own files. The README's instruction to keep the latest version installed is the practical maintenance rule: older builds are the first thing the project asks you to rule out when something breaks.

Editorial conclusion

Adopt FufuLauncher if you already juggle several Genshin accounts and want check-in, gacha history and launch parameters in one window, and you are comfortable running a third-party binary with administrator rights. Do not adopt it if you want a launcher that works without elevation, or if you are unwilling to run code that injects into the game process. Before installing, confirm that .NET 8.0 and the Webview2 runtime are present, and read the user agreement the first launch displays.

Frequently asked questions

Official sources

1. Official README
2. Project repository
3. Release notes