SkyFire Authnet Launcher v1.4.1

SkyFire Launcher 1.4 Authnet

This is the stable Authnet launcher release built from the latest main branch. The installer is self-contained for Windows x64 and does not require a separate .NET installation.

Highlights:

• Adds the optional Authnet login route for clean clients.
• Allows Authnet mode to be disabled in Configuration.
• Embeds the required authentication modules in the launcher.
• Adds account migration support for email login.
• Adds the About menu with version, project links, license, and copyright information.

SHA-256:
8667B0A92704512AFB0286146A9F0C157C917C37029D37BA5B380169F42B6DB4

SkyFire Launcher v1.4.0 - Non Authnet

SkyFire Launcher 1.4 Non Authnet

This release provides the established launcher workflow in a self-contained Windows x64 installer.

What's new:

• Added an About menu with launcher and project information.
• Added the 1.4 Non Authnet product version.
• Added links to the Project SkyFire website and launcher repository.
• Added GNU GPL v3 license information and copyright details.

SHA-256:
615C34A3D0DBF7C480DE1ACC79521E5F069F4724006803620730990BDF9B78F3

SkyFire Authnet Launcher v1.0.6

SkyFire Authnet Launcher v1.0.6

Experimental Battle.net-style authnet launcher for the 5.4.8 build 18414 client. This release is not production ready and requires the matching authnet-enabled server and database update.

Included

• Starts a clean client and redirects authnet traffic to the configured server.
• Applies required endpoint and trust compatibility changes only in process memory.
• Installs the required authentication modules from launcher-embedded resources.
• Keeps the client executable and installation unchanged on disk.
• Leaves email and password entry in the client; credentials are entered only once.
• Preserves compatibility with the existing patched-client login path.

Testing

1. Install SkyFireAuthnetLauncherSetup-1.0.6.msi.
2. Configure the 5.4.8 client directory and server address.
3. Enable the experimental authnet login option.
4. Start the client through the launcher and log in with an email identity.

Existing accounts must be migrated or have their password reset by an operator before authnet login so the native verifier is provisioned.

The MSI is not Authenticode signed. SHA-256: 0DF263BF5D11CE338BE49D1F3A69AED316FB3A33A032B3BBD1E6CAC1646C1DC2.