Jump to content
jeje00857050@hotmail.fr

Problem with Scheduler

Recommended Posts

No problem, hope it helps. The only thing I'm not entirely happy with is the repeated messages at the end. Want them to appear at 5 minutes past the hour. It will work as-is unless there is a manual or non-scheduled restart.

 

I could do this:

<job id="24">
<day>1,2,3,4,5,6,7</day>
<start>00:05:00</start>
<runtime>010000</runtime>
<loop>-1</loop>
<cmd>say -1 Both ZombieSkelper.com servers share the same hive - make sure to favourite both</cmd>
</job>

 

but I don't think that'll work as the next restart at 4am would effectively kill it. Need to do more testing but can't see anyway other than creating a job for each hourly update. I'll post up if I come up with anything though.

Edited by theirongiant74

Share this post


Link to post
Share on other sites

No problem, hope it helps. The only thing I'm not entirely happy with is the repeated messages at the end. Want them to appear at 5 minutes past the hour. It will work as-is unless there is a manual or non-scheduled restart.

 

I could do this:

<job id="24">
<day>1,2,3,4,5,6,7</day>
<start>00:05:00</start>
<runtime>010000</runtime>
<loop>-1</loop>
<cmd>say -1 Both ZombieSkelper.com servers share the same hive - make sure to favourite both</cmd>
</job>

 

but I don't think that'll work as the next restart at 4am would effectively kill it. Need to do more testing but can't see anyway other than creating a job for each hourly update. I'll post up if I come up with anything though.

This should work :

 

<job id="3">

        <runtime>000500</runtime>

        <start>000500</start>

        <day>1,2,3,4,5,6,7</day>

        <loop>60</loop>

        <cmd>say -1 Powered By DayZGameServer.com - PvP [1h restart]</cmd>    

        <cmdtype>0</cmdtype>            

    </job>

Share this post


Link to post
Share on other sites

This should work :

 

<job id="3">

        <runtime>000500</runtime>

        <start>000500</start>

        <day>1,2,3,4,5,6,7</day>

        <loop>60</loop>

        <cmd>say -1 Powered By DayZGameServer.com - PvP [1h restart]</cmd>    

        <cmdtype>0</cmdtype>            

    </job>

 

Hmm, not sure that's right, <start> in that format kicks off 5 minutes after BEC starts/restarts, <loop> is the number of times to loop (-1 for always) and <runtime> is the gap between loops.

 

Btw <cmdtype> is deprecated in the latest version of BEC so you don't need it if you're using the up to date version (and from the sounds of it you are), it used to be used to indicate whether the command was an internal or external (batch file) one. 

 

I think the only way round it is to create 24 jobs that run at the correct time, if you use the hhmmss format then the job is tied to the time you last restarted BEC.

 

Might try my hand at creating a web tool that will generate scheduler files, be a bit less onerous and would be quite handy for people to use. 

Share this post


Link to post
Share on other sites

Hmm, not sure that's right, <start> in that format kicks off 5 minutes after BEC starts/restarts, <loop> is the number of times to loop (-1 for always) and <runtime> is the gap between loops.

 

Btw <cmdtype> is deprecated in the latest version of BEC so you don't need it if you're using the up to date version (and from the sounds of it you are), it used to be used to indicate whether the command was an internal or external (batch file) one. 

 

I think the only way round it is to create 24 jobs that run at the correct time, if you use the hhmmss format then the job is tied to the time you last restarted BEC.

 

Might try my hand at creating a web tool that will generate scheduler files, be a bit less onerous and would be quite handy for people to use. 

From what i understand it should trigger 5 minutes after BEC restarted and then every 5 minutes 60 times.

 

 

For us its working in this context below. It will trigger it every 5 minutes after a server restart.

 

<job id="3">

        <runtime>000030</runtime> <!-- run every 30 sec -->

        <start>000030</start>

        <day>1,2,3,4,5,6,7</day>

        <loop>60</loop>

        <cmd>say -1 Powered By DayZGameServer.com - PvP [1h restart]</cmd>    

        <cmdtype>0</cmdtype>            

    </job>

    <job id="4">

        <runtime>000300</runtime> <!-- run once after 3 min -->

        <start>000000</start>

        <day>1,2,3,4,5,6,7</day>

        <loop>0</loop>

        <cmd>say -1 This Server restarted 3 minutes ago</cmd>    

        <cmdtype>0</cmdtype>            

    </job>

 <job id="5">

        <runtime>020000</runtime> <!-- run once after 1h -->

        <start>020000</start>

        <day>1,2,3,4,5,6,7</day>

        <loop>0</loop>

        <cmd>#shutdown</cmd>    

        <cmdtype>0</cmdtype>            

    </job>

Share this post


Link to post
Share on other sites

Ah, okay I misunderstood what you were trying to do. I'm wanting to display a message once an hour at 5 minutes past the hour, was hoping there was a way to do it without creating 24 jobs but I don't think that is possible. 

Share this post


Link to post
Share on other sites

OLD FORMAT

<!-- this job will start after 10 minutes and run forever with a 1 hour and 30 minutes interval between the jobs -->
    <job id='0'>
        <day>1,2,3,4,5,6,7</day>
        <time>001000</time>
        <delay>013000</delay>
        <loop>-1</loop>
        <cmd>say -1 job:0 forever</cmd>
    </job>



NEW FORMAT
<job id="3">
        <start>000400</start> <!-- run every 5 mins -->
        <runtime>000300</runtime>
        <day>1,2,3,4,5,6,7</day>
        <loop>1</loop>
        <cmd>say -1 Victory Gamerz Members Are Friendly</cmd>
        <cmdtype>0</cmdtype>
    </job>

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

×