Pre-build checklist

  • Confirm the exact game identifiers on the supported-version page.
  • Use one complete .nup, or a matching pair of romfs and exefs folders from your own supported game.
  • Allow about 60 GB free, use a writable output folder, and keep the original input intact.
  • Use the current official Builder for your operating system; it includes the normal build toolchain.

Start the build

  1. 1

    Open Builder and select .nup or the two game folders.

  2. 2

    Wait for validation. Do not continue with an unsupported build or substitute unrelated folders.

  3. 3

    Choose the game language and output folder, then select Build / Build the game.

  4. 4

    Allow compilation to complete. The official estimate is 10–45 minutes, not a timing promise for your PC.

  5. 5

    At Your game is ready, use Play. For later sessions open the launcher in the output folder.

01Your own game files
02Local compilation
03Native game + launcher

Understand the build output

The source game is read without being changed. Windows Builder data lives under %LOCALAPPDATA%\HookshotBuilder; Linux build data lives under ~/.cache/hookshot-builder. The chosen game directory contains the installation.

Current packaged builds use hookshot.exe on Windows or hookshot on Linux as the launcher. The Linux game binary itself is bin/hookshot. Source-checkout workflows can differ; use the development guide for those.

Builder retains roughly 4 GB of build files for faster updates. The Windows completion page offers Free up space; use the documented control instead of deleting arbitrary files during compilation.

Files, settings and saves: Windows · Linux · Settings files

Original tutorial illustration · AI-assisted

Files, settings and savesSourceLicense and attribution
Text description
  • Windows: Game folder / user
  • Linux: ~/.local/share/hookshot
  • Settings files: hookshot_options.ini · language.txt

If compilation stops

Record the failure stage and exact message, verify free space, input version and the current release, then consult troubleshooting. Runtime hookshot_log.txt describes a game run; it is not a substitute for the Builder’s failed-build output.

For a project issue, give the release version, OS, CPU, RAM, GPU and reproducible steps. Attach relevant text output without game data, encryption keys, generated C code or executable files.