Safe first checks
- Preserve the current save before changing files or testing a workaround
- Exit the current interface and restart the Playtest session
- Confirm Steam has applied the latest available Playtest update
- Compare the issue with recent reports in official Steam Discussions
- Include the affected interaction and current build context when reporting a reproducible problem
These checks avoid assuming that a bug report from an older build still describes the current game.
Current player-problem signals
Recent discussion topics include a Ribwich issue, a lock involving Johnathan Wild, a Simplified Chinese translation report, locked Security Crates and interactions involving Lottery Tickets. Topic titles show that other players are asking; they are not themselves verified fixes.
Save-file reference
SteamDB currently identifies save files beneath %USERPROFILE%/AppData/LocalLow/Questing Goose Studio/Probably Stolen and shows .es3 files.
Use that location only to make a backup or provide context for support. Do not delete saves as a default troubleshooting step.
Reporting a Playtest problem
State what you were interacting with, what happened instead, whether restarting reproduced it and which language or starting path was active. A precise current-build report is more useful than a speculative workaround.