windows/linux Rust - Automatic wipe/update, Oxide, Plugin Installer

[striker99]

Hi, the script to use 3 cores on startup does not work on Linux. Is it possible to add it to the Linux version?

Thanks

[Dennis]

The script is only meant to work on Windows. I couldn't find a way to do the same thing on Linux, unfortunately.

[striker99]

Randomly, the game servers are left with low affinity.

It is somewhat difficult to follow, because it is random and not easy to detect, you have to look at process by process.

[Dennis]

When that happens, check the server log. It should have "Server startup complete" - if it doesn't affinity and priority won't be changed back.

[striker99]

If the message appears in the log, but the server is still in low affinity.

I suspect it has to do with the automatic restart that tcadmin runs in a cron.

 

[Dennis]

I haven't been able to reproduce the issue, even with scheduled restarts. Is it always happening for the same service? Have you checked if it has custom affinity defined?

[striker99]

Yes, note that it happens with the same services, that is, out of 15 rust servers, it happens with 2 or 3.

It is possible that the affinity has been changed to high for one of these services, but now it is normal, I don't know if that may have generated an error.

It's very strange, how does the script to return to normal affinity work properly? does it read the server log?

thx

[striker99]

How can I override the affinity part of the script?

[xvkevin]

Hello,

I need some help. 

Everything in terms of wipe removing all bps, changing map etc, works fine for me. However when it does the update it seems like it does it, but it doesn't. The server then starts up fine, but then players can't connect because their is a mismatch and the server didn't auto update.

I then have to come in and manually shut it back off and run the steam update which then fixes it. 

(Running windows server)

It's the only issue I am currently having with the auto wipe, as I want to try and automate the wipes as best as I can. Just because I am not always online to see to the server when wipe.

Any help would be greatly appreciated.

Thanks

Kev

[Uzumi18]

On 11/10/2025 at 7:04 PM, xvkevin said:

Hello,

I need some help. 

Everything in terms of wipe removing all bps, changing map etc, works fine for me. However when it does the update it seems like it does it, but it doesn't. The server then starts up fine, but then players can't connect because their is a mismatch and the server didn't auto update.

I then have to come in and manually shut it back off and run the steam update which then fixes it. 

(Running windows server)

It's the only issue I am currently having with the auto wipe, as I want to try and automate the wipes as best as I can. Just because I am not always online to see to the server when wipe.

Any help would be greatly appreciated.

Thanks

Kev

In-case you haven't fixed this yet, you need to remove the -beta branch from the steamcmd, this was only needed from 2014-2016

Attached is the linux config for rust with the seed fix which causes rust+ to not render a map, beta branch fix so steamcmd will update the game if triggered through any of the wipe scripts.

Added Carbon support with the mod installer / updater.

Added proper server auto wipe script, Select it under schedule > Wipe Schedule

Select which day the script should run under the script parameters, then which day of the month it should run, first - fifth
For example Mondays (first, second, third, fourth and fifth) of the month

Added Mod updates to every wipe files, Will check if user has oxide or carbon installed and update the correct one

 

Rust - Linux.xml

Edited 22 hours ago by Uzumi18
Fixed a carbon injection in the wipe script

[Dennis]

1 hour ago, Uzumi18 said:

In-case you haven't fixed this yet, you need to remove the -beta branch from the steamcmd, this was only needed from 2014-2016

It's not a beta branch, the `-beta` parameter is just used for changing branch. If you do `-beta staging`, you're running the staging branch. The value of the "beta" variable defaults to public. It's rarely used but there's no reason not to have it. 

I'll take a look at the other things as soon as I have time.

 

[Uzumi18]

20 minutes ago, Dennis said:

It's not a beta branch, the `-beta` parameter is just used for changing branch. If you do `-beta staging`, you're running the staging branch. The value of the "beta" variable defaults to public. It's rarely used but there's no reason not to have it. 

I'll take a look at the other things as soon as I have time.

 

I thought so too, but the steamcmd script from wipe throws an error with it in and doesn't perform the steam update (Manually running steam update works fine), Once removed the script ran fine, you can probably find a tweak around it, but removing it seemed the easiest solution

[Dennis]

13 minutes ago, Uzumi18 said:

I thought so too, but the steamcmd script from wipe throws an error with it in

What was the error? Are you sure that the "branch" variable had a value?

[Uzumi18]

1 minute ago, Dennis said:

What was the error? Are you sure that the "branch" variable had a value?

I honestly don't remember what error it caused, just that it was an error and steam update was aborted, But running steam update worked fine, So the problem lies somewhere with how the wipe server handled the steam update