Jump to content
DayZ Forums
Sign in to follow this  
Followers 0
sneakydudes

Scheduler-Server Reboots

By sneakydudes, in Servers

Recommended Posts

sneakydudes    278

sneakydudes
Posted

I've been looking for a proper guide on schedulers on Vilayer hosting servers. I need to find a perfect example of server reboot messages.

 

However some of the information I find is about Mod'ed servers and not about SA servers.

 

Suggested script to reference?

 

Thanks in advance.

Share this post

Link to post
Share on other sites

sneakydudes    278

sneakydudes
Posted

Thank you so much for the link.

 

You know sometimes you can spend hours trying to locate things that actually end up useless and you need to rewrite them yourself.

 

It might be high time for Dayz Server SA Wiki :)

 

Thanks again amber for your help.

  • Like 1

Share this post

Link to post
Share on other sites

sinnaman    90

sinnaman
Posted (edited)

It might be high time for Dayz Server SA Wiki :)

 

You're damn right, but there is actually one up already at http://dayz.gamepedia.com/DayZ_Standalone_Wiki which may need some help. I'm sure the work needed to keep this database updated is quite extensive. :)

 

On a different note, feel free to use this scheduler script that I wrote for our server, found here. Instead of having cycles repeating itself every four hours (which may displace itself gradually) you're better off setting restart times to fixed times (server local time) to keep the restarts predictable. This script is intended for a 4-hour restart cycle from 13:00 server local time (meaning it will restart at EXACTLY 17:00, 21:00, etc). The script also warns players about upcoming restarts 10 and 3 minutes prior. Jobs 18 and 19 are server announcements which repeat themselves every other half hour. We use these as server ads; "Happy holidays, check out our teamspeak" and the like. You are of course free to add or remove jobs as you like, just make sure that the order of job ids is correct.

 

I hope this was of some help to you as well.

Edited by Sinnaman
  • Like 2

Share this post

Link to post
Share on other sites

sneakydudes    278

sneakydudes
Posted

Still having an issue getting it to display in game. Going to check the times, and the delays.

 

Could even be a missing part to the script.

Share this post

Link to post
Share on other sites

sneakydudes    278

sneakydudes
Posted

BEC might have been turned off, should be working now. I cant see anything else that may have caused the scheduler to not work.

Share this post

Link to post
Share on other sites

sneakydudes    278

sneakydudes
Posted (edited)

Still not sure I have this working right. As far as I know BEC is turned on from my last turn on with Vilayer

 

This is what I have, what is wrong with this.

 

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

 <!-- IMPORTANT: Visit www.ibattle.org for usage guides -->
 <!-- Guide For Using Scheduler System: http://ibattle.org/install-and-configure/setting-up-the-scheduler/ -->
 
 <!-- 2 Time Formats Can Be Used:
   00:00:00 - HH:MM:SS - Example, 02:30:00 would be 2:30am.  Messages using this format are sent based on the node's time.  It is recommend to set your ACP profile time to the same timezone as the node.
   000000 - HHMMSS - Example, 003000 Is 30 Minutes From When Server Started
 -->
<!-- 03:00:00 restart -->
 
    <job id="0">
        <runtime>000000</runtime> <!-- run once  -->
        <start>03:00:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>#restart</cmd>
    </job>
   
    <job id="1">
        <runtime>000000</runtime> <!-- run once  -->
        <start>02:57:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>say -1 job:1 Server will restart in 3 minutes LOG OFF NOW!</cmd>   
    </job>   

    <job id="2">
        <runtime>000000</runtime> <!-- run once  -->
        <start>02:50:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>say -1 job:2 Server will restart in 10 minutes. Yay, more burlaps!</cmd>       
    </job>   

<!-- 07:00:00 restart -->
 
    <job id="3">
        <runtime>000000</runtime> <!-- run once  -->
        <start>07:00:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>#restart</cmd>  
    </job>
   
    <job id="4">
        <runtime>000000</runtime> <!-- run once  -->
        <start>06:57:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>say -1 job:4 Server will restart in 3 minutes LOG OFF NOW!</cmd>   
    </job>   

    <job id="5">
        <runtime>000000</runtime> <!-- run once  -->
        <start>06:50:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>say -1 job:5 Server will restart in 10 minutes. Yay, more peaches!</cmd>     
    </job>  
 
<!-- 11:00:00 restart -->
 
    <job id="6">
        <runtime>000000</runtime> <!-- run once  -->
        <start>11:00:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>#restart</cmd>  
    </job>
   
    <job id="7">
        <runtime>000000</runtime> <!-- run once  -->
        <start>10:57:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>say -1 job:7 Server will restart in 3 minutes!</cmd>   
    </job>   

    <job id="8">
        <runtime>000000</runtime> <!-- run once  -->
        <start>10:50:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>say -1 job:8 Server will restart in 10 minutes. Yay, more shovels!</cmd>   
    </job>   
 
