Jump to content

1 Screenshot

  • 47.7k
  • 202
  • 7.53 kB
This area is for discussion and questions. Please use the support area for reporting issues or getting help.

Recommended Comments

MightyBeard

Posted

is it possible to have it like {
      "Minute": "@restart",
      "Hour": "*",
      "Day": "*",
      "Month": "*",
      "DoW": "2-5",
      "Command": "oxide.unload name"
    },
To have it being unloaded for several days?

kasvoton

Posted

Yes that should work.

  • Like 1
golgolakk

Posted

has anyone tried this plugin in Carbon? thanks

kasvoton

Posted

On 6/9/2023 at 7:46 PM, golgolakk said:

has anyone tried this plugin in Carbon? thanks

@golgolakk It will work just fine with Carbon.

  • Like 1
private_wire

Posted (edited)

I have your Automatic wipe plugin and i am currently using two profiles, weekly and full.
I'm using a pterodactyl panel to schedule to weekly wipes, but im unsure how to perform the full wipes.

I wish for the weekly wipe profile to execute every THU except for the first THU of the month, and the full profile to execute on the first THU of every month. Can this be done with this plugin?

I see you have added the @forced wipes, but how is @forced determined? 
Any help would be appreciated

EDIT: Found my answer, for anyone else:

@forced is equal to the first Thursday of the month. This would require the server to be running in an appropriate time zone, for me, I'm in Australia and forced wipe is on a Friday. So, I had to change the time zone of the server to 'Europe/London' the default Rust timezone. This now works as expected.

@wipe equals true if the server has created a new save file this restart.  

Great plugin, recommended!

Edited by private_wire
  • Love 1
C7_4K

Posted

Harmony Plugin ?? no need oxide to install ?

  • Like 1
kasvoton

Posted

I think I can provide a harmony version for it.

Nomad3211

Posted

I am interested in this plugin, however: My server is on a bi-weekly Wipe schedule.  
How do I configure this plugin to only run the wipe command On ONLY the first and third Thursday of each month? 
If that can be sorted - you have a sale on this and the wipe plugin 😄

kasvoton

Posted

Yeah "bi-weekly" has been a requested feature.. right now it's not supported.
I will work on this.

  • Like 1
Žéŧ

Posted

Good afternoon. I would like to know if this configuration is valid so that the wipe is only on the first Thursday of the month, thank you.
"Cron": [
     {
       "Minute": "0",
       "Hour": "16",
       "Day": "1-7",
       "Month": "*",
       "DoW": "4",
       "Command": "wipe forced"
     }

kasvoton

Posted (edited)

You have a special "command" to deal with forced wipe.

{
"Minute": "0",
"Hour": "16",
"Day": "*",
"Month": "*",
"DoW": "4",
"Command": "@forced wipe forced"
}

 

Edited by kasvoton
  • Like 1
Žéŧ

Posted

Show, tks...

  • Like 1
Žéŧ

Posted

Good afternoon. It's me again. I would like to know if this configuration is valid so that cleaning only takes place on the third Thursday of the month, if the day configuration can cover a period of one week and only run if the date falls on a Thursday, thank you for your attention.

"Cron": [
     {
       "Minute": "0",
       "Hour": "16",
       "Day": "15-21",
       "Month": "*",
       "DoW": "4",
       "Command": "wipe forced"
     }

Wodan

Posted

maybe add a command so we can see when the next scheduled command happends

  • Like 1
DodgeMan

Posted

Can you put multiple instances of commands under 1 day. For example 

    {
      "Minute": "*",
      "Hour": "*",
      "Day": "*",
      "Month": "*",
      "DoW": "6",
      "Command": "oxide.unload TrainYardEvent"
    },

 

Can you make it so its like

    {
      "Minute": "*",
      "Hour": "*",
      "Day": "*",
      "Month": "*",
      "DoW": "6",
      "Command": "oxide.unload someplugin", "oxide.unload anotherpluginhere", "oxide.unload yetanotherpluginhere"
    },

 

Or how would I go about doing this instead of adding more lines to the config for each plugin?

kasvoton

Posted

You need to have one command per entry.. so to do what you require, you would need multiple entries one per each command.

DeltaEremita

Posted

On 2/20/2024 at 7:48 AM, kasvoton said:

You need to have one command per entry.. so to do what you require, you would need multiple entries one per each command.

Hello there! how you doing? I have a question: In comments, people say about bi-weakly been not possible, however, if I use the Cron, minute... hour, day... I can set to wipe Bi-Weakly, right? The feature about Bi-Weakly you guys were taling about was the @bi-weakly thing, right?

theoutpost

Posted

Does this plugin support a countdown to wipe? e.g. execute (x) command -72 hours from wipe, or days etc. 

Deisel

Posted

Very helpful plugin, thankyou.

Would be even more amazing if in future updates it was able to be configured to trigger prior to wipe, not using rust timezones but by using our wipe schedule somehow.. 

Heres mine:

[10:48:07] Transmitting console input: printwipe
[10:48:07] Frequency: BiWeekly
Timezone: AEST (ID=Australia/Queensland, IANA=Australia/Queensland)
Wipe day of week: Friday
Wipe hour: 16
Test time: 2024-06-29T10:48:07.9637450+00:00
Wipe time: 2024-07-05T16:00:00.0000000+10:00
Time until wipe: 5:19:11:52.036255
Ticks until wipe: 5011120362550
Cron: 0 16 1-7,15-21,29-31 * 5

be good if we could execute a command xminute-xhours-xdays-dow "@beforewipe" or "@before forcewipe"

Just a suggestion i myself would find very helpful.

Thanks again!!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

User Feedback

1.6m

Downloads

Total number of downloads.

7.7k

Customers

Total customers served.

115.6k

Files Sold

Total number of files sold.

2.4m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.