TimedExecute [Unmaintained]

thanks , im allways forgetting the ,

 

Can someone send me a 4 hour automatic restart? Madness's config don't seem to work for me, I may be wrong though.

 

Code:

{
  "EnableTimerOnce": true,
  "EnableTimerRepeat": true,
  "TimerOnce": {
    "say 'Server <color=orange>AUTOMATIC</color> Restart in 4 hours!'": 0,
    "say 'Server <color=orange>AUTOMATIC</color> Restart in 3 hours!'": 3600,
    "say 'Server <color=orange>AUTOMATIC</color> Restart in 2 hours!'": 7200,
    "say 'Server <color=orange>AUTOMATIC</color> Restart in 1 hour!'": 10800,
    "say 'Server <color=orange>AUTOMATIC</color> Restart in 30 minutes!'": 11880,
    "say 'Server <color=orange>AUTOMATIC</color> Restart in 15 minutes!'": 13500,
    "say 'Server <color=orange>AUTOMATIC</color> Restart in 5 minutes!'": 12780,
    "server.save" : 14397,
    "say 'Server <color=orange>AUTOMATIC</color> Restart in 5 minutes!'": 14399,
    "restart": 14400,
    "reset.oncetimer": 14401
  },
  "TimerRepeat": {
    "event.run": 300,
    "server.save": 300
  }
}

 

Hey sup,

I doubt it's the plugin, but I noticed something real weird. I setup the plugin to do a heli.call every 2 hours on my server. I'm using a plugin to lengthen days, so the heli only pops up like twice a day on my server. Figured this would fix the issue... But... Nothing happens!

I see the heli.call pop in the console, so I know it's not the plugin that's not properly configured.. It is doing the command, but nothing happens. It's ignoring the command. If I run heli.call manually, it works.

Does that command have to be called by an admin on the console absolutely? It looks like it's being ignored when a plugin calls it.

I installed HeliControl and now use callheli instead and now it works...

 

From what you say... probably the "heli.call" cmd works only if you do it manually ? Since the other one from the HeliControl work.

 

Thats what I'm thinking. Just thought I'd share here to see if others had the same issue.

 

Hi! Can you add a timed commad at one specific hour (server hosting hour ... not game hour) ... like at 5AM (GMT) execute server.save and restart !?
----------------------------------------------------------------------
"TimerAtHour": {
"server.save": 5.00,
"restart": 5.00
}
----------------------------------------------------------------------
5.00 - 5AM... 5.30 - 5:30AM ... 18.45 - 18:45PM ETC

 

Hi any reason for i cannot do the command like:

"event.spawnfile desert": 7360,

is the space cause issue?

okay i can do by rename files or name kits with:
"event.spawnfile 'desert'": 7360,

but whythe following not work as example?
"event.open": 7362,
"event.end": 7660,

 

If you use this one as a repeat command, they are going to space out as time goes by. The first set will be fine, but every time it runs they will get further and further away from each other.

 

hi i don't understand what you mean, then what must i do for use these as repeat command an example?
do you read this one won't run?
"event.spawnfile desert": 7360,
same as event.kit blabla

 

It's simple really. Set something every 2 min and something every 3 min...

2 min: event 1
3 min: event 2
4 min: event 1
6 min: event 2 + event 1
8 min: event 1
9 min: event 2
etc...

Both of your repeats are cycled and they won't be spaced the same each time because they each occur at different repeat rates.

Basically, you cannot do this with this plugin.

 

hahaha you don't understand i show you a command have you tried "event.spawnfile desert" in TimedExecute? or event.kit of course or something that you can do with your files and/or kit config and the command contain a space you know... i would mean the TimedExecute seem not work with a space !! understood? but !! "event.open" this one won't work and "event.end" this one too :/ my english is limited

 

I wasn't replying to the space issue, but to the fact starting events like you are trying to do won't work because of the delays.

That said you seem to say they do not work at all. I had issues with heli.call with this plugin so perhaps there is an issue with the plugin itself.

 

ok yes i would want to understand you too but the command i put "event.open" won't work at 1st up of the file you know the repeat command are under this and in future timed :/ simply try a little file you see that TimedExecute won't execute ^^ or i don't know

 

It works for event.run (airdrop) and callheli (heli control plugin) as I use both of these.

I was using heli.call before using the heli control plugin and I would see it pop in RCON for the plugin, but it would not have any effect, it did not work. I think the plugin has a problem, or perhaps it's an issue with Rust or Oxide.
[DOUBLEPOST=1445486486][/DOUBLEPOST]Update: Did a code review on the plugin and it doesn't look like it's doing anything wrong, assuming it's a Rust or Oxide issue at this point...?

 

mmm my english is limited sorry i go try another

 

Oh ok and this plugin only use native command it's ok solved then !!

 

woo :/