Skip to content

Document frequent update checks and backend cleanup #66

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JamieW105 merged 1 commit into from
Oct 27, 2026
Merged

Document frequent update checks and backend cleanup #66

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 10 additions & 5 deletions content/user/installation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,8 +13,8 @@ If a release asset is unavailable, a successful [Windows installer workflow](htt
## Automatic Windows updates

Windows builds that include the automatic updater check GitHub Releases when
Project Manager or the editor starts, then hourly while Rustic is open, including
while a downloaded update is waiting for the apps to close. A newer release
Project Manager or the editor starts, then every two minutes while Rustic is open,
including while a downloaded update is waiting for the apps to close. A newer release
replaces the waiting update after verification. Older installations need one
manual upgrade to an installer containing this feature.
There is no account or Rust toolchain setup step.
Expand All @@ -37,7 +37,12 @@ with each editor restoring its original project. Paths with spaces and Unicode
are supported. Reopened applications run as the original user.

You can cancel closing and keep working. Close standalone games/workers separately;
installation waits for all Rustic processes from that installation. An automatic
installation waits for all Rustic processes from that installation. Once desktop
windows, games and workers close, the updater stops that installation's agent
backends, including those kept alive by external MCP clients. It checks once a
second during Setup and stops backends that clients restart, including while
optional language tools install. Backends from other installations stay running.
Reconnect the Rustic MCP server in your agent client after installation. An automatic
update request does not close windows you open afterward. If another process still
blocks a requested update after two minutes, the updater cancels the close request
and restores closed windows with the currently installed version and original
Expand All @@ -59,8 +64,8 @@ to compare releases.

For download, checksum, API rate-limit or Setup failures, inspect
`%LOCALAPPDATA%\Rustic Game Engine\updates\<installation-key>\update.log` and
`update-setup.log` in the same folder. Failed checks retry hourly while Rustic is
open or on a later launch. While waiting, `update.log` lists remaining Rustic
`update-setup.log` in the same folder. Failed checks retry every two minutes while
Rustic is open or on a later launch. While waiting, `update.log` lists remaining Rustic
process names and IDs once a minute. Retries reuse downloaded installers after
rechecking their size and checksum. If an update is waiting, close all Rustic processes;
you can also install the release manually from its GitHub page.
Expand Down
Loading