Skip to content

Releases

PhValheim Client 2.0.19 — all-platform prerelease

Choose a tag to compare

@brianmiller brianmiller released this 19 Nov 20:17

2.0.19 is a prerelease for testing, for Windows, Linux (DEB, RPM, TGZ, Flatpak) and macOS.
This broader revision handles Hidden mod configuration, player-setting preservation
and sync records as well as loader/backend files, addressing
issue #25.
Live Valheim gameplay with this revision remains unverified.

PUBLISHED — broader revision, November 20, 2026. Seven packages were replaced;
macinstall.sh is unchanged. All nine public downloads, fetched without authentication,
are byte-identical to the release files, including SHA256SUMS; all eight checksum
entries passed.
2.0.18 remains stable, including normal installer and “latest” links.

Already installed 2.0.19?

Redownload and reinstall your 2.0.19 package on every platform. The version and
filenames are unchanged. Verify SHA-256 against the table
below before installing: the new and previous MSIs are both 32,899,072 bytes, so
size cannot distinguish them. Native upgrades from both earlier 2.0.19 ProductCodes
are verified for this exact MSI.

For an existing RPM installation, explicitly replace the same-version package:

sudo rpm -Uvh --replacepkgs ./phvalheim-client-2.0.19-x86_64.rpm

Downloads and SHA-256

These are the published broader revision sizes and hashes. All eight entries in the release
SHA256SUMS
passed against the unauthenticated public downloads, which match the release files byte for byte.

Platform / format Artifact Bytes SHA-256
Windows MSI phvalheim-client-2.0.19-x86_64.msi 32,899,072 6816a959190a3a4eedbd5fbe4cab15348c9fc10c8345699f9c098d8e8b611ab5
Linux DEB phvalheim-client-2.0.19-x86_64.deb 23,605,832 7d4e2233a124702c54c6fb31feaea22b205bfad6ae8586f2471a9e49d2ad1740
Linux RPM phvalheim-client-2.0.19-x86_64.rpm 25,715,981 af17b34c63a1c242345f1674b09e58c0574aeac3c29a546aeb0463a0ce9fe1b9
Linux TGZ phvalheim-client-2.0.19-universal-x86_64.tar.gz 31,442,762 3f956daa86f0c0a4b1b59545bf600afdf8c4245be6fd029aeb9601a9cc42d77a
Linux Flatpak phvalheim-client-2.0.19-x86_64.flatpak 23,330,920 4356e8698004915512403cc6bd61a9085bb1b417e1d77c1b49460c07a80fe2d5
macOS universal TGZ (primary) phvalheim-client-2.0.19-macos-universal.tar.gz 61,777,898 d0279d41ccaa7aea0f80d2e5a64449be77f6af1f5f10677be2a9df86c58fc24b
macOS universal PKG (supplementary) phvalheim-client-2.0.19-macos-universal.pkg 61,781,848 b62d282b165030b5a424e8e5752ca1ea8d6bb6d1643e73850863c0c2e65bbdb3
macOS shell installer macinstall.sh 9,355 13c8894e2d76e0cebb1a6b097c7dbbd175a420175a134c65d2374299f748d925

macOS uses the shell installer plus universal TGZ as its primary installation method;
the PKG is supplementary. The normal installer selects stable 2.0.18.
Download the installer and tarball into the same folder, verify their hashes above,
and explicitly select the 2.0.19 tarball:

curl -fLO https://github.com/brianmiller/phvalheim-client/releases/download/2.0.19/macinstall.sh
curl -fLO https://github.com/brianmiller/phvalheim-client/releases/download/2.0.19/phvalheim-client-2.0.19-macos-universal.tar.gz
PHVALHEIM_TARBALL=./phvalheim-client-2.0.19-macos-universal.tar.gz bash ./macinstall.sh install

For Linux DEB and TGZ, follow the README installation commands
with version 2.0.19; for RPM use the replacement command above. For Flatpak:

flatpak install --user --reinstall ./phvalheim-client-2.0.19-x86_64.flatpak

On Windows, run the downloaded MSI.

What changed

Windows managed writes now handle Hidden files during mod-config policy enforcement,
personal-setting application and preservation, and sync-record updates, in addition to
winhttp.dll, doorstop_config.ini and phvalheim.backend. Existing-file overwrites
preserve Hidden attributes and existing ACLs. Personal config retains Hidden through
staged updates; sync records and game-directory loader files also retain Hidden.
A full world regeneration recreates cache/backend files with fresh metadata, so their
previous Hidden flags are not expected to survive that lifecycle.

