Shared by hwk on June 11, 2015

Since the 0.57 update on stable branch, developers implemented new options for admins: Server date, time & persistence. In this guide I’ll explain you the new functionalities and give you an example on how to setup a “3 hours day + 1 hour dusk” Server” including BEC Scheduler configuration.

New Server Time Options

  • Server Time: “System Time” (based on server) or “Custom Time”.
  • Start-up Time: If the Server time is set on “Custom Time” then you can define a date time for the server start-up, using the following pattern: YYYY/MM/DD/HH/MM. Example: “2015/4/8/17/23”.
  • Time Acceleration: Sets multiplier for X in-game hours that pass during 1 real world hour
  • Time Persistence: Saves server time to persistence, time will continue after restarts

Understanding Chernarus Time

DayZ use the real time location of Chernarus, in Czech Republic. That means If you define a custom time, let’s say “2015/4/8/12/00”, then the server will the use the real-world sunrise & sunset of the april, 8th 2015 in Chernarus. The nearest and most accurate real-world location is Moscow. Here is a graph all dates with sunrise, sunset, dawn and dusk times.

dayz-chernarus-real-time-moscow-sunset-sunrise-dusk

As we can see, on april 12th, dawn occurs around 5h30 and dusk around 19:30. This graph from gaisma.com will let you choose and control your whole day cycle.

Setting up “3 hours day + 1 hour dusk” Server

Use the following settings:

  • Custom Time
  • 2015/4/8/05/25
  • Enable “Time Acceleration” to 4 hours
  • Disable “Time Persistence”
  • Set BEC Scheduler to Restart every 4 hours

The server time range will be 5:30AM (start) to 21:30PM (shutdown). As we saw on Moscow real-world dawn & dusk graphics, 5h30 AM is when the sunrise & 19h00 PM is when the dusk occurs. Which means you’ll have a gorgeous sunrise for first players joining the server and about ~45mn of “dusk” atmosphere at the end of the session.

Here is an overview of the server cycle:

  • 0h00 Real World = 05:30 AM In-game (Sunrise)
  • 1h00 Real World = 09:30 AM In-game
  • 2h00 Real World = 13:30 PM In-game
  • 3h00 Real World = 17:30 PM In-game
  • 3h30 Real World = 19:00 PM In-game (Dusk)
  • 4h00 Real World = 21:30 PM In-game (Shutdown)

Setting up the BEC Scheduler File

BEC Scheduler let you define automatic global messages, warnings & server restart. Here is a compatible BEC Scheduler with “Current in-game time” & “Restart in xx hours” messages.

<?xml version=”1.0″?>
<Scheduler>

<!– READ http://ibattle.org/install-and-configure/setting-up-the-scheduler/ –>
<job id=”0″>
<runtime>040000</runtime>
<start>040000</start>
<day>1,2,3,4,5,6,7</day>
<loop>6</loop>
<cmd>#shutdown</cmd>
<cmdtype>0</cmdtype>
</job>

<job id=”1″>
<runtime>040000</runtime>
<start>020000</start>
<day>1,2,3,4,5,6,7</day>
<loop>6</loop>
<cmd>say -1 Server Restart in 2H</cmd>
<cmdtype>0</cmdtype>
</job>

<job id=”2″>
<runtime>040000</runtime>
<start>030000</start>
<day>1,2,3,4,5,6,7</day>
<loop>6</loop>
<cmd>say -1 Server Restart in 1H</cmd>
<cmdtype>0</cmdtype>
</job>

<job id=”3″>
<runtime>040000</runtime>
<start>033000</start>
<day>1,2,3,4,5,6,7</day>
<loop>6</loop>
<cmd>say -1 Server Restart in 30min</cmd>
<cmdtype>0</cmdtype>
</job>

<job id=”4″>
<runtime>040000</runtime>
<start>034500</start>
<day>1,2,3,4,5,6,7</day>
<loop>6</loop>
<cmd>say -1 Server Restart in 15min</cmd>
<cmdtype>0</cmdtype>
</job>

<job id=”5″>
<runtime>040000</runtime>
<start>035000</start>
<day>1,2,3,4,5,6,7</day>
<loop>6</loop>
<cmd>say -1 Server Restart in 10min</cmd>
<cmdtype>0</cmdtype>
</job>

<job id=”6″>
<runtime>040000</runtime>
<start>035500</start>
<day>1,2,3,4,5,6,7</day>
<loop>6</loop>
<cmd>say -1 Server Restart in 5min</cmd>
<cmdtype>0</cmdtype>
</job>

<job id=”7″>
<runtime>040000</runtime>
<start>035900</start>
<day>1,2,3,4,5,6,7</day>
<loop>6</loop>
<cmd>say -1 Server Restart in 1min</cmd>
<cmdtype>0</cmdtype>
</job>

<!– Messages –>
<job id=”8″>
<runtime>040000</runtime>
<start>000500</start>
<day>1,2,3,4,5,6,7</day>
<loop>6</loop>
<cmd>say -1 It is 05:30 In-game</cmd>
<cmdtype>0</cmdtype>
</job>

<job id=”9″>
<runtime>040000</runtime>
<start>010000</start>
<day>1,2,3,4,5,6,7</day>
<loop>6</loop>
<cmd>say -1 It is 9:30 In-game</cmd>
<cmdtype>0</cmdtype>
</job>

<job id=”10″>
<runtime>040000</runtime>
<start>020010</start>
<day>1,2,3,4,5,6,7</day>
<loop>6</loop>
<cmd>say -1 It is 13:30 In-game</cmd>
<cmdtype>0</cmdtype>
</job>

<job id=”11″>
<runtime>040000</runtime>
<start>030010</start>
<day>1,2,3,4,5,6,7</day>
<loop>6</loop>
<cmd>say -1 It is 17:30 In-game</cmd>
<cmdtype>0</cmdtype>
</job>

<job id=”12″>
<runtime>040000</runtime>
<start>035700</start>
<day>1,2,3,4,5,6,7</day>
<loop>6</loop>
<cmd>say -1 It is 21:30 In-game</cmd>
<cmdtype>0</cmdtype>
</job>

</Scheduler>

*