Translocator 0.3.1

Signed

Windows no longer shows "Unknown publisher". This build carries a Public Trust
Authenticode signature issued to the company.

Subject     CN=Lueken Good Design LLC, O=Lueken Good Design LLC, S=Oregon, C=US
Issuer      CN=Microsoft ID Verified CS EOC CA 03
Timestamped RFC3161, Microsoft Public RSA Time Stamping Authority

Check it yourself with no tools: right-click the installer, Properties, then
the Digital Signatures tab.

sha256  885214dc2eaaa17326792b8ff16f01022de3a6ceb7cfacbb1d0d2a5b33e93e32

That hash is a build fingerprint rather than a security claim; the signature is
the security claim. It is useful for confirming the file here and the one on
translocator.app are the same bytes, since those are two independent hosts.

Updating

On 0.3.0: the launcher updates itself. Nothing to do.

On 0.2.x: you need to install this one by hand, once. The updater signing
key was replaced in 0.3.0, so your launcher will offer the update and then fail
with "The signature was created with a different key than the one provided".
That is expected and nothing on your installation is touched. Download the
installer below and run it; updates work normally afterwards.

Also in this release

Nothing user-facing beyond the signature. Under the hood, the signing
configuration is kept out of the repository so that anyone can still build the
project without an Azure account, and docs/releasing.md records the setup
along with the three failure modes that cost the most time to diagnose.

The launcher is free software under GPL-3.0, and contributions are taken under a
Developer Certificate of Origin with no CLA and no copyright assignment. See
CONTRIBUTING.md.

Translocator 0.3.0

Install this one by hand

The updater signing key was replaced in 0.3.0. Your existing launcher will offer
the update and then fail with:

Update failed: The signature was created with a different key than the one provided

That is expected and nothing on your install is touched. Download the installer
below, run it once, and auto-updates work normally afterwards.

Translocator_0.3.0_x64-setup.exe
sha256  31ccb501594b9d93528d616682783368c9f38b6ef74af62019e5394728a4d45b

The previous key's password was recorded incorrectly and could not be recovered.
Retiring it is a one-way door: the old public key is compiled into every 0.2.x
build, so there is no way to reach those installs automatically.

Modpacks are verified before anything is installed

Until now the launcher checked each downloaded mod against a hash printed in the
same document the pack came with, which catches a corrupted download and no
attacker at all. Now:

• Every pack version is checked against the publisher's Ed25519 signature, bound
  to their Vintage Story account.
• The first install of a pack records who signed it. Every install afterwards has
  to match, so a pack changing hands stops and asks rather than going through
  quietly. The first install is trust on first use and is not verified against
  anything, which is a real limit rather than a detail.
• A pack carries a signed revision counter, so an older release can no longer be
  served in place of the current one.
• Verification runs over the document the Hub served, not a reparsed copy of it.

Pack format v3

Clean break, no compatibility window. Packs published before this need
republishing; The Quire already has been. Packs now declare
min_launcher_version: 0.3.0, so an older launcher is refused rather than
allowed to install something it cannot verify.

Credentials

• Backups no longer contain your session or your saved server passwords.
• Signing out clears saved sessions from every installation, not only the current one.
• Saved server passwords are hidden from the in-app browser.
• Developer tools are compiled out of release builds.

Also

A pack id from the Hub could reach the filesystem before being validated. It is
checked now before it is joined to any path.

Version numbers in tauri.conf.json, package.json and Cargo.toml had drifted
apart, leaving the launcher reporting 0.1.0 to the pack version gate and to the
Hub. CI now fails when they disagree.

Translocator 0.2.4

Pack images, publisher config defaults, and the GPL relicense.

• Modpack Hub: packs can carry a logo and up to eight screenshots. Publishers upload them straight from the curator; the pack page shows a carousel and browse cards show real logos
• Curator: one click selects every mod config belonging to the pack's own mods, so a publisher's tuned settings ship as the pack's recommended defaults (players' own edits are never overwritten by updates)
• Pack pages link each mod to its ModDB page and to its author's tip link
• Translocator is now GPL-3.0 with the Commons Clause. The LICENSE ships with the app, and the end-user notice was updated to match
• Every Hub request identifies the launcher version

Existing installs update themselves. Windows x64.

Which file? Download the .exe. The .sig is the updater signature the launcher checks when it updates itself; you do not need it to install. It is published so anyone can verify a build independently against the public key in src-tauri/tauri.conf.json.

Translocator 0.2.3

Fixes wrong-game-version launches for installations adopted from VS Launcher.

• Adopted installations now launch with the game binaries VS Launcher already downloaded (VSLGameVersions), so migrated installs just run
• If a pinned game version exists nowhere on the machine, Translocator downloads it and launches in the same click instead of silently using the base-game exe
• The fallback game executable setting now only applies to installations with no version pin

Installs from 0.2.2 update themselves; this installer is for fresh machines. Windows x64.

Translocator 0.2.2

Beta build for testers.

• Self-updating: installs from here update themselves from now on (signed releases via translocator.app, thequirevs.com fallback)
• First-launch end-user notice and one-time optimized-client (Optimum) opt-in
• Optimum build tools set up automatically at first build (user-local, no admin)
• Modpack Hub: browse published packs, verified pack installs frozen to the publisher's manifest
• Mods tab: auto-loaded most-downloaded list, in-app descriptions, ModDB and tip links
• Human-readable login errors (including the account-without-the-game case)
• Graceful installation delete

Requires a Vintage Story account that owns the game. Windows x64.