Hookshot Recomp
Build time10 to 45 minutes
Game builde0f3ccfa
Linux saves~/.local/share/hookshot
Windows folderGames\Hookshot

Hookshot Recomp Setup Guide

Install from the official builder or AppImage, then point it at a legal copy of build e0f3ccfa. A build takes about 10 to 45 minutes. Linux settings and saves use ~/.local/share/hookshot.

Three-stage diagram of dump, build, and launch
Setup runs from a legal game dump, through the official builder or AppImage, to the first launch.

Windows 10 or 11

Download HookshotBuilder.exe from the v2.3.2 release and run it on 64-bit Windows 10 or 11. The default install folder is Games\Hookshot in the user folder. The builder brings its own compiler, so a separate Visual Studio install is not the path the readme describes.

1

Confirm the dump

The only supported input is program 0400486024DEC000, update v131072, build e0f3ccfa. A short dump, about 23.3 GB against a complete copy near 23.8 GB, is listed in hookshot_damaged_files.txt.

2

Leave disk space

Plan on about 60 GB free while building. An SSD is preferred. The builder warns before it uses a hard drive.

3

If security software strips tools

An unsigned builder can trip Windows Security. Restore the files from Protection history or exclude %LOCALAPPDATA%\HookshotBuilder, then press Repair.

Linux and Steam Deck

The player file is Hookshot-v2.3.2-x86_64.AppImage. It needs glibc 2.35 or newer, including Ubuntu 22.04, Debian 12, Fedora, Arch, and SteamOS, plus an AVX2 CPU. Steam Deck uses this same AppImage.

1

Run the AppImage

Allow the file to execute, then start the build against the same legal dump. The AppImage is the large file on the release, about 234.5 MB.

2

Open the save folder

Linux settings and saves use ~/.local/share/hookshot. v2.3.2 also keeps the newest 20 save backups outside the game folder.

3

Deck freeze line

A freeze in Kokiri Forest or the Great Deku Tree can be passed with RX_VK_MESH_NOCULL=2c56dc1006942f74 in hookshot_env.txt. That draws every model and skips the long cull pass.

Where the build keeps your files

1

Windows folder

Windows keeps the game in Games\Hookshot under the user folder. Saves sit in the user directory inside that game folder. The newest 20 backups are written to %LOCALAPPDATA%\Hookshot\save-backups. Linux keeps settings and saves in ~/.local/share/hookshot, with the same backup count under save-backups in that directory.

2

Update files

An update keeps those saves, hookshot_options.ini, hookshot_env.txt, and the mods folder. It replaces the game under bin, image.bin, the shader list, and language.txt. The language code you already chose is written back into language.txt. The dump from the first build stays in the game folder, so a later update does not ask for the game files again.

3

Builder cache

The builder cache is %LOCALAPPDATA%\HookshotBuilder on Windows and ~/.cache/hookshot-builder on Linux. From the AppImage, pass --update and the game folder. The previous build files are cleared first, so the update takes about as long as the first build. Keep one extra copy of the save folder if you want a backup beyond those 20. The readme license is GPL-3.0-or-later. Hookshot reimplements the console OS and replays Switch 2 graphics on Vulkan. It is a static recompilation, not an emulator.

After the first launch

hookshot_log.txt in the game folder holds the last run. Older runs rotate through hookshot_log.1.txt to hookshot_log.4.txt. Language is the code in language.txt in the game folder. The project is a static recompilation, not an emulator, and the readme calls it experimental: some PCs hold 60 fps and others stay under that, especially in Hyrule Field.

Questions

Where are Hookshot saves on Linux?

The readme puts Linux settings and saves in ~/.local/share/hookshot. v2.3.2 keeps the newest 20 backups outside the game folder, so a bad exit does not have to wipe the only copy.

Sources