Uzumi18

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

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

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

Gamemode vanilla is no longer supported by the game. its better to leave it blank or use survival (blank is default survival) do not use the "random seed" under wipe for this config, its currently broken and can result in negative seeds which is again not supported by the game Edit: Have sendt Dennis the required changes to fix this which hopefully he will apply when he has time

This was also very easy to solve, Simply change the executable from RustDedicated to the runds.sh file (it should have been like that all along) then when installing carbon you inject the code from the carbon.sh to the runds.sh. really all it needs is the "source" line

I have made the changes required to make the wipe schedule fully adjustable and fixed some mistakes when it came to the regular wipe mechanic. I have not looked into the carbon part though. Files and information has been sent to Dennis so that he can proof read it and upload it if he wish to this template

Force wipe is indeed still every first thurday of the month at 8pm for us (If i am correct in you being danish) Most server are however weekly or biweekly wipe and setting this up in tcadmin is nearly impossible as its monthly schedule is day 1 - 31 and not named and we cannot use weekly schedule either as then the first thursday would have two wipes. the schedule on forced would need to use what you have made which wipes, updates. but the update part is not required nor wanted on other wipes Edit to clarify If you could make copies of your wipe script and without the update feature (maybe have it as a toggle) add a Wipe every first thursday (this is your current) at 8pm Wipe every second thurday (whatever time user sets the script to run at) wipe every third thurday (whatever time user sets the script to run at) wipe every fourth thursday (whatever time user sets the script to run at) wipe every fift thursday (whatever time user sets the script to run at)

Thank you for this Dennis, Is this file still in use? I see that the function Wipe at force is now included in the standard Rust config. If this is still being worked on i would like to request that Carbon gets added as its starting to replace oxide/umod and is gaining alot of popularity I did some prework on the update script for carbon but without really looking into how do some things in python i couldnt advance, here is what i have so far https://pastebin.com/bCijH2Tb (This is based off your oxide script) https://codefling.com/carbon/carbon https://github.com/CarbonCommunity/Carbon/releases/tag/production_build Would it also be possible to setup a way to wipe weekly and bi weekly? Having to make 4 wipe scripts seems very tedious