The client does not scan for and unhide files, reset permissions, clear ReadOnly, or
request elevation. ReadOnly still aborts protected updates; a genuinely denied backend
write still aborts launch. Reparse-point destinations are rejected. Managed writes stage
contents before replacement; failed staging preserves the original. Staging does not
guarantee protection against external races or power loss.

Windows loader installation copies only winhttp.dll and doorstop_config.ini,
skipping files intended for other platforms. Linux selects libdoorstop_x64.so
and the config; macOS copies no loader files into the signed Valheim.app bundle.
Ordinary macOS copies also preserve the destination's Hidden flag.

Diagnostics and troubleshooting

Path-specific diagnostics retain the failing operation, exception type, message,
and hexadecimal HResult, plus file attributes, Windows owner/ACL observations,
and a temporary parent-directory write probe where available. Unavailable observations
remain unknown; these observations do not establish antivirus or Controlled Folder Access as the cause.

Diagnostics, persistent logs, and disk-space checks are available on all platforms:

Platform Normal diagnostic log
Windows %APPDATA%\PhValheim\logs\phvalheim-client.log
Linux ~/.config/PhValheim/logs/phvalheim-client.log
macOS ~/Library/Application Support/PhValheim/logs/phvalheim-client.log

Logs redact credentials and rotate at 1 MiB and at the start of each run, retaining
up to three archives. If the normal location fails, the client tries a temporary
fallback. Use the actual path printed in the error; if both locations fail, logging
is reported as unavailable. Review logs before sharing: local paths and usernames may remain.

Disk-space preflight checks the destination volume for downloads, archive/config
staging, loader copies, and backend writes. It reports required additional bytes
and available space where measurable; unknown sizes remain unknown, and estimates
do not guarantee an update will fit. Failed staged updates preserve the installed
world; failed download transport preserves the cached archive.

Published revision validation

  • Native actual-client source validation 44643769336: SUCCESS. All 11 Hidden-file targets passed, with a published-executable negative control and a ReadOnly control. This is source validation, not validation of the new MSI.
  • Full source CI 44648623221: all 15 jobs succeeded.
  • Published MSI local validation: 81 structural, 24 executable smoke, and 36 Wine behavior checks passed. Wine repair was SKIPPED; native Windows repair PASSED.
  • Exact packaged Windows validation 44647729127: the 11-target Hidden-file actual-client fixture and previous-correction 2.0.19 migration, 14 checks both SUCCEEDED. Upgrades from 2.0.12 through 2.0.18, native repair, the wizard and negative control also SUCCEEDED. The initial workflow failed overall only in the original 2.0.19 migration job, because of a COM test-harness bug.
  • Targeted native Windows rerun 44649449411 at 47790c96adac024cb7f2d6f66bf49e2795c5fcd5: SUCCESS, with 14 original-2.0.19 migration checks and 20 installer-condition cases. It tested the same unchanged MSI (6816a959…), completing the native Windows gate and verifying migration from both known 2.0.19 predecessors.
  • Linux DEB, RPM and TGZ each passed 13 upgrade/removal checks from stable 2.0.18. Same-version 2.0.19 DEB and TGZ reinstalls each passed 13 checks; RPM reinstall with --replacepkgs passed exact-binary verification.
  • Flatpak passed 42 package, 88 runtime/browser, 46 native pass-through, 16 stable-2.0.18 upgrade, and 16 prior-2.0.19 upgrade checks.
  • Native macOS validation 44646602998: SUCCESS, with 15 checks in each of four candidate installation scenarios and 7 URL-handler checks in each of three phases. Native execution was Apple Silicon only.

Validation limits

No Intel Mac runtime validation or actual Valheim gameplay validation was performed.
No Bazzite-specific validation is claimed.
Recording Steam/game stub...

Read more

2.0.18 — Linux overlay controls and personal mod settings

Choose a tag to compare

@brianmiller brianmiller released this 06 Nov 06:04
dd15bed

PhValheim Client 2.0.18 — overlay controls and personal settings

Stable release for Windows, Linux and macOS, alongside PhValheim Server 2.62.

