From a chat with one of my less technical friends, having to open the installer (not updater!) and rerun installation to update quilt loader is incredibly unintuitive. What I'm envisioning to fix this is bundling the installer inside loader, thus allowing us to provide a "update quilt loader" button on error screens. I think that this should be implemented as a red banner across every error screen when a newer stable version is detected, with an update button. On game crash we can query meta for that information.
neat!
Using this, we can then build an automatic updating system, configurable via a system property and the config file. This would allow privacy-focused users to avoid loader phoning home for any reason on game launch, which as we've learned in the past many do not like.
other details
I think we should start by building this for clients, and focus on server only after its completion. Server users are savvy enough to update, and most users are on the client anyway.
huh?
From a chat with one of my less technical friends, having to open the installer (not updater!) and rerun installation to update quilt loader is incredibly unintuitive. What I'm envisioning to fix this is bundling the installer inside loader, thus allowing us to provide a "update quilt loader" button on error screens. I think that this should be implemented as a red banner across every error screen when a newer stable version is detected, with an update button. On game crash we can query meta for that information.
neat!
Using this, we can then build an automatic updating system, configurable via a system property and the config file. This would allow privacy-focused users to avoid loader phoning home for any reason on game launch, which as we've learned in the past many do not like.
other details
I think we should start by building this for clients, and focus on server only after its completion. Server users are savvy enough to update, and most users are on the client anyway.