Skip to main content

Replace a Rust restart script one job at a time

Read what the old script does before switching it off. One loop may handle launching, restarts after an exit and updates, and each job needs a clear owner.

Find what the old script actually runs

Write down the executable path, game options and server identity, then check whether a scheduled task or service launches the script. If the script jumps back to an update or launch step after the game exits, it can try to start the game while the new tool is trying to do the same job.

Hand over the next scheduled job first

Test on a spare copy first. Give the new tool one scheduled restart and check that only one process starts. If the old script automatically launches the game whenever it exits, disable that loop before the new tool takes over. If you cannot disable it separately, rehearse the launcher and restart together before switching them on the live server.

In the announced live window, verify one stop, one new start and a join to the original world. Leave independent jobs where they are until you can verify each transfer. Test crash recovery on a spare copy and confirm a deliberate stop stays stopped.

Sources

Analytics settings

Analytics are off.

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