The Steam overlay is enabled by default for direct modded Linux launches when Steam's renderer is available. PhValheim Server 2.62 can disable it globally or override it per world. Preferences take effect on the next client launch. The player's PHVALHEIM_NO_OVERLAY=1 always wins; the older PHVALHEIM_ENABLE_OVERLAY=1 is no longer necessary and cannot override an operator disable.

Windows, macOS and vanilla launches continue to use Steam's own overlay settings. Disabling the overlay is an optional troubleshooting step, not proof that it caused a hang.

This release also applies personal mod settings saved in the server's themed View mods panel. Choices belong to one Steam account and world and apply at the next launch. Only published, operator-overridable keys are accepted; operator-controlled values remain enforced. Use published default saves the suggested value; Use local config stops applying a web choice and keeps its last local value. Older servers and ordinary local configuration continue to work.

Personal-setting links expire after one hour. If the client cannot retrieve your choices, reopen the world page and launch again. The read credential is scoped to your account and world and is not forwarded to the game.

Packages: Windows MSI; Linux Flatpak, DEB, RPM and tarball; macOS universal PKG and tarball (Apple Silicon and Intel). Checksums are in SHA256SUMS.

For the macOS tarball, download macinstall.sh alongside the archive and run:

PHVALHEIM_TARBALL=./phvalheim-client-2.0.18-macos-universal.tar.gz bash macinstall.sh install

Install the downloaded Flatpak bundle:

flatpak install --user --reinstall ./phvalheim-client-2.0.18-x86_64.flatpak

Linux packages updated November 6: if you installed a 2.0.18 candidate before then, download and install it again. Flatpak, DEB, RPM and tarball now fix the enabled Vulkan overlay being disabled by an environment variable set to 0; enabling removes the variable entirely. Operator-off and PHVALHEIM_NO_OVERLAY=1 still disable it. The already-tested Windows and macOS packages are unchanged; this follow-up affects direct modded Linux launches.

Brian confirmed the overlay toggle works on Bazzite in Desktop Mode using the updated Flatpak. The Flatpak passed 42 package checks and 85 browser/runtime checks; native launch checks and real Vulkan-loader tests verify environment handling. The rebuilt DEB, RPM and tarball each passed 13 real upgrade/removal checks from the published 2.0.17 packages. Recording Steam/game fixtures do not establish every graphics-driver or Steam packaging combination.

Validation covers native Windows upgrades from 2.0.12 through 2.0.17, exact installed payload, repair/uninstall and the full wizard; native Apple Silicon tarball and PKG upgrades from 2.0.17, PKG reinstall/fresh install and browser URL activation; Linux package upgrades from 2.0.17; and Flatpak installation, browser launch, synchronization and personal configuration. Linux launch tests use recording Steam and Valheim stubs.

Beyond the reported Bazzite Desktop overlay confirmation, broad live Valheim/GPU behavior, the cause of any hang, Intel Mac execution, SteamOS and Flatpak Steam are not established by these checks. Both macOS architectures are included and their signatures checked. The macOS payload uses ad-hoc signing; it is not Apple-notarized. The Windows MSI uses the project's self-signed certificate.

Package source: Linux runtime b25eccb, tested Flatpak 8f67065, and rebuilt native Linux packages 512f50f. Unchanged Windows/macOS package source: 0d95b03.

2.0.17 — Player config preferences and Linux launch fixes

Choose a tag to compare

@brianmiller brianmiller released this 28 Oct 01:41

PhValheim Client 2.0.17 — config preferences and Linux launch reliability

Supports PhValheim Server 2.60 config delivery. Personal config files survive both full mod
updates and small settings updates. Overridable values fill missing settings only; enforced
values are reapplied before every launch, even when there is nothing to download. Retired
rules release their unchanged enforced values so the mod can regenerate defaults.

Updates extract and merge into a temporary folder before swapping it into place. Failure
keeps the working install. A missing extracted world restores from the cached archive and
then fetches current settings, even when a prior config-only update was newer than that zip.
Older servers retain the previous synchronization contract.

Testing uses real archives, HTTP downloads and the shipped Syncer, with failure and recovery
cases. The actual Syncer harness passed 26 checks, and six archive-to-client checks passed.
Live Unity gameplay remains an operator test. This is the official stable 2.0.17 release.
The tested 2026-10-31 packages were promoted unchanged on 2026-11-02.

