From 7033d63af134177a117967e05676cbd8a02a75ec Mon Sep 17 00:00:00 2001 From: chrg6 Date: Sun, 8 Nov 2026 08:55:34 -0500 Subject: [PATCH] After a rollback, show why the version went back instead of finishing the failed update. When a new version did not start, the stub started the previous one with --rolled-back and the same arguments, --continue-update among them: the previous version then ran the update's rebuild as if it were the new one, and the "Version X did not start" notice on home never showed. A rolled-back start now goes to home with the notice. Co-Authored-By: Claude Opus 5.5 --- launcher/ui/app.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/launcher/ui/app.py b/launcher/ui/app.py index 86bc803c..f3536dea 100644 --- a/launcher/ui/app.py +++ b/launcher/ui/app.py @@ -473,7 +473,9 @@ class App: self.fonts_from_game(gd, self.settings.get('dump')) if a.uninstall: self.show('uninstall') - elif a.continue_update is not None: + elif a.continue_update is not None and not a.rolled_back: + # after a rollback the stub passes the failed version's --continue-update on to this one: the game was + # never rebuilt for the new version, so there is nothing to finish, and home tells why the version is back self.run_job(jobs.ContinueUpdateJob(self.ctx, gd if gd and build.built_version(gd) else '', a.continue_update, self.settings.get('dump')), 'home') elif gd and build.built_version(gd):