mirror of
https://github.com/ValveSoftware/Proton.git
synced 2025-01-15 16:18:20 +03:00
0abb95b7e7
This matters for builds dropped into compatibilitytools.d/. Steam uses the internal tool name to detect it's Proton and alters some behavior regarding how cloud saves work. Not including Proton in the name may lead to confusing behavior regarding saves where they are present on some builds but vanish on the other, only to reappear when switching back.
24 lines
704 B
Plaintext
24 lines
704 B
Plaintext
"compatibilitytools"
|
|
{
|
|
"compat_tools"
|
|
{
|
|
"##INTERNAL_TOOL_NAME##" // Internal name of this tool
|
|
{
|
|
// Can register this tool with Steam in two ways:
|
|
//
|
|
// - The tool can be placed as a subdirectory in compatibilitytools.d, in which case this
|
|
// should be '.'
|
|
//
|
|
// - This manifest can be placed directly in compatibilitytools.d, in which case this should
|
|
// be the relative or absolute path to the tool's dist directory.
|
|
"install_path" "."
|
|
|
|
// For this template, we're going to substitute the display_name key in here, e.g.:
|
|
"display_name" "##BUILD_NAME##"
|
|
|
|
"from_oslist" "windows"
|
|
"to_oslist" "linux"
|
|
}
|
|
}
|
|
}
|