Linux launch reliability

  • Direct modded Linux launches no longer inject Steam's overlay automatically. BepInEx
    remains enabled. Opt in with PHVALHEIM_ENABLE_OVERLAY=1; the existing
    PHVALHEIM_NO_OVERLAY=1 still takes precedence. Overlay-off launches remove inherited
    Steam renderer preload entries and disable the implicit Vulkan overlay layer.
  • The Flatpak checks the host process list, so its terminal can close when the game exits.
  • A per-user launch lock rejects duplicate clicks before prep or sync. A game already
    running outside PhValheim also blocks sync and launch. No queued automatic relaunch.
  • Failed host inspection is reported, not treated as proof the game stopped. Host queries
    drain both output pipes and have an enforced timeout. Unobservable post-launch sessions
    show a warning and close their launcher after 30 seconds without terminating the game.

This addresses launcher defects found while investigating a user-reported Steam overlay
hang. The original machine's raw stacks have not been inspected; the claimed Steam semaphore
cycle and exact root cause are unconfirmed. No live Steam/Unity gameplay fix is claimed.
Disabling our overlay injection removes that integration path; enabling it can still hang.
Vanilla launches remain managed by Steam.

The Vulkan layer opt-out follows the Khronos troubleshooting guidance.

Downloads

  • Windows: phvalheim-client-2.0.17-x86_64.msi.
  • Linux: universal x86_64 tarball, Debian .deb, Fedora .rpm, and Flatpak.
  • macOS: universal Intel/Apple Silicon tarball and .pkg, plus macinstall.sh.
  • SHA256SUMS identifies the exact revision of every download.

These packages are revisions of the 2.0.17 prerelease. Redownload the appropriate
package even if your installed client already reports 2.0.17. The Windows revision
explicitly supports upgrading the original 2.0.17 MSI, while preserving protection
against newer versions and unrecognized same-version packages. The Mac .pkg uses
the same universal client and URL handler as the tarball.

Install or upgrade the downloaded Flatpak with:

flatpak install --user ./phvalheim-client-2.0.17-x86_64.flatpak

Install this client before joining Server 2.60 worlds that use the new config policy. Confirm personal settings
survive both a full mod update and a config-only update, then clear Overridable in the admin
UI and confirm the operator's value returns before launch. A mod's own runtime synchronization
can still override settings during play.

The current launcher compares against stable releases when checking for updates.

Close the old game and launcher windows once before using this Linux revision. Launch
with the same changed config, confirm the overlay-off notice, quit, and launch again.
The launcher should close after the game exits and reject a second click while playing.

Earlier Linux revision validation (2026-10-30)

The rebuilt 2.0.17 packages passed 42 Flatpak package checks, 53 runtime/browser checks,
and 33 native launch checks. Installing over the earlier 2.0.17 passed 16 checks, including
confirmation that the active Flatpak commit changed. Installing over the withdrawn 2.0.18
test build also passed 16 checks. The tarball contains the same tested published executable.

The unchanged launch implementation previously passed 22 process/lock/transport checks;
config-policy26, launch-window14, sync-display25, and progress10 also passed. Those focused
suites were not repeated for this version-only correction. Recording Steam/Valheim stubs
are used for runtime tests; live Unity/GPU overlay compatibility remains unverified.

Full package refresh (2026-10-31)

All seven package formats are built and tested. These exact packages are now the stable release.
Runtime source is unchanged from 7ae44e0; packaging and test improvements are in
e087519.
The original 2.0.17 git tag is retained; use that source link for this revised package set.

  • Debian, RPM and Linux tarball: each passed 13 real install/upgrade/removal checks
    from the published 2.0.16 package.
  • Flatpak: 42 package, 53 runtime/browser, 33 native launch checks, plus 16 checks
    installing over the earlier 2.0.17 Flatpak, including active commit replacement.
  • Windows: 78 package checks, 24 executable smoke checks, and 36 Wine behavior checks.
    Native Windows passed 14 original-to-revised 2.0.17 upgrade/repair/removal checks
    and 12 full-wizard checks. The installed executable matched the candidate SHA256.
    An old-package negative control failed specifically on that hash check.
  • macOS: both universal architectures checked; native Apple Silicon verified tarball
    install, PKG-over-tarball, PKG reinstall, fresh PKG install, and URL activation.
    Fresh PKG installation registers links in the desktop user's Launch Services database.

