fix: publish component choices again when a new Proton build appears

Game and global component choices were written to desired.tsv only when a
selection changed, so a Proton build installed later (DroidDeck-Proton
11-11.8) had no rows and kept its bundled FEX. Battle.net's d2rfix FEX never
reached it and StarCraft died in ClientSdk.dll's DllMain. The choices are now
republished at session start and on Battle.net's FEX request whenever the
installed tools no longer match what was published.
This commit is contained in:
maxjivi05 authored and MaxsTechReview committed 2026-10-27 00:07:45 -04:00
1 parent 4c7e59ed8b
commit c781cfd525
4 files changed
+111 -2

No files matched your search

@@ -360,6 +360,8 @@ object BattleNet {
if (ComponentsManager.gameComponents(context, scope)["fex"] != file) {
ComponentsManager.setGameComponent(context, scope, "fex", file)
Log.i(TAG, "FEX for the Battle.net prefix: $file")
} else if (ComponentsManager.republish(context)) {
Log.i(TAG, "FEX for the Battle.net prefix: $file, now in every installed Proton")
}
return file
}