Native Windows and Linux GUI installer and hotfix utility for the private SPT 4.1.3 friends pack.
Important: Release 1.1.2 omitted Avalonia's native renderer libraries and can exit before opening its window. Download 1.1.9 or newer manually. Earlier Linux builds had native-runtime, UI-thread, EFT-validation, automatic-relaunch, progress-display, completed-download verification, or Windows-separator extraction defects.
Download the ZIP for your operating system from this repository's Releases page and extract it before running:
- Windows x64:
SPT413-Phetzy-Updater.exe - Linux x64:
SPT413-Phetzy-Updater.Linux
On Linux, make the downloaded file executable if the archive tool did not preserve its mode:
chmod +x SPT413-Phetzy-Updater.Linux
./SPT413-Phetzy-Updater.LinuxThe official release embeds access to the private pack. No separate configuration or AWS credentials are required.
Release builds run native-runtime smoke checks on Windows and Linux. They also verify that the embedded private channel can read its manifest and the S3-backed bundle endpoint before GitHub publishes the assets.
The Windows release gate runs the complete unit suite on Windows, publishes the self-contained executable, checks its file version, extracts it from a ZIP, exercises native rendering, managed mod verification, self-update extraction, and self-update process handoff, then confirms the packaged GUI remains running after startup.
The updater checks the latest GitHub release when it opens. It selects the Windows or Linux asset automatically, then can download, verify, replace, and restart itself. A commit alone does not trigger client updates; publish a newer versioned release.
Use Apply Hotfix to update Item Preview QoL in an existing compatible installation.
Use Verify Mod Pack Install on an existing pack to verify every managed runtime file against the signed archive set. Missing files are restored and hash-mismatched files are replaced. Existing user configuration files and unrelated files are preserved. The verified bundle remains in the updater cache so later verification runs can reuse it without downloading it again.
- Start with a fresh combined SPT 4.1.3 installation backed by EFT build 40743.
- Close EFT, the launcher, the server, and any headless clients using that installation.
- Run the updater and select the SPT installation folder.
- Select Fresh install from private pack.
The updater validates the target version and existing-mod state. It downloads the AWS-hosted pack, reports progress, verifies SHA-256, installs the archives, audits the receipt, and deletes its downloaded bundle after success.
Version 1.1.7 closes the download stream before SHA-256 verification. It also detects, verifies, and reuses a complete .part file left by version 1.1.6 instead of downloading the pack again.
Version 1.1.8 normalizes Windows archive separators before writing files on Linux. Its Repair Linux install action repairs and audits a version 1.1.7 installation that already reached the final audit without downloading the pack again.
Version 1.1.9 makes Linux repair idempotent and ignores non-runtime source artifacts left by version 1.1.7. It also adds full managed-file verification and concise, user-facing validation errors.
Use the .NET 10 SDK:
dotnet test .\cross-platform.tests\SPT413-Phetzy-Updater.CrossPlatform.Tests.csproj -c Release
dotnet publish .\cross-platform\SPT413-Phetzy-Updater.CrossPlatform.csproj -c Release -r win-x64 --self-contained true -p:PublishSingleFile=true
dotnet publish .\cross-platform\SPT413-Phetzy-Updater.CrossPlatform.csproj -c Release -r linux-x64 --self-contained true -p:PublishSingleFile=trueRelease builds supply PrivateManifestSource and HotfixPayload MSBuild properties. The repository workflow reads the private source from the PHETZY_UPDATER_SOURCE_JSON_B64 Actions secret.
The Item Preview QoL hotfix payload is included under its MIT license. See THIRD_PARTY_LICENSES/ItemPreviewQoL-MIT.txt.
The official release embeds bearer access to the private pack. Do not mirror or repost the updater. Local source builds without the private embedded resource can still use an adjacent updater-source.json for development.
The executables are not code-signed. Verify the release ZIP against its accompanying .sha256 file before running it.