Native installer evidence: package validation run.
These are packaging/launcher checks; live Steam/Valheim gameplay remains unverified.

For the macOS tarball, download it and macinstall.sh from this release, then run:

PHVALHEIM_TARBALL=./phvalheim-client-2.0.17-macos-universal.tar.gz bash ./macinstall.sh install

Running macinstall.sh without that override installs the latest stable release.
Alternatively, use the included universal .pkg.

2.0.16 — Steam overlay on Linux modded launches, Flatpak runtime 25.08, upgrade path verified for every installer

Choose a tag to compare

@brianmiller brianmiller released this 21 Oct 02:34

Pre-release. This build is published for players who want to try the Linux changes below
before they become the recommended client. Two things follow from that: the client's own
"a newer version is available" check and your server's web page download buttons both skip
pre-releases, so nothing will nudge anyone toward this build and your server will keep
offering 2.0.15 until 2.0.16 is promoted. Get it from this page. Nothing in it needs a
particular server version.

Three things, all Linux. The Windows and macOS packages carry no code change beyond the
version number; they are published so that every platform is on one version.

What changed

Modded launches on Linux have the Steam overlay

A vanilla launch goes through Steam (steam -applaunch), so Steam sets the game up itself and
Shift+Tab works. A modded launch cannot: BepInEx has to be injected through the environment,
so the client starts valheim.x86_64 directly, and Steam never sees the game start and never
injects its overlay. That is why the overlay worked in a vanilla world and not in a modded one,
which is what players on Bazzite reported.

Steam's injection is nothing more than environment variables, so the client now sets the same
ones on a modded launch: Steam's gameoverlayrenderer.so on the game's LD_PRELOAD, after
doorstop, and Valheim's app id in the three names the overlay looks for. Doorstop first, then
the overlay, is the order every BepInEx-on-Steam Linux user already runs, because BepInEx's own
run_bepinex.sh prepends doorstop to the LD_PRELOAD that Steam handed it.

Details that decide whether this is safe to ship on every machine:

  • The library is only named when it exists. If <steam root>/ubuntu12_64/gameoverlayrenderer.so
    is not on disk the launch is exactly what 2.0.15 did, and the console says why the overlay was
    skipped. A path that does not exist must never go on LD_PRELOAD: the loader complains at
    exec and the game starts anyway, which is the worst kind of warning.
  • Only the 64-bit library. Steam preloads both the 32- and 64-bit ones. Valheim is x86_64;
    the 32-bit one would print "wrong ELF class" into the console on every launch for nothing.
  • Opt-out without waiting for a release: PHVALHEIM_NO_OVERLAY=1 in the client's
    environment. The overlay has a history of crashing games on some Mesa and Wayland
    combinations; a player hit by that keeps playing. For the Flatpak client:
    flatpak override --user --env=PHVALHEIM_NO_OVERLAY=1 com.phvalheim.Client.
  • Steam must already be running, as it always had to be. The client starts it if it is not
    and waits ten seconds; if that race is lost the overlay silently does nothing. Unchanged
    behaviour, now visible.
  • The overlay hooks GLX and X11 Vulkan surfaces. Valheim runs under XWayland on a Wayland
    desktop, so it works there; a forced Wayland-native SDL would not get it.
  • A Flatpak Steam uses the same code (the Steam root is under
    ~/.var/app/com.valvesoftware.Steam), but that launch path remains untested on real
    hardware, as docs/FLATPAK.md has said since it was written.

The stub launch rigs that run on every Flatpak build now pin the exact LD_PRELOAD string
(order included) and the three Steam ids, and the native rig proves the guard by deleting the
stub library and by setting the opt-out, checking that both leave LD_PRELOAD as doorstop
alone and print the reason.

PHVALHEIM_VERBOSE=1 now prints every variable the game is launched with, including the
overlay path. The old verbose list named two variables the client never set and printed
"(unset)" for them on every run.

The Flatpak moves to the 25.08 runtime

Flathub marked org.freedesktop.Platform 24.08 end-of-life on 2026-10-03, and Bazaar had
started showing "Stopped Receiving Core Updates" on our listing. The 2.0.16 bundle is built on
and declares 25.08. Nothing to do on your side: installing the bundle pulls 25.08 from Flathub,
and the old runtime stays until flatpak uninstall --unused.

Bazaar may show an old version, and that is Bazaar

