v0.3.0

What's new since v0.2.0

This release changes how the Companion keeps up with Farever patches: every Companion release is now built for exactly one game build, and this one is built for the current Steam build, 24241595. When Farever updates, grab the matching Companion release — older game builds are no longer supported.

The big stuff

Everything re-pinned to the current game build (24241595). Recent Farever patches shifted several of the structures the overlay reads — enough that damage, shield, and status data could come out wrong or empty on the live build. Every value the overlay touches — damage, heals, shields, statuses, party, position, gear — has been re-derived from the current build's own class layouts and verified against it. If the meter looked off after the last game patch, this is the fix.

One release per game update, and nothing gets paused. We'd been building toward the opposite: an overlay that identifies the game build at startup, checks it against a registry, reads memory by field name so patches can't move things out from under it, and pauses features it can't trust in the meantime. That direction is gone — the version gate has been reverted and the by-name reading layer removed. A release either matches your game build and everything works, or it doesn't and you update. No half-working states, no Map tab switched off behind a build check, no runtime guessing that can go quietly wrong mid-fight.

(v0.2.0's notes said some reads "survive the shifts that come with game and Steam patches" — walking that back: by design, they don't anymore. The matching release does that job instead.)

What this means for you

• Each Companion release states the Farever build it targets; this one is for 24241595. Update the Companion when the game updates — on a newer game build than the release targets, the overlay's numbers can't be trusted.
• Older game builds are unsupported. There's no compatibility mode; previous releases stay downloadable if you're somehow pinned to an old build.

Behind-the-scenes stuff (probably don't care, but for completeness)

• The build-gate machinery (build classification at attach, feature kill-switches, the remote registry fetch) is reverted, and the runtime by-name introspection layer is deleted outright. Every game-memory read now compiles to a fixed offset from memory_layout.rs, and a native CI test pins each constant against a layout extract of the exact hlboot.dat this release targets — a drifted offset fails the build instead of shipping wrong numbers.

Thanks as always for testing this in the wild — the bug reports are what keep it honest.

---

Download & verify

Only download from farevercompanion.com. Anything claiming to be Farever Companion that doesn't match the SHA-256 hashes below is not ours — don't run it.

There are two hashes: one for the .zip you download, and one for the dinput8.dll you copy into your game folder. The dll hash also ships inside the zip as a current-hash file.

Asset	farever-companion-v0.3.0.zip
Version	0.3.0
Released	2026-07-22
Size	2.90 MB (3,045,411 bytes)
SHA-256 (zip)	2b2d48aa31939c3518036fc0aa97ad1a99a4f3e785037beafb651dd39920d932
SHA-256 (dinput8.dll)	437ddf6431a755b7036219ef2755d86a6b4c6976ab88a3af10df076372533dee

1. Verify the download (the .zip)

Windows (PowerShell), run in the folder where you saved the file:

Get-FileHash .\farever-companion-v0.3.0.zip -Algorithm SHA256

macOS / Linux:

shasum -a 256 farever-companion-v0.3.0.zip

The output's Hash value must match SHA-256 (zip) above, character for character. If it doesn't, delete the file.

2. Verify the binary (dinput8.dll) after extracting

Once you've extracted the zip, verify dinput8.dll before copying it into your Farever folder. Run this in the extracted folder:

Get-FileHash .\dinput8.dll -Algorithm SHA256

macOS / Linux:

shasum -a 256 dinput8.dll

The output must match SHA-256 (dinput8.dll) above — which is also the value in the bundled current-hash file. If it doesn't, don't run it.

Windows users — please do this before extracting

Right-click the downloaded .zip → Properties → tick the Unblock checkbox at the bottom of the General tab → OK. Then extract. If you skip this step, Windows may falsely demand admin rights when you copy dinput8.dll into your Farever folder, and even granting admin can fail with an "unspecified error". Already extracted and stuck? Either delete and re-extract after unblocking, or open PowerShell in the extracted folder and run:

Get-ChildItem -Recurse | Unblock-File