<!-- 15:00:00 restart -->
 
    <job id="9">
        <runtime>000000</runtime> <!-- run once  -->
        <start>15:00:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>#restart</cmd>  
    </job>
   
    <job id="10">
        <runtime>000000</runtime> <!-- run once  -->
        <start>14:57:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>say -1 job:10 Server will restart in 3 minutes LOG OFF NOW!</cmd>   
    </job>   

    <job id="11">
        <runtime>000000</runtime> <!-- run once  -->
        <start>14:50:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>say -1 job:11 Server will restart in 10 minutes. Yay, more helicrashes!</cmd>             
    </job>   
 
<!-- 19:00:00 restart -->
 
    <job id="12">
        <runtime>000000</runtime> <!-- run once  -->
        <start>19:00:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>#restart</cmd>  
    </job>
   
    <job id="13">
        <runtime>000000</runtime> <!-- run once  -->
        <start>18:57:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>say -1 job:13 Server will restart in 3 minutes LOG OFF NOW!</cmd>           
    </job>   

    <job id="14">
        <runtime>000000</runtime> <!-- run once  -->
        <start>18:50:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>say -1 job:14 Server will restart in 10 minutes. Yay, more coffee!</cmd>             
    </job>   
 
<!-- 23:00:00 restart -->
 
    <job id="15">
        <runtime>000000</runtime> <!-- run once  -->
        <start>23:00:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>#restart</cmd>  
    </job>
   
    <job id="16">
        <runtime>000000</runtime> <!-- run once  -->
        <start>22:57:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>say -1 job:16 Server will restart in 3 minutes, LOG OFF NOW!</cmd>   
    </job>   

    <job id="17">
        <runtime>000000</runtime> <!-- run once  -->
        <start>22:50:00</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>0</loop>
        <cmd>say -1 job:17 Server will restart in 10 minutes. Yay, more guns!</cmd>   
    </job>   

    <job id="18">
        <runtime>006000</runtime> <!-- run every 30 mins -->
        <start>004000</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>-1</loop>
        <cmd>say -1 job:18 Welcome to Clan Z Server clanzgaming.com</cmd>
    </job>

    <job id="19">
        <runtime>006000</runtime> <!-- run every 30 mins -->
        <start>001000</start>
        <day>1,2,3,4,5,6,7</day>
        <loop>-1</loop>
        <cmd>say -1 job:19 Server resets 3am, 7am, 11am, 3pm, 7pm, and 11pm EST clanzgaming.com</cmd>
    </job>
</Scheduler>

Edited by FIRMSneakydude

Share this post

Link to post
Share on other sites

sneakydudes    278

sneakydudes
Posted (edited)

I put in #reboot instead of #shutdown.

 

I still don't see the messages in game that I can verify.

 

I also tweaked it one last time so I hope it works.

 

(new server) etc.. if your wondering.

Edited by FIRMSneakydude

Share this post

Link to post
Share on other sites

sneakydudes    278

sneakydudes
Posted

LINE 23, COLUMN 4 error bec scheduler log file I was testing the epm rcon program and I reloaded scripts and those messages came up in the acplayer admin control.

Share this post

Link to post
Share on other sites

sneakydudes    278

sneakydudes
Posted

<scheduler> would help in the front of it all :)

 

Stupid little mistake but I missed it because of the initial text.

 

All should be good tomorrow when I reedit it.

Share this post

Link to post
Share on other sites

sinnaman    90

sinnaman
Posted (edited)

 <!-- IMPORTANT: Visit www.ibattle.org for usage guides -->

 <!-- Guide For Using Scheduler System: http://ibattle.org/install-and-configure/setting-up-the-scheduler/ -->

So far so good...

 

<!-- 2 Time Formats Can Be Used:

   00:00:00 - HH:MM:SS - Example, 02:30:00 would be 2:30am.  Messages using this format are sent based on the node's time.  It is recommend to set your ACP profile time to the same timezone as the node.

   000000 - HHMMSS - Example, 003000 Is 30 Minutes From When Server Started

 -->

Here there are no <--! or proper <code> entries on lines 2, 3, and 4. That's what's causing your mess. You should rather have the following;

<!-- 2 Time Formats Can Be Used:-->   <--! 00:00:00 - HH:MM:SS - Example, 02:30:00 would be 2:30am.  Messages using this format are sent based on the node's time.  It is recommend to set your ACP profile time to the same timezone as the node.-->   <--!000000 - HHMMSS - Example, 003000 Is 30 Minutes From When Server Started-->