Bazzite's app store can show this app's detail page at one old version and its Library row at
another after you install a newer bundle. The bundles are correct (each of 2.0.13, 2.0.14 and
2.0.15 was unpacked and checked); Bazaar keeps its own cache of each app's AppStream entry and,
for an app installed from a bundle rather than a remote, never refreshes it. flatpak info com.phvalheim.Client and Warehouse show the installed version. Bazaar's Refresh fixes the
display, or delete ~/.cache/io.github.kolunmi.Bazaar.

Upgrading from 2.0.15

Every package here was installed OVER the published 2.0.15 package, by the package manager a
player would use, and the result was run and read back. Each path has a control that feeds the
rig the old package as the "new" one and requires it to fail.

Client How to upgrade Verified
Debian / Ubuntu .deb sudo dpkg -i phvalheim-client-2.0.16-x86_64.deb builders/verify_linux_upgrade.sh deb, in the Debian build image
Fedora .rpm sudo dnf install ./phvalheim-client-2.0.16-x86_64.rpm (or rpm -U) builders/verify_linux_upgrade.sh rpm, in the Fedora build image
Universal tarball extract, sudo ./phvalheim-client-installer.sh install builders/verify_linux_upgrade.sh tgz
Flatpak flatpak install phvalheim-client-2.0.16-x86_64.flatpak — no --reinstall needed, the commit and runtime both move builders/verify_flatpak_upgrade.sh, bundle over bundle, 24.08 → 25.08
Windows .msi run the installer CI: msiexec upgrade from each of 2.0.12, 2.0.13, 2.0.14 and 2.0.15, plus the full wizard clicked
macOS macinstall.sh install, or the tarball CI: 2.0.15 installed by its own installer, then this build installed over it on Apple Silicon

The Windows and macOS legs run against the published assets on this page, so their result
is in this release's CI run rather than in a log on a build machine.

2.0.15 — faster launches, and a settings change no longer costs the whole modpack

Choose a tag to compare

@brianmiller brianmiller released this 04 Oct 18:57

This is the recommended client for every player, on every server. It pairs with PhValheim
Server 2.55
, but nothing here requires it — against an older server this client behaves as
2.0.14 did, minus the per-launch delay described below.

There is no "stay on the old one" caveat: everything here is an improvement on any server.

Fixes you will notice immediately

"Valheim is damaged and can't be opened" — macOS

A macOS player reported Valheim refusing to start with "'valheim' is damaged and can't be
opened. You should move it to the Trash."
Nothing was damaged. A signed .app seals its
contents, and a file we had placed under Contents/MacOS/ invalidated that seal — so Gatekeeper
blocked the app. Deleting the stray file restores the original signature exactly, because the
seal was computed over a tree without it. This client removes it on launch and never re-signs
anything, which matters: re-signing would replace Apple's identity with ours and survive Steam's
"verify integrity of game files".

If you hit this, you do not need to reinstall Valheim. Launch through PhValheim once.

The download progress stays on one line

The progress bar used to print a new line for every percent — about a hundred lines scrolling up
the window on a large modpack. It now rewrites a single line in place, and the finished line no
longer leaves fragments of the longer line behind it.

The launch window stays open until you quit Valheim

It used to close itself ten seconds after launching, taking the whole launch log with it — so a
crash two minutes into a session had nothing left on screen to explain it. The window now closes
when Valheim does, and tells you plainly that you can close it at any time and the game keeps
running.

That last part is now true on macOS, where it was not before. The macOS app opens a Terminal
window to run this client, and macOS signals every process in that window when you close it —
which previously killed Valheim with it. The game is now started detached, so closing the window
really is safe.

Launching is faster, on every launch, against every server

The client used to compute the MD5 of the world payload every single time you launched, just
to answer "which version do I already have". On a large modpack that is over half a gigabyte read
off disk and hashed before anything else happens.

It now keeps a small <world>.sync record beside the payload and reads that instead. The payload
is hashed in exactly two situations: the record is missing (a first run, or the first launch after
upgrading to this version), or a download just finished — in which case hashing it is the point.

That second case is a correctness requirement, not an optimisation. The old
hash-every-launch behaviour caught a truncated download by accident on the following run. A
client that wrote down "I have version X" without checking what it received would turn that
accidental self-healing into a permanent lie. So a completed download is verified against the
server's checksum before anything is recorded, and a payload that does not match is discarded
with your existing install left untouched rather than half-replaced.

