TimedExecute [Unmaintained]

Thanks!, i use taskkill in a batch file atm, but last week it seemed to corrupt the map, so i imagine TimedExecute would be the answer, as the restart command is a much safer method

 

you can just run the command server.save before the restart like 10 secs if you want to be 100% safe

 

For any Admins on a Multiplay/Clanforge servers wanting to use TimedExecute.

Adding the plugin to your server creates a config file named "timedexecute.json" but this is the incorrect name. Upload you config in a file named
"p-timedexecute.json" and it should work fine.

 

Decided to do an arena every two days with a server restart after the arena has ended.

I don't think the reset.oncetimer is needed at the end, because the server restart should reload it fresh and start the countdown when the plugin is reloaded. Just in case though, I added it in.

Should you use this, I would manually run an arena at the time that you would like yours to be from now on (roughly) and then do a server restart with this config. That way, your arena will (roughly) be at that time 2 days from now.

Server restarts take a bit, so eventually you'll have to 'reset' your time to get back on track.

Also has a repeater command that refreshes NPCs every 4 hours.

Code:

{
  "ConfigCode": "1",
  "EnableTimerOnceCommands": "true",
  "EnableTimerRepeatCommands": "true",
  "OnceCommands": [
  {
  "command": "say '<color=orange>Deathmatch</color> Next registration in 5 minutes!'",
  "seconds": 169800
  },
  {
  "command": "event.game Deathmatch",
  "seconds": 170096
  },
  {
  "command": "event.spawnfile tikiDM",
  "seconds": 170098
  },
  {
  "command": "event.open",
  "seconds": 170100
  },
  {
  "command": "say '<color=orange>Deathmatch</color> will start in 5 minutes! Use /event_join to join!'",
  "seconds": 170100
  },
  {
  "command": "say '<color=orange>Deathmatch</color> will start in 4 minutes! Use /event_join to join!'",
  "seconds": 170160
  },
  {
  "command": "say '<color=orange>Deathmatch</color> will start in 1 minute! Use /event_join to join!'",
  "seconds": 170340
  },
  {
  "command": "event.start",
  "seconds": 170400
  },
  {
  "command": "say '<color=orange>Deathmatch</color> Event has started. Registration closing in 2 minutes! Use /event_join to join now!!!'",
  "seconds": 170400
  },
  {
  "command": "say '<color=orange>Deathmatch will end in 30 mins, if no one wins by then. Good Luck!</color>'",
  "seconds": 170405
  },
  {
  "command": "event.close",
  "seconds": 170520
  },
  {
  "command": "event.end",
  "seconds": 172200
  },
  {
  "command": "say '<color=orange> Server will restart in 10 minutes! Buy your rewards from the arena and get someplace safe!</color>'",
  "seconds": 172205
  },
  {
  "command": "say '<color=orange> Server will restart in 1 minutes!</color>'",
  "seconds": 172740
  },
  {
  "command": "server.save",
  "seconds": 172790
  },
  {
  "command": "restart",
  "seconds": 172800
  },
  {
  "command": "reset.oncetimer",
  "seconds": 172801
  }
  ],
  "RepeaterCommands": [
  {
  "command": "oxide.reload HumanNPC",
  "seconds": 14400
  },
  {
  "command": "say '<color=orange> NPCs will reset in 5 minutes. If you're in the tower, finish up quickly before complete respawn</color>'",
  "seconds": 14100
  }
  ]
}

 

Good plugin, but have a nitpick question. When using the say command, I noticed that ' is required to show the whole message and not just the first word - but they also show in the message itself. Is there a way around this? Thanks.

 

It's a Rust command so it probably needs the : ' : also have you tried without them ?

 

Thanks. Yes I have, only the first word gets sent.

 

I use repeater commands to run events and while looking at logs, I noticed an event I have set to run 10 minutes ran 20 minutes to the second. It ran 10 minutes just fine otherwise in the logs. What happened? Thanks.

Edit: Consistently happens now. 10 minutes equals 20 minutes?

 

what to prescribe commands to spawn animals and barrels?
какие комманды прописать для спавна животных и бочек?

 

i am pretty sure the timed save is causing this message in rcon every 5 minutes, any ideas?

[Oxide] 3:29 PM [Info] [PaiN TimedExecute] Ran command: server.save
Cannot save mining quary because children were null
Cannot save mining quary because children were null
[Oxide] 3:34 PM [Info] [PaiN TimedExecute] Ran command: server.save
Cannot save mining quary because children were null
Cannot save mining quary because children were null

 

Cannot save mining quary because children were null
Cannot save mining quary because children were null
@Wulf Any ideas ? thas probably now comming from server.save but from your "Save" file or server.

 

it hasnt been doing it anymore since the update, not sure what the deal is

 

Just saw your message.. loll you know that the timer is a chain right ? read all the Overview Notes

 

The timer chains for repeater commands? That's what i'm using, not once commands. If so, your example config shows server.save every 300 seconds, how would it make sense for that to be chained to become longer and longer?

 

Oh you are talking about the Repeater....
Then no its not a chain.
Could you please explain more your problem ?

 

I have set up events to run on the server such as airdrops and radiation events. The radiation, for example, stays off for 10 minutes at a time. From the logs I have, it appears to work the first 2-3 times. After that, it stays off for 20 minutes, to the second. Since it was messing up, I unloaded it, so I don't know if it fixes itself or continues to increase.

 

Are you user that its the plugin's fault ? try without executing with this plugin .. try to make it manualy

 

I don't understand what you are asking. If I do the commands manually, of course they will be fine. If not the plugins fault, what else would it be? It is the only plugin running these commands. What I understand about this plugin is the repeater commands repeat the commands every x seconds, correct? I have an event set to run every 3 hours and last for 10 minutes. It does this just fine the first 2 times (lets say I start it at 12pm, it will run at 3pm and 6pm and last for 10 minutes.) Now, when it reaches the third time around, it runs at 9pm (as it should) but lasts for 20 minutes instead of 10. The longer the plugin runs, the later and later the some events get. I find it strange the start of the event doesn't get pushed later, but the end does.

Edited.

 

WoW what a mindfuck.. Why you are not trying to make the event with the Timer Once ? There are some examples http://oxidemod.org/plugins/timedexecute.919/field?field=faq