Updates

Updates

The launcher, the client it installs into the game, and the servers are one release, with one version number. The launcher keeps you current by itself.

How the launcher updates

• When it checks: when it starts, every 4 hours while it's open, and straight away when a server refuses it as outdated.
• What you see: a banner at the top, Version x is available, with Update now, What's new (the release notes) and Later. The launcher downloads the new one, checks it, replaces itself and restarts.
• The client comes with it: the launcher carries the matching client DLL, and replaces any other version in the game folder (once the game is closed).
• New game options: when an update brings options that change how the game plays, the launcher lists them once, in a New game options window, with what we recommend already chosen. The game starts once you've saved your choice; Settings › Game changes them later.
• What's new: the first time it opens after an update, the launcher shows the main changes and the fixes you'd notice. Click the version at the bottom of the side menu to see it again. See The Launcher › What's new.

Settings › About › Check for updates checks now.

Every update is checked

The launcher installs only releases from this project's GitHub releases. It checks every download against the release's published SHA-256 checksums, and the checksums against the release key's signature, so a changed release is never installed. You can check a download yourself, too: see Antivirus Warnings › Check your download.

"Update the launcher"

Servers refuse launchers and clients older than they allow (by default, their own release). When that happens:

• the Status card shows Update the launcher, with Update;
• the message says which version the server needs.

Press Update. If it says "… is the latest: the server needs one that hasn't been published. Try again later.", the server needs a release that isn't published yet: try again later, or pick another server in the meantime.

When the servers update

Servers in a network update themselves: one server first, watched for a while, then the rest when they're quiet. While a release goes out, a notice under the launch bar says when your server updates and is back, in your own time zone, and that you can keep playing until then. If your server is already on a newer version than your launcher, it offers Update and restart.

Booked maintenance shows the same way, on the day or from 12 hours before: see The Launcher › Maintenance.

Development builds

A launcher whose version ends in -dev (or one built from source) is a development build: it never updates itself. If a server asks for a newer one, it says "This is a development build: it doesn't update itself. Get the new one from whoever sent it." Download the latest release to get back on the update track.

Update failed?

Message	What to do
GitHub didn't answer in time, or the download stalled	Try again later, or download launcher.exe from the latest release yourself and replace yours with it
release x isn't signed yet; try again later	A release has just been published and isn't signed yet. Wait a few minutes
release x isn't signed by the project's release key as x; not installed	The release's signature doesn't check out for that version (a release published again under another tag, say). The launcher refuses it on purpose. Keep the version you have, don't install that release by hand, and report it
… doesn't match its published checksum; not installed	The download was damaged or changed on the way. Try again; if it repeats, download it yourself and check it
The update keeps disappearing, or launcher.exe won't start after updating	Your antivirus may be removing it: see Antivirus Warnings

Release notes for each version are on the releases page.