A settings change no longer costs you the whole modpack

This part needs a 2.55 server.

When an operator changed a mod setting, the only way to reach players was to rebuild the entire
client payload — so everyone re-downloaded the whole modpack to receive a few lines of changed
text. Measured on a real world: 577,604,696 bytes to deliver 80,174 bytes of actual change.

The server can now publish a configuration-only update, and this client recognises one and
fetches just the configuration archive. Same world, same mods, 80 KB instead of 573 MB.

An older client talking to a 2.55 server is not broken by this — it simply does not take the
shortcut and downloads everything, exactly as it always did.

Install

Pick the file for your platform below. On macOS, run macinstall.sh from the extracted tarball.
Windows users: the .msi is unsigned, so SmartScreen will warn — choose More info → Run
anyway
.

2.0.14 — the client hands the world's details to the Companion

Choose a tag to compare

@brianmiller brianmiller released this 02 Oct 21:07

Released. Confirmed end to end on a real Valheim client. It pairs with PhValheim Server
2.53
, released alongside it. If you are not running a 2.53 server there is nothing urgent here
for you, but it is a safe upgrade from 2.0.13 either way.

Windows note: installing this over an existing 2.0.13 upgrades it in place. If a different
build of the same version is already installed, the installer now says so instead of adding a
second copy alongside it.

What changed

The client now hands the world's details to the Companion mod.

Until now the client installed a world's mods and started Valheim, and the player still had to
join the world themselves — typing an address, or pasting a crossplay join code. The Companion
mod that PhValheim installs on every modded world can do that last step for the player, but it
had no way of knowing which world the client had just been launched for.

This release passes that along on the command line, as --phvalheim-launch followed by the
launch payload. On a 2.53 server the Companion reads it and offers a Connect button on
Valheim's main menu: the player picks their own character and joins, with nothing to copy and
nothing to type.

Two details worth recording, because both are places this could have gone wrong quietly:

  • The payload handed over is the original base64 the client was given, not a re-encoding of
    the fields after parsing. Re-encoding would have been a second place to get the positional
    order wrong, and the two would have drifted the first time a field was added.
  • Windows launches Valheim through Steam's -applaunch, which takes a single command string
    rather than an argument list, so it has its own append path. Every other platform passes
    separate argv entries.

Nothing is appended when there is no payload. A plain Steam launch, or this client started
without a world, produces exactly the command line it did in 2.0.13 — the argument is only
added when a launch payload is actually present, so this cannot make an ordinary launch look
like a PhValheim one.

Compatibility

  • Against a 2.52 or older server: harmless. Those servers do not send a launch payload, so
    nothing is appended and the client behaves exactly as 2.0.13 did.
  • Against a 2.53 server: the Companion offers Connect on modded worlds.
  • Vanilla (unmodded) worlds are unaffected and always will be. A vanilla world has no
    BepInEx, so it has no Companion, so there is nothing to hand the payload to. Those worlds are
    joined with their join code, as before. This is by design, not a gap.

2.0.13

Choose a tag to compare

@brianmiller brianmiller released this 21 Sep 01:38

Confirmed working on real hardware: a modded world synced, launched and loaded all its mods correctly on Omarchy (Arch + Hyprland). Not yet confirmed on SteamOS or Bazzite specifically — reports welcome.

New: Linux Flatpak