Honestly, you shouldn't need to have any of what I've quoted in your script. They are just useless pieces of information for you now.

Also make sure you're using the #shutdown command, not #restart. #restart just restarts the mission, not the server, and should be disabled IMHO.

Edited by Sinnaman

Share this post

Link to post
Share on other sites

sneakydudes    278

sneakydudes
Posted (edited)

Ok testing this now. This is the current code I have. (first test)

 

 

 

 

<?xml version="1.0"?>
<Scheduler>
    <!-- READ http://ibattle.org/install-and-configure/setting-up-the-scheduler/ -->

     <job id="0">
         <runtime>000000</runtime>
         <start>03:00:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>#shutdown</cmd>
     </job>
     <job id="1">
         <runtime>000000</runtime>
         <start>02:57:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>say -1 Server will restart in 3 minutes LOG OFF NOW!</cmd>  
     </job>
    <job id="2">
         <runtime>000000</runtime>
         <start>02:50:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>say -1 Server will restart in 10 minutes</cmd>      
     </job>
  
     <job id="3">
         <runtime>000000</runtime>
         <start>07:00:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>#shutdown</cmd> 
     </job>  
     <job id="4">
         <runtime>000000</runtime>
         <start>06:57:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>say -1 Server will restart in 3 minutes LOG OFF NOW!</cmd>  
     </job>
    <job id="5">
         <runtime>000000</runtime>
         <start>06:50:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>say -1 Server will restart in 10 minutes</cmd>    
     </job>
 
     <job id="6">
         <runtime>000000</runtime>
         <start>11:00:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>#shutdown</cmd> 
     </job>
     <job id="7">
         <runtime>000000</runtime>
         <start>10:57:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>say -1 Server will restart in 3 minutes!</cmd>  
     </job>
    <job id="8">
         <runtime>000000</runtime>
         <start>10:50:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>say -1 Server will restart in 10 minutes.</cmd>  
     </job>
 
     <job id="9">
         <runtime>000000</runtime>
         <start>15:00:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>#shutdown</cmd> 
     </job>
     <job id="10">
         <runtime>000000</runtime>
         <start>14:57:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>say -1 Server will restart in 3 minutes LOG OFF NOW!</cmd>  
     </job>
     <job id="11">
         <runtime>000000</runtime>
         <start>14:50:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>say -1 Server will restart in 10 minutes</cmd>            
     </job>
  
     <job id="12">
         <runtime>000000</runtime>
         <start>19:00:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>#shutdown</cmd>
     </job>
     <job id="13">
         <runtime>000000</runtime>
         <start>18:57:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>say -1 Server will restart in 3 minutes LOG OFF NOW!</cmd>          
     </job>  
     <job id="14">
         <runtime>000000</runtime>
         <start>18:50:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>say -1 Server will restart in 10 minutes</cmd>            
     </job>
 
     <job id="15">
         <runtime>000000</runtime>
         <start>23:00:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>#shutdown</cmd>
     </job>  
     <job id="16">
         <runtime>000000</runtime>
         <start>22:57:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>say -1 Server will restart in 3 minutes, LOG OFF NOW!</cmd>  
     </job>
     <job id="17">
         <runtime>000000</runtime>
         <start>22:50:00</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>0</loop>
         <cmd>say -1 Server will restart in 10 minutes</cmd>  
     </job>

     <job id="18">
         <runtime>006000</runtime>
         <start>004000</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>-1</loop>
         <cmd>say -1 Welcome to Clan Z Server www.clanzgaming.com Please help us Grow!, Donations accepted.</cmd>
     </job>
     <job id="19">
         <runtime>006000</runtime>
         <start>001000</start>
         <day>1,2,3,4,5,6,7</day>
         <loop>-1</loop>
         <cmd>say -1 Server resets 3am, 7am, 11am, 3pm, 7pm, and 11pm EST www.clanzgaming.com</cmd>
     </job>
 </Scheduler>

Edited by FIRMSneakydude

Share this post

Link to post
Share on other sites

sneakydudes    278

sneakydudes
Posted (edited)

FIXED

 

Vilayer isn't using the same thing

 

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<?xml-stylesheet href="acs.xsl" type="text/xsl" ?>

 

<Scheduler>
  
 <job id="0">
  <time>003000</time>
  <delay>000000</delay>
  <day>1,2,3,4,5,6,7</day>
  <loop>1</loop>
  <cmd>say -1 Welcome to ClanZ Private Server, please visit us www.clanzgaming.com</cmd> 
  <cmdtype>0</cmdtype>
 </job>

</Scheduler>

 

Example

Edited by FIRMSneakydude

Share this post

Link to post
Share on other sites

