Hookshot Game Files: .nup, romfs & exefs Explained

Two supported input choices

romfs holds the game’s file data; exefs supplies executable content used by the build. Keep the pair consistent. An unrelated update or another game’s folder is not interchangeable.

• A .nup file from your own game at the exact supported version.
• Both romfs and exefs folders from that same supported version. Choosing only one folder is not the complete input.

your-game.nup

romfs/
exefs/

Select inputs in Builder

1. 1

   Keep your original game input in its own folder.

2. 2

   Choose .nup file, or romfs and exefs in the Builder UI.

3. 3

   Browse to the file or to each requested folder. Windows may also list found .nup files automatically.

4. 4

   Wait for the version check, then choose a separate output location and the game language.

Where output and saves go

The build reads the original game without changing it. It writes to the chosen output folder and Builder’s working folder. Where the disk permits, romfs can be hard-linked instead of copied.

Windows saves are in user inside the game folder. Linux saves are in ~/.local/share/hookshot. Back them up privately before updates. Settings are kept in hookshot_options.ini in the game folder.

The current build keeps the input data needed for updates in the game folder, so the original .nup is not needed again for the launcher’s normal update flow. Still keep a private backup of your original files.

What not to share in a bug report

Do not upload .nup, romfs, exefs, keys, game executables, generated C, shader caches or saves. The project explicitly requires game files and everything generated from them to stay on your PC.

The contribution guide permits hookshot_log.txt and relevant screenshots or videos for reports. Inspect attachments for personal information, and include the release, hardware and steps needed to reproduce the problem.