FIRESTARTERS Keybind Problems and Restoring Default Controls

What should you try before resetting configuration files?

Install the current Steam update and test rebinding again. The October 31 notes confirm a fix affecting some keyboard configurations, including Japanese layouts. Resetting everything first can discard preferences unnecessarily when the published software correction is the relevant step.

Record which action and key fail, and whether the problem affects all bindings or just one. Include the keyboard layout in a report rather than assuming a physical keyboard model explains the whole issue.

Where did the config-reset advice come from?

In the pinned Japanese localization thread, kagerou01gata responded to a player who could not change bindings. The responder is credited as Japanese translator in the February 20 developer announcement. This attribution is different from a Steam developer badge and should not be presented as an independent gameplay test by this site.

The dated workaround identifies two G1_PLAYER_CONFIG files inside:

%LOCALAPPDATA%\Studio Kerosene\Firestarters\Configs

The original advice was to remove those files to restore defaults. A later reply said a patched build addressing the issue had been uploaded.

How can you preserve a way back if you try the fallback?

Close the game first, locate the exact files described, and make a separate backup. Moving only the matching player-configuration files out of the Configs folder preserves a reversible test. Do not remove the whole Firestarters directory, guess at similar filenames, or delete anything in a save-data folder.

Restart and check whether the defaults return. If the files do not match the description, stop rather than assuming the installation has the same layout. This site has not verified the workaround on the current build, so updating and reporting a reproducible problem remain the preferred first steps.

What should you include in a follow-up report?

State the build, Windows keyboard layout, failed binding, and whether updating changed the behavior. Explain if you attempted a reset and kept backups. The log guide explains where diagnostic files belong; it does not identify save files.

For language availability and the localization-reporting thread, see the language reference. Return to the beginner guide once your controls behave as expected.

Sources checked November 2, 2026. The reset is attributed historical support advice, not a tested current-build procedure or a save-recovery method.