One press in the Insert menu that saves everything a bug report needs #2346

Closed
opened 2026-11-11 15:21:57 +00:00 by mooki000 · 1 comment
mooki000 commented 2026-11-11 15:21:57 +00:00 (Migrated from github.com)

The idea

A bug report on the game problem form needs things a player has to look up by hand today: the Hookshot version (the launcher, or the first line of hookshot_log.txt), where in the game he was, the graphics card and its driver version, CPU, RAM and operating system, the Insert-menu options and hookshot_env.txt lines he changed, hookshot_log.txt, and after a restart also hookshot_log.1.txt, because the restart moved the crashed run's log there. The log itself does not answer most of it: it gives the driver only as Vulkan's packed number (driver 0x99d38200), has no line for the system, the CPU, the options or the place, and its paths name the player's home folder. Reports that arrive without the log are scored at confidence 0.4 in docs/workflow.md, and the first answer has to ask for it.

The idea: a row Gameplay → Bug report in the Insert menu. One press saves a folder bug-reports/<date>_<time>/ in the game folder with:

  • report.txt: the form's answers under the form's own headings (version, the map the player is in, graphics card and driver, CPU, RAM and system, the options and switches changed from their defaults), and a link that opens the form with them filled in;
  • hookshot_log.txt and hookshot_log.1.txt (this run's and the run before's), with the home folder and the user name taken out of their paths;
  • picture.png: the game's picture at that moment, without the menu.

Nothing is sent anywhere, and no saves, no game files and not the options or env files go in: the player opens the form, writes what happened, and drags the folder's files in.

Anything else

Claim: I am working on this (#2347 is open with it, its test and pictures). Severity S3 (a feature, weight 1); it should raise the share of reports that come with a log and the hardware, which docs/workflow.md asks for first. Hardware I can test on: Linux, RTX 4090 with NVIDIA 615.78.08, and Intel UHD 770 with Mesa 26.2.5; not Windows.

### The idea A bug report on the game problem form needs things a player has to look up by hand today: the Hookshot version (the launcher, or the first line of `hookshot_log.txt`), where in the game he was, the graphics card **and its driver version**, CPU, RAM and operating system, the Insert-menu options and `hookshot_env.txt` lines he changed, `hookshot_log.txt`, and after a restart also `hookshot_log.1.txt`, because the restart moved the crashed run's log there. The log itself does not answer most of it: it gives the driver only as Vulkan's packed number (`driver 0x99d38200`), has no line for the system, the CPU, the options or the place, and its paths name the player's home folder. Reports that arrive without the log are scored at confidence 0.4 in `docs/workflow.md`, and the first answer has to ask for it. The idea: a row **Gameplay → Bug report** in the Insert menu. One press saves a folder `bug-reports/<date>_<time>/` in the game folder with: - `report.txt`: the form's answers under the form's own headings (version, the map the player is in, graphics card and driver, CPU, RAM and system, the options and switches changed from their defaults), and a link that opens the form with them filled in; - `hookshot_log.txt` and `hookshot_log.1.txt` (this run's and the run before's), with the home folder and the user name taken out of their paths; - `picture.png`: the game's picture at that moment, without the menu. Nothing is sent anywhere, and no saves, no game files and not the options or env files go in: the player opens the form, writes what happened, and drags the folder's files in. ### Anything else Claim: I am working on this (#2347 is open with it, its test and pictures). Severity S3 (a feature, weight 1); it should raise the share of reports that come with a log and the hardware, which `docs/workflow.md` asks for first. Hardware I can test on: Linux, RTX 4090 with NVIDIA 615.78.08, and Intel UHD 770 with Mesa 26.2.5; not Windows.
NotRexed commented 2026-11-11 21:31:36 +00:00 (Migrated from github.com)

This is being done in your pull request #2347; closing the issue so the work is tracked in one place there.

This is being done in your pull request #2347; closing the issue so the work is tracked in one place there.
Commenting is not possible because the repository is archived.
No milestone
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Hookshot#2346
No description provided.