Possible to Configure Steam config.vdf path?

[mrgraff0]

First I want to say that I love the idea of this project. My particular use case is that I have some nerve damage and impairment that makes it difficult to hold a single controller for a length of time, and being able to use separate controllers in each hand on linux is great. Thank you!

Now for the question: Is it possible to configure the path CtrlAssist uses for steam's config.vdf when using the --hide option on the mux? My Steam install ended up at ~/.steam/steam/config/config.vdf instead of ~/.local/share/Steam/config.

I was able to workaround it by creating the folder path and copying over the controller_blacklist setting to ~/.local/share/Steam/config/config.vdf, but if there was a flag for overriding the default path I missed it.

Thanks again!

[ruffsl]

Hello @mrgraff0 , sorry for the late reply, github never sent me notification for new discussions.

We could add a check for a new ENV or an entry in the config to set the path. Does steam have it's own standard ENV to configure it config location, then we could just check for that instead.

BTW, what package/method/OS did you install steam with? I use CtrlAssist on NixOS and Bazzite mostly, and didn't notice any alternate default path locations for Steam's config until now.

That said, a simple symlink could do just as well for using the restore-controller_blacklist-on-stop behavior with CtrlAssist as is:

• https://stackoverflow.com/questions/1951742/how-can-i-symlink-a-file-in-linux

CtrlAssist/src/utils/hide.rs

Lines 103 to 117 in e7be894

	HiderState::Steam {
	config_path,
	added_ids,
	} => {
	if !added_ids.is_empty() && config_path.exists() {
	log::info!("Removing added IDs from Steam blacklist...");
	modify_steam_config(config_path, |blacklist| {
	for id in added_ids.iter() {
	blacklist.remove(id);
	}
	})
	} else {
	Ok(())
	}
	}