On this page
What should I back up before updating?
- Close the game. If it is still running, the updater displays
Close the game before updating. - Check Game → Saves folder so you know which data directory the installation uses. Saves and backups explains blank fields, custom paths and backup copies.
- Copy that data directory and your settings to a separate backup location. On Windows, these include
user,spartanport.iniandsettings.jsonin the installation folder; Linux data lives separately from the AppImage. Keepmods,mods.json,mods_presets.jsonandpatches.jsonif you use them, too.
This updates the port program. For the game's own version and separate Update folder, use Game version.
How do I update through the Windows launcher?
- Open the existing launcher.
- Go to Advanced.
- Click Check for updates. A newer version appears in a version card. What's new opens its release notes.
- Click Update on that card.
- Confirm the dialog saying the launcher will close, install the version and open again. A download percentage appears while it fetches the package.
- When the launcher reopens, check that it shows 2.7.0.
- Check the game paths and settings before launching.
The packaged updater preserves user, out, mods, spartanport.ini, settings.json, mods.json, mods_presets.json and patches.json. Keep the existing installation for this update path so it uses those files.
If the check displays You have the latest version (…), it found no newer release. If it displays Could not check for updates: …, the check failed: open the release page to compare versions.
If installation fails with Could not install the update. Download it from the releases page., use the manual Windows steps below and include the failure message in a report.
How do I update Windows manually?
- Close the game and launcher, and make the backup described above.
- Download and verify the current Windows ZIP.
- Extract it completely into a different program folder. Keep the old installation available.
- Copy
spartanport.iniandsettings.jsoninto the new program folder. Copy existingmods,mods.json,mods_presets.jsonandpatches.jsonif used. - For default Windows saves, copy
savedataandsavedata_backupsfrom the olduserfolder into the newuserfolder. Keep each version's cache separate. For a custom Saves folder, use a copy of that data root and set its path in the new launcher. - Open the new
SpartanPort.exe, check the game and update paths, and click Save. - Click PLAY, then Load Game, and confirm your expected progress appears.
Keep the old program and backup until the new installation loads your progress. Use Saves if the new list points at a different data root.
How do I update Linux or Steam Deck?
For the 2.6.0 AppImage:
- Close the game and launcher.
- Download
spartanport-x86_64.AppImagefrom the current release and verify its SHA-256. - Replace the old AppImage file with the new file. Keep the separate data directory.
- Use the Linux launch commands to make the replacement executable and start it.
- Check the saved game paths and Saves folder.
- Start the game.
- Select Load Game to check the save list.
The current AppImage has Advanced → Check for updates for subsequent releases. It needs a writable directory. It downloads a temporary file, checks the release's SHA-256 and replaces the AppImage only after that check succeeds. A failed download or checksum leaves the old file in place.
If the launcher cannot write to its directory, use the offered release link for a manual replacement. A launch outside an AppImage also opens the release page instead of replacing itself. If the check says the newer release has no Linux build, keep using the Linux package you have.
Will the rename keep my shortcuts, saves and settings?
gow3_pc became SpartanPort in 2.6.0. The first start copies old configuration and data to the new names, keeps old files and leaves existing destination files intact. Linux's old cache and out directory are excluded from that migration.
If a Linux Steam shortcut contains the old AppImage filename, change that filename to spartanport-x86_64.AppImage at the file's current path. The Windows package includes compatibility launchers for older shortcuts.
Why does the first start after updating stutter?
The first start rebuilds the shader cache once and can stutter. Later starts reuse it. Keep caches separate from older builds. If an older version wrote into the new disk cache, follow the exact cache-file rebuild steps. A persistent black screen or crash needs the matching troubleshooting steps.
Open Load Game to check your saves. If the expected list is missing, confirm Saves folder using Saves; the same page has the full backup restoration steps.
Can I return to my previous working version?
Yes. Close the game and keep the new failure log first. Reopen the old installation you kept, with its original settings and its own cache. Restore the save backup made before the update if you need that earlier progress.
Keep the new and old data roots separate. Saves explains restoration and how to return to the saves replaced by a restore. Include the last working version and the new failure message in a report.
