Skip to main content

Will a Rust management tool do the same jobs on both your hosts?

Test the job against each host you intend to use. A rental can let a tool read Rust’s console while the start button still belongs to the rental panel. Even two rentals with a similar panel can give your accounts different access.

Write down which connection you are testing

Use a spare instance and the account that will handle the job on each host. Record whether you connected through the game’s remote console, the rental panel or software on a host you control. A successful connection only proves that route is available. Try the actual job using it.

For example, Harbour is self-hosted and Dunes is rented. You can read fresh console output for both through the manager. On Dunes the tool can see the stopped game but says it cannot start it with your current access. Use the rental panel directly and record the difference instead of changing the helper’s permissions just to make the two screens match.

Write down which connection you are testing
JobHarbourDunes
Read new console outputManager shows a fresh lineManager shows a fresh line
Start a stopped gameManager starts itOpen the rental’s panel
Change a test startup settingMake and verify the change in the managerAsk who controls the setting before altering it

Hand over the exact exception

For each job that moved to another screen, write who can finish it there. Have the person who covers the server use their own account on the spare instance. If they cannot use the fallback, revise the job they take on or ask the owner to remain available for that step.

Keep a separate result for each rental even if the panels look alike. Repeat the limited set of jobs when a connection or account role changes. Verify a start by joining the intended world and verify a startup setting still applies after the game opens.

Sources

Analytics settings

Analytics are off.

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