Where Does vkBasalt Store Its Config?
vkBasalt searches a chain of config spots, but the one to edit is ~/.config/vkBasalt/vkBasalt.conf, with per-game overrides beside the game.
Last updated
vkBasalt looks for its config in a documented chain, and knowing the chain ends most confusion. An explicit VKBASALT_CONFIG_FILE wins, then a vkBasalt.conf beside the game, then the user config folder, then data and system spots. In practice nearly everyone edits exactly one file.
That file is ~/.config/vkBasalt/vkBasalt.conf. It may not exist until you create it; grab the upstream default as a starting point. Effect strength, toggles, and keybinds all live there in plain ini style. Effects chain in order, so the file reads top to bottom like a pipeline rather than a bag of switches.
Where vkBasalt stores this, by platform
~/.config/vkBasalt/vkBasalt.conf
The per-user config to edit. Create the folder if missing and seed it with the upstream default. Per-game vkBasalt.conf files beside game binaries override it for that game only.
/etc/vkBasalt.conf
System-wide fallback consulted after user paths. Package installs sometimes ship an example here. Leave it alone and override per user instead.
Frequently asked questions
Which config file should I edit?
Edit the user config at ~/.config/vkBasalt/vkBasalt.conf for global changes. Drop a vkBasalt.conf next to the game binary for per-game tweaks, which beats the global file. VKBASALT_CONFIG_FILE beats everything for testing.
There is no config file yet. Where do I get one?
Fetch the default config from the vkBasalt repo into ~/.config/vkBasalt/vkBasalt.conf. The file documents every effect and toggle inline, so starting from defaults beats writing one from memory.
Notice an outdated path? Let us know.