Save the evidence before you relaunch

The developer’s instructions

A · ARTDOCK BARD · OCTOBER 16, 2026

In a Steam review reply, a developer requests reproduction steps, expected behavior, host/client role, screenshots or video, and Player.log. They warn against launching again before collecting the log. Source: Developer bug-report reply and player follow-up ↗.

The supplied Windows location is:

C:\Users\UserName\AppData\LocalLow\ArtDock\Hands Over\Player.log

Replace UserName with your Windows account folder. This is a developer-published path, not one inspected on your computer.

Preserve a copy in Windows

1. After the failure, avoid opening the game again.
2. In File Explorer, open the developer-specified folder for your Windows account.
3. Copy Player.log to a separate folder and give the copy a date and incident label. Do not edit the original.
4. Write down the time, game edition and host/client role while you remember them.
5. Review a copy for account identifiers, personal paths or other private details before sharing.
6. Use the developer’s official community route to submit the report yourself.

These file-handling steps are our practical interpretation of the developer’s instructions. They do not collect or upload anything automatically. If the folder is absent, record that fact and your environment rather than creating a fake log or downloading a purported repair tool.

Brown-screen report: what actually changed

C · ONE PLAYER’S FOLLOW-UP · OCTOBER 23, 2026

The original reviewer reported a brown screen on launch on October 16. In an October 23 follow-up, that player said a newer update resolved their problem. This supports a historical report and an individual resolution, not a universal fix or a verified patch version.

If you see the symptom now, include the current date and build in a fresh report. Do not assume a seven-day-old follow-up explains the cause of your current failure. A visually similar blank screen may have a different cause.

Make the report reproducible

Describe a small sequence another person could repeat: launch the named edition, choose a specific option, join as host or client, then identify the exact point at which the result changes. Separate the error text from your interpretation of it. “Could not join host after selecting the lobby” gives a clearer starting point than “multiplayer broken.”

Preserve one successful attempt and one failed attempt if they differ only in one condition. For intermittent faults, report the number of attempts and the number of failures; do not convert that small sample into a universal failure rate. Use the copyable report template to organize the details.