sneakydudes    278

sneakydudes
Posted (edited)

Oh they're using the old BEC system..? That's a little.. odd...

See I had no information on this and the tech said the utube video was of the other version.

This is the same version most of you use.

 

Sinnaman you have been a huge help, and I high five you.

 

But one more request is there a help file I don't have on this version.

Edited by FIRMSneakydude

Share this post

Link to post
Share on other sites

Valdenburg    200

Valdenburg
Posted

Oh they're using the old BEC system..? That's a little.. odd...

Yes indeed - i would call it "bad" though not just "odd" :D

 

Vilayer is good when you can eat the bullshit they are giving the customer to eat - when you don´t want this or good support you got to switch provider.

Share this post

Link to post
Share on other sites

sneakydudes    278

sneakydudes
Posted

Yes indeed - i would call it "bad" though not just "odd" :D

 

Vilayer is good when you can eat the bullshit they are giving the customer to eat - when you don´t want this or good support you got to switch provider.

Is it not checking for current hacks? well the hacks I see aren't being caught anyways.

 

Old = bad? in this case?

Share this post

Link to post
Share on other sites

Valdenburg    200

Valdenburg
Posted

Is it not checking for current hacks? well the hacks I see aren't being caught anyways.

 

Old = bad? in this case?

BEC got nothing todo with Battleye hack detection as far as i know.

 

As one of the biggest GSPs you just don´t leave a update to the side when it included that many changes in how scripts are working.

So yes old equals bad in this case.

Share this post

Link to post
Share on other sites

sneakydudes    278

sneakydudes
Posted

BEC got nothing todo with Battleye hack detection as far as i know.

 

As one of the biggest GSPs you just don´t leave a update to the side when it included that many changes in how scripts are working.

So yes old equals bad in this case.

Thanks van,

 

The reason I ask is because we just got the script working great and I was pulling my hair out trying to get the new codes to work (and I was doing it right all along)

I just am waiting for our private 50/50 server to be available and I wanted to make sure its up to date so that nobody can screw around with it or problems with whitelisted hackers.

 

I was thinking of whitelisting it due to protecting the gaming community. (should we?) I will have to follow advertising it to keep it open as the 3 admins we currently have been donating to the master hive. I don't want scripts to be a problem if we open it up to the public to play on. It will be a PVP server, and the master hive will be clan members not wishing to do pvp on it. Or testing or running practice ops whichever.

 

As you know many of us look for bugs on our master hive, and report our findings.

 

I am sure you guys do the same things.

Share this post

Link to post
Share on other sites

Valdenburg    200

Valdenburg
Posted

Thanks van,

 

The reason I ask is because we just got the script working great and I was pulling my hair out trying to get the new codes to work (and I was doing it right all along)

I just am waiting for our private 50/50 server to be available and I wanted to make sure its up to date so that nobody can screw around with it or problems with whitelisted hackers.

 

I was thinking of whitelisting it due to protecting the gaming community. (should we?) I will have to follow advertising it to keep it open as the 3 admins we currently have been donating to the master hive. I don't want scripts to be a problem if we open it up to the public to play on. It will be a PVP server, and the master hive will be clan members not wishing to do pvp on it. Or testing or running practice ops whichever.

 

As you know many of us look for bugs on our master hive, and report our findings.

 

I am sure you guys do the same things.

Hi Sneaky. Great to hear you sorted that out.

 

You should deffinately run a whitelist imo. Only thing that bugged me was the fiddling with the GUID to actually whitelist people.

We have a automated Whitelist running for our Server. Atm we try to make that available to other server admins.

 

Right now its a long process for a player to get his GUID. On our site you "Sign in through Steam" and you are automatically whitelisted.

 

Just PM me when your are interested in a automated whitelist that you can fully administrate ;)

 

Regards

Van

Share this post

Link to post
Share on other sites

sneakydudes    278

sneakydudes
Posted

Hi Sneaky. Great to hear you sorted that out.

 

You should deffinately run a whitelist imo. Only thing that bugged me was the fiddling with the GUID to actually whitelist people.

We have a automated Whitelist running for our Server. Atm we try to make that available to other server admins.

 

Right now its a long process for a player to get his GUID. On our site you "Sign in through Steam" and you are automatically whitelisted.

 

Just PM me when your are interested in a automated whitelist that you can fully administrate ;)

 

Regards

Van

Thank you very much Van,

 

The 50 man hive is up and rolling... funny its pinging better then our master atm. :)

 

I will definitely get in contact with you once we are ready to roll out the whitelisting part. Right now its in beta testing to get everything perfectly running.

 

Sneaky

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
Sign in to follow this  
Followers 0
Go To Topic Listing Servers
×