%name% in config.vdf

[d10sfan]

Discussed in #267

^{Originally posted by PhasecoreX January 6, 2024}
When I select "Luxtorpeda" in Steam's compatibility dropdown, everything works as expected, however in the /home/phasecorex/.var/app/com.valvesoftware.Steam/.local/share/Steam/config/config.vdf file (I'm using Flatpak) it shows up as %name%:

...
				"CompatToolMapping"
				{
					"0"
					{
						"name"		"proton_experimental"
						"config"		""
						"priority"		"75"
					}
					"13240"
					...
					{
						"name"		"%name%"
						"config"		""
						"priority"		"250"
					}
					...
				}
...

13240 is the ID for Unreal Tournament: Game of the Year Edition, but it happens with the other games in my library as well. If I switch it to "Proton Experimental", the %name% in this config file does indeed switch to proton_experimental, but switching back to "Luxtorpeda" it saves it as %name%.

Normally I would have never known it was doing this, as Luxtorpeda still launches and works as intended. I discovered it by using ProtonUp-Qt: it shows that %name% when you click the "Show game list" button in the dropdowns for the games. Even weirder, if I use ProtonUp-Qt to manually switch it to luxtorpeda when Steam is closed, opening Steam and checking the game will shows that the forced compatibility is turned off. Checking it back on and selecting "Luxtorpeda" puts that %name% back in there.

Didn't know if this was a Steam thing, or a Luxtorpeda thing, or maybe a Flatpak thing, but wanted to bring it up. Has anyone else run into this before? Is there a way to fix it so it says luxtorpeda in the config? It's kinda weird, usually %% looking strings are variables...

[d10sfan]

It looks like this is because the compatibilitytool.vdf isn't being updated properly in the build steps for some reason. I'll look into that when I can. Note that fixing this will mean games will lose the compatibility tool and have to be setup again.

Making a note here to make sure to add that to the release notes.