For SteamOS, Bazzite and other immutable gaming distros where a .deb or .rpm is awkward or impossible (phvalheim-server#86).

flatpak install --user ./phvalheim-client-2.0.13-x86_64.flatpak

On Hyprland, Sway, i3 and other bare window managers, also run this once and log out and back in — otherwise clicking a world link silently does nothing. GNOME and KDE don't need it:

mkdir -p ~/.config/environment.d && printf 'XDG_DATA_DIRS=/usr/local/share:/usr/share:/var/lib/flatpak/exports/share:%s/.local/share/flatpak/exports/share\n' "$HOME" > ~/.config/environment.d/flatpak.conf

That puts Flatpak's applications directory on your session's search path, so the phvalheim:// handler can be found. It is needed by every Flatpak you install, not this one in particular, and a Flatpak cannot do it for you — an app can't edit its own session's environment. Confirm after logging back in:

gio mime x-scheme-handler/phvalheim     # should print com.phvalheim.Client.desktop

To exercise the client without any desktop wiring, copy a world's launch link from the server web UI (right-click → Copy Link Address):

flatpak run com.phvalheim.Client '<paste the phvalheim:// link here>'

Notes

Synced worlds live in ~/.config/PhValheim, the same place the .deb and .rpm use, so switching package format keeps your worlds.

Works with a system Steam (what SteamOS and Bazzite ship). A Steam installed as a Flatpak (com.valvesoftware.Steam) is also supported, but that path is untested — details and what to report. Steam libraries under home, /run/media, /media and /mnt work out of the box — that covers Steam Deck SD cards. For anywhere else:

flatpak override --user --filesystem=/your/library/path com.phvalheim.Client

This package is not meaningfully sandboxed — launching Valheim means running host programs and reading your Steam library. docs/FLATPAK.md lists every permission and why it is there.

Also in 2.0.13

  • Vanilla world support — zero-mod worlds launch through Steam's own +connect. Valheim has no client-side password argument, so the password is printed for you to type.
  • Windows installer rebuilt from scratch. The .msi now builds headlessly on Linux via wixl; the Visual Studio Setup Project is retired. Fixes along the way: the installer wizard silently vanishing, missing and unstyled wizard text, error 2834 on Cancel, and an upgrade that deleted the executable.
  • macOS ships as a universal build for Apple Silicon and Intel, with Apple Silicon running Valheim under Rosetta 2 for full mod compatibility. The .pkg is replaced by macinstall.sh. Earlier builds shipped an Apple-Silicon-only URL handler, so phvalheim:// links did not work on Intel Macs; they do now.
  • No more crash when Steam's library list is missing — you get a message instead of a stack trace.

Platform notes

  • macOS: install or upgrade with

    curl -fsSL https://raw.githubusercontent.com/brianmiller/phvalheim-client/master/macinstall.sh | bash

    The build is universal — Apple Silicon and Intel. If you installed on macOS between this release going Latest and 2026-09-23 and your client still reports 2.0.12, you got a placeholder tarball that was standing in for a build we could not produce at the time; re-run the command above to get the real 2.0.13.

  • The .msi is signed with a self-signed certificate, so SmartScreen warns about an unknown publisher — More info → Run anyway.

  • Steam Deck Game Mode has no terminal, so a launch there shows no progress output.

2.0.12

Choose a tag to compare

@brianmiller brianmiller released this 07 Mar 02:40

Linux BepInEx / Doorstop fixes + macOS Apple Silicon support

macOS Apple Silicon (arm64)

  • On Apple Silicon Macs, Valheim now runs under Rosetta 2 (x86_64 translation) for full mod compatibility
  • MonoMod v22 (bundled with BepInEx 5.x) cannot write detour trampolines on arm64 due to hardware W^X enforcement — Rosetta avoids this entirely
  • The client automatically extracts the x86_64 slice via lipo -thin and re-signs with codesign to preserve entitlements
  • All BepInEx mods load correctly under Rosetta 2 with zero errors

macOS general

  • Fixed doorstop dylib path resolution (uses world directory with app bundle fallback)
  • Added phvalheim:// URL scheme handler with Terminal window for visible progress
  • New macinstall.sh one-liner installer replaces .pkg:
    curl -fsSL https://raw.githubusercontent.com/brianmiller/phvalheim-client/master/macinstall.sh | bash
    

macOS running loads of mods

macos_mx_mods

Linux

  • Fixed BepInEx doorstop environment variables for direct Valheim launch
  • setsid wrapper ensures Valheim survives terminal close

Downloads

Platform File
Debian/Ubuntu phvalheim-client-2.0.12-x86_64.deb
Fedora/RHEL phvalheim-client-2.0.12-x86_64.rpm
Linux universal phvalheim-client-2.0.12-universal-x86_64.tar.gz
macOS (Intel + Apple Silicon) phvalheim-client-2.0.12-macos-universal.tar.gz
Windows phvalheim-client-2.0.12-x86_64.msi

2.0.11

Choose a tag to compare

@brianmiller brianmiller released this 29 Aug 21:20

updated doorstop steam arguments and moved from dotnet6 to dotnet9

2.0.10

Choose a tag to compare

@brianmiller brianmiller released this 07 Nov 23:15

Removed 'unstripped_corlib' installer as these libs were removed as a dependency from BepInEx. If these files remain, Valheim will crash-loop.