A new launcher is in the works that I am a large contributor to. Unfortunately this means I cannot maintain GrassClipper much - if at all - since I am busy on the new one. This is good news, however, because this new launcher is already much more stable and contains many additional features. If you are having too much trouble with GrassClipper, I recommend you wait until the new launcher.
Experimental Grasscutter launcher for easily switching between Official and Private servers
Download Here! (Supports Windows 8+)
*Note: some translations are outdated, so if random English text appears or an option seems misleading, this is why. If you notice an issue like this, feel free to make a pull request!
GrassClipper.exe, install the proxy server, and set your game folder!
npm install -g @neutralinojs/neu
npm run dev
npm run build
install.cmdwhen opening for the first time
C:/Program Files) and warn
Below are some scenarios you may encounter and their solutions.
If you having trouble installing the proxy server, you can also install it manually. To do so:
extin the GrassClipper folder.
mitmdump.exeand allow it to run for a few seconds to generate the certificate
certutil -addstore root "%USERPROFILE%\.mitmproxy\mitmproxy-ca-cert.cer"
Encountering a white screen? Ensure WebView2 is installed
You may also want to run this command as administrator:
CheckNetIsolation.exe LoopbackExempt -a -n="Microsoft.Win32WebViewHost_cw5n1h2txyewy"
If you have Chinese characters in your file path, this may crash it too! I am working on a fix.
You can also try running in Windows 8 compatitbility mode.
If all else fails, you can run GrassClipper in
browser mode. To do so:
Targetbox, at the very end, add
chromeonly works if you have Chrome installed, and will create a Chrome window
browerwill, you guessed it, open GrassClipper in your default browser
You may be using the wrong port, ensure your port in GrassClipper is either 443 or nothing (not 0, but literally nothing)
If you are running a local server, ensure the local server is running. Otherwise, ensure the server you are connecting to is actually running.
If you are able, use the development branch of Grasscutter. It is known to work better with GrassClipper.
If you are still getting an error 502 when attempting to log in to your own server, open your Grasscutter config and add the following to the
YOUR_PORT is the same port you use as the
Port value already. This will probably be 443.
Ensure you have the correct
keystore.p12 file that comes with your branch (
development). Also ensure the password is set properly in Grasscutters
config.json (blank for
stable, "123456" for
If you are getting infinite CMD windows for any of the scripts (such as the proxy installation, or private server start), ensure you have UAC (user access control) set to any option that requires asking. Ensure your user account can open things as Admin.
Discord/YouTube (plus surely some others) does not seem to be a fan of the proxy server. You may need to disable it by either closing mitmdump or by disabling your proxy in the Windows proxy settings.
The launcher most likely did not close correctly, and was unable to clean your proxy settings back to what they were. Disable your proxy in the Windows proxy settings.
Thank you to everyone who has provided translations! <3