v0.1.8

What's new since v0.1.7

This release is almost all about the combat log — and it's a big step. Exports that used to come out half-empty (no gear, enemies listed as bare numbers, damage you couldn't trace back to anyone) are now detailed and a fraction of the size on disk. The overlay itself also went on a small diet.

The big stuff

The combat log is dramatically better. This was the focus of the release, and it shows up all over an encounter export:

• Your gear and weapons actually show up now. The log used to read equipment through pointer paths that don't exist on current game builds, so for a lot of you an export's gear section came out simply empty. The overlay reads your live loadout now, so logs carry the weapons and armor you were actually wearing.
• Every item carries its details. Enhancement (star) level, flawless flag, rarity, socketed augments, which weapon was in hand, and the full generated stat lines — augment stats, item level, weapon upgrade specials and all — are recorded now, recomputed with the game's own formulas.
• Talents and specialization are captured. The build a hero was actually running during the fight makes it into the log.
• Enemies have names and levels. First-seen enemies used to land in the log as a bare numeric id with nothing attached. They now resolve to real names and combat levels, with a readable fallback so you get something instead of a blank when a name isn't known yet.
• Damage events link back to combatants again. Combatant ids were being written two slightly different ways, so the id stamped on a damage event often didn't match anyone in the participant list — meaning you couldn't tell who dealt what. They line up now.
• Logs are far smaller on disk. Release builds write the encounter log as minified, gzip-compressed JSON (.json.gz) — same data, a fraction of the footprint.

A lighter overlay

The shipped DLL is a little smaller. Dear ImGui's demo window, its debug and metrics tooling, and a batch of deprecated API — none of which the overlay uses — are compiled out now. It's a modest trim (~23 KB, plus a pile of unused baked-in demo text), nothing you'll notice on screen, just less dead weight in the download.

Other fixes

• Gear logging keeps up with the game. A recent game update added a new bag slot; the overlay's slot map was refreshed to match, so bag contents don't get logged as gear and slot names stay lined up.
• Crafted gear logs its stats. Some crafted pieces were coming through with empty stats — they generate the correct procedural stats now, verified against the in-game tooltip.
• Enemy names on the live meter, too. The same name and level lookup that fills in the logs also surfaces enemy target names on the meter, fetched at a gentle rate so it doesn't cost you frames.

The format is settling down

The encounter log is close to final. v1 might still pick up the odd new field or a tweaked name, but it's additive-only from here — nothing you rely on will be removed. If you've been holding off building tooling on top of the exports, this is a safe point to start.

What's being worked on

• An official JSON Schema for the encounter log, published for download so you can validate your exports automatically.
• Filling in more enemy names and levels as the lookup learns more of the game's data.

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.1.8.zip
Version	0.1.8
Released	2026-06-13
Size	3.08 MB (3,233,540 bytes)
SHA-256 (zip)	1b6c9212a035eca089f1c3f0e9af6d8b04a30ca47695018733c619b8e2282df4
SHA-256 (dinput8.dll)	ea39184b2f3842d2f057d806417794ed36094b47407b02b70bcabbcc4c4c212b

1. Verify the download (the .zip)

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

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

macOS / Linux:

shasum -a 256 farever-companion-v0.1.8.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