Skip to main content

Try a management tool update on one Rust host first

If your management tool has an update you install on each host, start with one that uses the features you need to check. For example, use a spare home instance for your local start and stop routine. Check a rental separately if you manage it through a different connection.

Pick the results that let you continue

Record the manager version you already use and check how its publisher says to return to it if necessary. Pick a few tasks that must work on the first host. For example, read current game output, send a harmless message and review the next scheduled run. If you depend on the tool to start a stopped game, do a test start too.

Before applying the update, see whether it requires stopping the game or changing host settings. Use a quiet window or the spare host if it does. This rehearsal is for the management tool. Keep the game version steady so you can tell what changed.

Wait for one regular job if it matters

Check the updated host through a normal use of its most important scheduled job before moving to the others. If you see an unexpected stop, missing schedule or a setting changed on the wrong world, pause the rollout. Use your known working host route while you check the update or ask for support.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details