Hookshot Builder

What you hand it

Windows starts HookshotBuilder.exe. Linux starts the same program from inside the AppImage. Both call the script nx2/make_game.py. The accepted input is a .nup file, or a romfs folder plus an exefs folder. The readme says the only working game is update v131072, build e0f3ccfa. Anything else stops with the line that Hookshot supports build e0f3ccfa.

On Windows the window looks in Downloads, Desktop, and Documents for a .nup. You can also browse, drag the file in, or point at the two folders. You pick an output directory, which defaults to Games\Hookshot, and a language. The language is written to language.txt. Build time on the readme's range is 10 to 45 minutes. The machine wants about 60 GB free while it works, and an SSD is called out because a hard disk slows the compile. Memory guidance is 16 GB or more, with the running game using about 10 GB.

What you get back

The finished folder holds hookshot.exe plus a bin directory. The installer also offers a desktop shortcut and a Start menu entry. Intermediate files are about 4 GB and are deleted when the build finishes. Set HOOKSHOT_KEEP_BUILD_FILES=1 if you need to keep them. Later, the launcher can show Update available. It downloads only the changed pieces, then builds again for about as long as the first time, and it keeps saves and settings.

If security software deletes a build tool, the readme says to restore it from Windows Security protection history, or to exclude the Hookshot tools folder, then press Repair. I do not host a zip of those tools here. The release page is the source.

Sources

How we check pages

Related