This version should be the most stable one. Unless I find a bug somewhere in the code or the publisher drastically changes their way of game client distribution, there won't be any more updates for the launcher.

All the previous versions have been removed (source code associated with the releases are still available in Tags) because they contain critical bugs.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• The standalone pre-built binaries are currently for 64-bit OSs (Windows and Linux only).
• .NET6, .NET7, .NET8 and .NET9 are side-by-side runtimes, they aren't in-place replacement. Therefore, if the dependent binaries (which you're using) target .NET8, you have to get .NET8 Runtime installed on your system despite the fact that you already have .NET7 Runtime or .NET6 Runtime or .NET9 Runtime installed. It needs the specific major .NET version.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.3.2...1.3.7

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

This version should be the most stable one. Unless I find a bug somewhere in the code or the publisher drastically changes their way of game client distribution, there won't be any more updates for the launcher.

All the previous versions have been removed (source code associated with the releases are still available in Tags) because they contain critical bugs.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• The standalone pre-built binaries are currently for 64-bit OSs (Windows and Linux only).
• .NET6, .NET7, .NET8 and .NET9 are side-by-side runtimes, they aren't in-place replacement. Therefore, if the dependent binaries (which you're using) target .NET8, you have to get .NET8 Runtime installed on your system despite the fact that you already have .NET7 Runtime or .NET6 Runtime or .NET9 Runtime installed. It needs the specific major .NET version.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.3.2...1.3.6

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

Sadly, I can't test whether the launcher is stable or not on Linux, I don't have any real Linux devices. While I think that the launcher should work on Linux just like on Windows, if you encounter a problem like launcher crash without error dialogs, or error dialogs while patching the Snowbreak game client, please look up the issue to see if is already reported, or create a new issue and report the error yourself.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• The standalone pre-built binaries are currently for 64-bit OSs (Windows and Linux only).
• .NET6, .NET7, .NET8 and .NET9 are side-by-side runtimes, they aren't in-place replacement. Therefore, if the dependent binaries (which you're using) target .NET8, you have to get .NET8 Runtime installed on your system despite the fact that you already have .NET7 Runtime or .NET6 Runtime or .NET9 Runtime installed. It needs the specific major .NET version.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.3.2...1.3.3

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

Sadly, I can't test whether the launcher is stable or not on Linux don't have any real Linux devices. While I think that the launcher should work on Linux just like on Windows, if you encounter a problem like launcher crash without error dialogs, or error dialogs while patching the Snowbreak game client, please look up the issue to see if is already reported, or create a new issue and report the error yourself.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• The standalone pre-built binaries are currently for 64-bit OSs (Windows and Linux only).
• .NET6, .NET7, .NET8 and .NET9 are side-by-side runtimes, they aren't in-place replacement. Therefore, if the dependent binaries (which you're using) target .NET8, you have to get .NET8 Runtime installed on your system despite the fact that you already have .NET7 Runtime or .NET6 Runtime or .NET9 Runtime installed. It needs the specific major .NET version.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.3.1...1.3.2

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

