Where Does Hunt: Showdown Store Settings?
Where Hunt keeps attributes.xml and game.cfg in its install folder, and how the Linux Proton path mirrors it.
Last updated
Hunt keeps settings inside its own install folder rather than Documents: an attributes.xml in the default profile tree plus an optional system.cfg at the root. Keybinds hide as numeric codes inside the XML, readable only with patience. Hunters themselves live server side.
Linux plays through Proton with the identical tree inside compatdata. Corrupt states yield to the rename-and-regenerate trick for attributes. Server region edits in the same file dodge several notorious connection errors. Keep a known-good copy before each patch day.
Where Hunt: Showdown stores this, by platform
<install-dir>\Hunt Showdown 1896\user\profiles\default\attributes.xml
CryEngine settings with numeric keybind codes in attributes.xml, plus optional system.cfg tweaks at root. Rename to regenerate clean defaults after bad updates. Hunters stay server side; only settings transfer by file.
~/.local/share/Steam/steamapps/compatdata/594650/pfx
Proton prefix for app ID 594650 mirroring the install-relative profile tree. Continue inside pfx to the same user profiles path. The regenerate trick works identically here.
Frequently asked questions
how do I move Hunt settings to a new PC
Copy attributes.xml from the default profile folder with the game closed to move settings and binds. Hunters and progress stay server side on your account. Linux runs the same tree inside compatdata for app ID 594650.
settings broken after an update
Close the game, rename attributes.xml to a backup name, and relaunch to regenerate clean defaults. Stale values from before the 1896 update cause the oddest conflicts. Rebuild binds afterward; keep the backup until stable.
CryCloud errors, any local fix
Edit the server region lines in attributes.xml with the game closed to dodge connection errors. Switch to a reachable region, connect once, then switch back in-game. Community guides document the exact lines per incident.
Notice an outdated path? Let us know.