FIRESTARTERS Log Location and the Public Debug Branch

Where are the current release’s log files?

Use the Windows local AppData folder, not Steam’s installed-files directory. The developer’s release support reply identifies the path below and notes that AppData may be hidden. The environment-variable form avoids requiring you to substitute a Windows account name into an absolute path.

%LOCALAPPDATA%\Studio Kerosene\Firestarters\Logs

Press Windows + R, paste the path, and open it. Reproduce the issue first so you can identify a log from the relevant attempt. Preserve the original file while preparing a report, and review the text for personal details before sharing it publicly.

What if the folder does not exist?

Tell the developer that no folder or log was created, rather than searching only the game installation repeatedly. In the same support thread, the developer explained that a failure can occur before systems such as the file system finish initializing. Missing logs therefore provide useful diagnostic context rather than proving that the game launched successfully.

Older demo discussions use a folder named Firestarters Demo. Do not silently substitute that historical location for a release installation. A stale log from another version may describe an unrelated failure.

How do you access the developer’s diagnostic branch?

The developer described Steam’s game Properties, then Game Versions & Betas, as the place to select public-debug. Their October 31 reply announced diagnostic build 0.2.2.6 with additional initialization-error popups. That version number is a dated announcement, not a promise that the branch still contains that exact build today.

Use it as an optional diagnostic step when relevant to the developer’s instructions. Record which branch you tested and the resulting error. This page does not claim the branch is faster, more stable, or required for ordinary play.

What makes a bug report useful?

Include the sequence of actions, whether any window appeared, the complete popup text, the selected branch, your GPU and audio setup, and a log from the failed attempt if available. State what changed between a successful launch and a failed one, rather than listing fixes that you cannot remember testing.

The GPU error guide covers a documented detection regression. The audio page covers another launch failure with a different cause. For general compatibility, consult the requirements table.

Developer instructions checked November 2, 2026. No local files are collected by this website, and no debugging branch is installed through this page.