Rat Game · Reviewed Oct 31, 2026

Rat Game Player.log Location on Windows and macOS

Quick answer

For a Rat Game bug report, attach Player.log and describe the symptom. The developer lists Windows at %USERPROFILE%/AppData/LocalLow/Sokpop/Rat Game/Player.log and macOS at ~/Library/Logs/Sokpop/Rat Game/Player.log.

Version and source details

Guide context: For a Rat Game bug report, attach Player.log and describe the symptom.

Game version and evidence scope: Steam launch / October 30, 2026 FAQ; evidence checked October 31, 2026; no independent GGClue gameplay test.

Last reviewed: Oct 31, 2026

Sources and evidence scope

  • current official FAQofficial developer Steam announcements · Tier A · checked Oct 31, 2026

    Supports: Developer-published launch or patch information cited in the approved guide; no universal recovery result is inferred.

  • Steam store and platform availabilityofficial Steam store listing · Tier A · checked Oct 31, 2026

    Supports: Official game identity and release or platform context.

Original GGClue editorial decision diagram for Find Player.log for a Rat Game bug report; not game UI.
Find Player.log for a Rat Game bug report. Original evidence-based guide diagram; not a gameplay screenshot.

Find the log on Windows

  1. Close Rat Game after reproducing the error, so the log is not still being written.
  2. Open File Explorer and paste %USERPROFILE%\AppData\LocalLow\Sokpop\Rat Game\Player.log into the address bar. If the file opens in an editor, make a copy before changing anything.
  3. If the path is missing, check that you are using the correct Windows account and that the full game has been launched. Do not create a dummy Player.log; an empty file cannot document a crash.

Find the log on macOS

  1. Exit the game.
  2. In Finder, open Go → Go to Folder, and paste ~/Library/Logs/Sokpop/Rat Game/.
  3. Look for Player.log. Copy it to a temporary location if you need to attach it to a private bug report; keep the original unchanged.

What should accompany the log?

Sokpop’s launch FAQ specifically asks whether you were the host or someone joining another player’s lobby. Include the symptom, platform, when it occurred, whether it happens again, and the visible build if known. If the issue is a join failure, first check the documented lobby visibility instructions.

The FAQ lists an official developer bug-report email address. Follow the contact information in the current official FAQ rather than trusting an arbitrary third-party upload form. Logs may contain account identifiers, paths, or system information: read them first and do not post raw logs publicly.

FAQs

Will deleting Player.log fix a crash? No developer source cited here recommends deleting the log as a repair step. It is diagnostic evidence.

Is this an in-game save file? No. The official FAQ calls it Player.log for bug reports, not progress recovery.

Does the developer guarantee a fix once I submit the log? No. The log helps reproduce and diagnose an issue; it is not a support SLA.

Sources

Source-checked October 31, 2026. Original directory-path diagram, not a screenshot of Windows, macOS or the game.

A useful crash report without exposing account data

The developer’s published bug-report instruction asks for the actual Player.log and a symptom description. On Windows the %USERPROFILE%\\AppData\\LocalLow\\Sokpop\\Rat Game\\Player.log path is a user-specific file location, not a command to paste into the game console. The macOS log has a different Library path. Include the game version, whether the fault occurred before a menu or during a live match, steps to reproduce and an exact error if displayed.

Before sharing a log publicly, check whether it contains usernames, local directories, IP addresses or other private data. Prefer the developer’s authorized report channel and redact sensitive information where appropriate. Success: an actionable report with the correct log and steps; submitting a report is not the same as the bug being fixed.