Sadly, I can't test on Linux whether the launcher can patch the game client or not as I don't have any Linux devices. While I think that the launcher should work on Linux just like on Windows, if you encounter a problem like launcher crash without error dialogs, or error dialogs while patching the Snowbreak game client, please look up the issue to see if is already reported, or create a new issue and report the error yourself.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs (Windows and Linux only, MacOS is untested).
• .NET6, .NET7 and .NET8 are side-by-side runtimes, they aren't in-place replacement. Therefore, if the launcher's dependent binaries (which you're using) targets .NET8, you have to get .NET8 Runtime installed on your system despite the fact that you already have .NET7 Runtime or .NET6 Runtime installed.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.2.11...1.3.1

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

This is a experimental pre-release for testing the new patching system (which comply with the official launcher's new patching system)

This means that there may be critical errors such as game file corruption (not system file corruption) or launcher crashes.

Sadly, I can't test on Linux whether the launcher can patch the game client or not as I don't have any Linux devices. I think that the launcher will likely crash or encounter errors while patching on Linux.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs (Windows and Linux only, MacOS is untested).
• .NET6, .NET7 and .NET8 are side-by-side runtimes, they aren't in-place replacement. Therefore, if the launcher's dependent binaries (which you're using) targets .NET8, you have to get .NET8 Runtime installed on your system despite the fact that you already have .NET7 Runtime or .NET6 Runtime installed.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.2.11...1.3.0

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs (Windows and Linux only, MacOS is untested).
• .NET6, .NET7 and .NET8 are side-by-side runtimes, they aren't in-place replacement. Therefore, if the launcher's dependent binaries (which you're using) targets .NET8, you have to get .NET8 Runtime installed on your system despite the fact that you already have .NET7 Runtime or .NET6 Runtime installed.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.2.10...1.2.11

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs (Windows and Linux only, MacOS is untested).
• .NET6, .NET7 and .NET8 are side-by-side runtimes, they aren't in-place replacement. Therefore, if the launcher's dependent binaries (which you're using) targets .NET8, you have to get .NET8 Runtime installed on your system despite the fact that you already have .NET7 Runtime or .NET6 Runtime installed.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.2.8...1.2.10

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs (Windows and Linux only, MacOS is untested).
• .NET6, .NET7 and .NET8 are side-by-side runtimes, they aren't in-place replacement. Therefore, if the launcher's dependent binaries (which you're using) targets .NET8, you have to get .NET8 Runtime installed on your system despite the fact that you already have .NET7 Runtime or .NET6 Runtime installed.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.2.8...1.2.9

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs (Windows and Linux only, MacOS is untested).
• .NET6, .NET7 and .NET8 are side-by-side runtimes, they aren't in-place replacement. Therefore, if the launcher's dependent binaries (which you're using) targets .NET8, you have to get .NET8 Runtime installed on your system despite the fact that you already have .NET7 Runtime or .NET6 Runtime installed.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.2.7...1.2.8

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs (Windows and Linux only, MacOS is untested).
• .NET6, .NET7 and .NET8 are side-by-side runtimes, they aren't in-place replacement. Therefore, if the launcher's dependent binaries (which you're using) targets .NET8, you have to get .NET8 Runtime installed on your system despite the fact that you already have .NET7 Runtime or .NET6 Runtime installed.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.2.5...1.2.7

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs (Windows and Linux only, MacOS is untested).
• .NET6, .NET7 and .NET8 are side-by-side runtimes, they aren't in-place replacement. Therefore, if the launcher's dependent binaries (which you're using) targets .NET8, you have to get .NET8 Runtime installed on your system despite the fact that you already have .NET7 Runtime or .NET6 Runtime installed.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.2.5...1.2.6

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs (Windows and Linux only, MacOS is untested).
• .NET6, .NET7 and .NET8 are side-by-side runtimes, they aren't in-place replacement. Therefore, if the launcher's dependent binaries (which you're using) targets .NET8, you have to get .NET8 Runtime installed on your system despite the fact that you already have .NET7 Runtime or .NET6 Runtime installed.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.2.4...1.2.5

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs (Windows and Linux only, MacOS is untested).
• .NET6, .NET7 and .NET8 are side-by-side runtimes, they aren't in-place replacement. Therefore, if the launcher's dependent binaries (which you're using) targets .NET8, you have to get .NET8 Runtime installed on your system despite the fact that you already have .NET7 Runtime or .NET6 Runtime installed.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.2.3...1.2.4

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

This is a re-release packages which contains the rebuilt binaries targeting the official release version of .NET8 instead of the release candidate versions.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs (Windows and Linux only, MacOS is untested).
• .NET6, .NET7 and .NET8 are side-by-side runtimes, they aren't in-place replacement. Therefore, if the launcher's dependent binaries (which you're using) targets .NET8, you have to get .NET8 Runtime installed on your system despite the fact that you already have .NET7 Runtime or .NET6 Runtime installed.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.2.2...1.2.3

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs (Windows and Linux only, MacOS is untested).
• .NET7 and .NET8 are side-by-side runtimes, they aren't in-place replacement.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.2.0...1.2.2

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET8 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET8 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET8 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the system-wide .NET8 Runtime installation up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET8 Runtime separately and the launcher will use the new runtime version, without having to wait for new launcher release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET8 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs (Windows and Linux only, MacOS is untested).
• .NET7 and .NET8 are side-by-side runtimes, they aren't in-place replacement.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.2.0...1.2.1

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET7 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET7 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET7 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the .NET7 Runtime up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET7 runtime indepenently and the launcher will use the new runtime version, without having to wait for new release here.
• In case Windows warns you about security concerns when you run the launcher[^1], please install .NET7 Runtime and use dependent build instead.

For dependent builds, you only need .NET Runtime, NOT .NET Desktop Runtime or ASP.NET Core Runtime.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher should work fine without Administration/Root privileges under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs (Windows and Linux only, MacOS is untested).

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.1.1...1.2.0

[^1]: Windows can warn user about known security holes of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

This is a temporarily build, attempt to workaround the 'File in use by another process' issue and the 'MemoryMappedFile on empty FileStream' issue. If you don't have these issues, you don't have to download this build.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET7 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET7 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the .NET7 Runtime up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET7 runtime indepenently and the launcher will use the new runtime version, without having to wait for new release here.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher works fine without Administration under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs.

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.1.1...1.1.3-pre

[^1]: Windows can warn user about known security issue of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.

Download the zip package (in the assets) and uncompress the package, then run the executable file to use:

• standalone-win64.zip: This zip package contains the standalone binaries to be running on 64-bit Windows OSs.
• dependent-win64.zip: This zip package contains the binaries to be running on 64-bit Windows OSs, requiring .NET7 Runtime installed on the system to run.
• standalone-linux64.zip: This zip package contains the standalone binaries to be running on 64-bit Linux OSs.
• dependent-linux64.zip: This zip package contains the binaries to be running on 64-bit Linux OSs, requiring .NET7 Runtime installed on the system to run.

Which package to download?

It's simple, if you don't want to install the .NET7 Runtime, you should download standalone build. (Personally, I recommend you use dependent one, if possible)

• For standalone build: There's no additional dependencies or anything you need to install to run if you download standalone package. It's all ready to be run.
• For dependent build: Providing more flexible, you can keep the .NET7 Runtime up-to-date and the launcher will also get the benefit. For example[^1], when a security issue is found, the newer runtime version will have it patched, you can just update the .NET7 runtime indepenently and the launcher will use the new runtime version, without having to wait for new release here.

DO NOT run the launcher as Administration (or as root for Linux, via "sudo") unless you fully understand why you need that, the launcher works fine without Administration under normal circumstance.

You can extract to the directory where official launcher is located for easy migration.

Notes:

• The launcher currently has no Self-updating feature. But other features are completed.
• This build is currently for 64-bit OSs (Windows and Linux only, MacOS is untested).

Full Changelog: https://github.com/Leayal/SnowBreakLauncher-Dotnet/compare/1.1.0...1.1.1

[^1]: Windows can warn user about known security issue of running binaries targeting out-dated .NET SDK, to "fix" this, requiring rebuilding the new binaries that targeting newer SDK versions.