Pokee v0.4.2

Pokee for Monster Hunter Freedom Unite (USA, ULUS-10391, version 1.01). It does not include the game. On first start it asks for your own disc image and accepts only that release.

This release is for Windows x86-64 and Linux x86-64. macOS, Android and the Flatpak are not part of it.

Downloads

File	What it is
pokee-0.4.2-linux-x86_64.tar.gz	Portable Linux: pokee, Pokee, overlay libraries, SDL3, FFmpeg, the fallback font, and licenses
pokee-0.4.2-windows-x86_64.zip	Windows: Pokee.exe, overlay DLLs, SDL3, FFmpeg, the Visual C++ runtime and licenses. Keeps its data in %APPDATA%\Pokee\MHFU
pokee-0.4.2-windows-x86_64-portable.zip	The same, plus portable.txt: keeps all data in data\ next to Pokee.exe
ffmpeg-7.1.5.tar.xz	Unmodified FFmpeg source for the LGPL libraries in the Linux build
SHA256SUMS	Checksums of the Linux tarball and the FFmpeg source

Linux: sha256sum -c SHA256SUMS --ignore-missing.

Windows (Get-FileHash <file> in PowerShell):

d832f727db8037891e9d4ec68836198c8b034630257a89f243ae1361208b6fb8  pokee-0.4.2-windows-x86_64.zip
b6d982fbe012b0dc87829281bfd71d1623bdd8530e36c5094a9406b106ac4076  pokee-0.4.2-windows-x86_64-portable.zip

What changed since v0.4.1

• Quest papers stay on their hunter's name. In the Guild Hall, the quest paper and the blinking ready mark over another hunter jittered heavily and, when hunters stood close together, were pushed off their own name toward someone else's. The game files these marks with no position or with the next hunter's, and each was matched to the nearest name. Each mark is now given to the name it sits on (the paper 3 pixels right of its hunter's name and 1 pixel above it, the ready mark 7), sized with that name, and moved with it between frames, so it no longer steps at 30 fps under smoothly gliding names. MHFU_TRACE_HALL_NAMES=1 shows where each mark was placed. Commit b17c21f.

Build

Linux

Version: v0.4.2
Commit: b17c21f3e970dafff2af7262adf2c46ead9fad0a
Built: 2026-10-20
Platform: Linux x86-64
Configuration: Release; MHFU_RELEASE=ON
Build environment: Steam Runtime 3 sniper SDK
Needs glibc: 2.29 or newer
SDL3: 3.4.16
FFmpeg: 7.1.5 (LGPL)
Overlay libraries: 298

Windows

Version: v0.4.2
Commit: b17c21f3e970dafff2af7262adf2c46ead9fad0a
Built: 2026-10-20 04:04:43 UTC
Platform: Windows x86-64
Configuration: Release; MHFU_RELEASE=ON
Compiler: MSVC 19.44.35229
SDL3: 3.4.16
FFmpeg: bundled LGPL shared build (ffmpeg-n7.1.5-1-g7d0e842004-win64-lgpl-shared-7.1.zip)
Overlay DLLs: 290

The FFmpeg source for the Windows DLLs is named in licenses/FFmpeg-SOURCE.txt inside each zip.

Checked

• Linux: built from tag v0.4.2 (b17c21f) by release_linux.sh in the Steam Runtime 3 sniper SDK container. The script found no game data in the staged build or the tarball, and a separate scan of every file, binaries included, found no path, user name or computer name of the build machine.
• Linux: the tarball was unpacked into a folder of its own and booted headless for 40 seconds against a scratch data directory: Functions: 272890, and overlays installed.
• Windows: built with MSVC from tag v0.4.2 (b17c21f) with -DMHFU_RELEASE=ON. include/psprecomp/ and src/ are unchanged since v0.4.1, so the 290 overlay DLLs are the same as in earlier 0.4 builds.
• All 59 ctest unit tests passed on this machine, including new tests for two hunters side by side, a mark filed with another hunter's position or none, hunters walking, and a mark with no name under it.
• The fix was tried on a development build of this code in an online Guild Hall, walking past another hunter who had posted a quest, before tagging.
• Both zips were packed by release_windows.sh, then unpacked and checked: 290 overlay DLLs each, no game-data files, and no path, user name or email address of this machine. The script's own path search aborted inside Git Bash, as for earlier releases, so that search was repeated separately.
• The normal zip was installed from a disc image into a scratch data folder and booted headless for 40 seconds: it reports v0.4.2, Functions: 272890, and overlays installed.

Not verified

• The tagged release build itself was not played; the fix was checked on screen on a development build of the same code.
• The portable zip was scanned but not booted.
• The game was not played from the Linux tarball, and it was not run on a Steam Deck. ctest was not run in the Linux release build.
• No macOS, Android or Flatpak package for this tag.
• No full TESTING.md smoke test is recorded in COMPATIBILITY.md for this release.