BEC BattlEye Extended Controls Question?

Q

Quarterbreed

Well-Known Member
hey guys BEC been running great for me and got my scheduler to restart every 4 hours.. was just wonder how can i add a msg to be sent every 10-15 min and how do i get Anti Hacks to pop up ingame chat also.. thx for the help..

this is my scheduler file here.

<?xml version="1.0"?>
<Scheduler>

<job id="0">
<time>23:30</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 30 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="1">
<time>23:45</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 15 minutes</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="2">
<time>23:50</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 10 minutes</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="3">
<time>23:55</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 5 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="4">
<time>23:59</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 1 minute</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="5">
<time>00:00</time>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>#restart</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="6">
<time>03:30</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 30 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="7">
<time>03:45</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 15 minutes</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="8">
<time>03:50</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 10 minutes</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="9">
<time>03:55</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 5 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="10">
<time>03:59</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 1 minute</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="11">
<time>04:00</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>#restart</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="12">
<time>07:30</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 30 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="13">
<time>07:45</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 15 minutes</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="14">
<time>07:50</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 10 minutes</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="15">
<time>07:55</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 5 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="16">
<time>07:59</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 1 minute</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="17">
<time>08:00</time>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>#restart</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="18">
<time>11:30</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 30 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="19">
<time>11:45</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 15 minutes</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="20">
<time>11:50</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 10 minutes</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="21">
<time>11:55</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 5 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="22">
<time>11:59</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 1 minute</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="23">
<time>12:00</time>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>#restart</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="24">
<time>15:30</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 30 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="25">
<time>15:45</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 15 minutes</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="26">
<time>15:50</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 10 minutes</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="27">
<time>15:55</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 5 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="28">
<time>15:59</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 1 minute</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="29">
<time>16:00</time>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>#restart</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="30">
<time>19:30</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 30 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="31">
<time>19:45</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 15 minutes</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="32">
<time>19:50</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 10 minutes</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="33">
<time>19:55</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 5 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="34">
<time>19:59</time>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 Server will be rebooted in 1 minute</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="34">
<time>20:00</time>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>#restart</cmd>
<cmdtype>0</cmdtype>
</job>

</Scheduler>
 
hhmmss format will make a message go after so many minutes.

001500 will be 15 minutes into the launch. Make it loop for what you need.
 
I guess you could reduce the 34 jobs into 5, as follows:

<?xml version="1.0"?>
<Scheduler>
<job id="0">
<time>033000</time>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 30 minutes</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="1">
<time>034500</time>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 15 minutes</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="2">
<time>035000</time>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 10 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="3">
<time>035900</time>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 1 minute</cmd>
<cmdtype>0</cmdtype>
</job>
<job id="4">
<time>040000</time>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>#restart</cmd>
<cmdtype>0</cmdtype>
</job>
</Scheduler>

You can add a job for the 15min message like:
<job id="5">
<time>001500</time>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 This message shows up every 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

I don't use my scheduler like that (I use the clock format and external batch files for log rotation and restarts), but I guess it would work.
 
Ooops, my fault, when using the <time>18:29</time> variation there's no need to set the delay, but in that example with the <time>033000</time> you gotta add the delay tag... I am posting it all again so you can copy/paste... I am not sure what the <loop> value should be in this case, experiment with it...

<?xml version="1.0"?>
<Scheduler>

<job id="0">
<time>033000</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 30 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="1">
<time>034500</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 15 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="2">
<time>035000</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 10 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="3">
<time>035900</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 1 minute</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="4">
<time>040000</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>#restart</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="5">
<time>001500</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 This message shows up every 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

</Scheduler>

Remember to experiment with the loop values... let me know if it worked!
 
Im not sure how to experiment with loop values.. I noticed tho during restart my server is still dark even tho its set to 24/7dayime.. I don't think its restarting properly or something.. its really bothering me
 
rboos said:
Ooops, my fault, when using the <time>18:29</time> variation there's no need to set the delay, but in that example with the <time>033000</time> you gotta add the delay tag... I am posting it all again so you can copy/paste... I am not sure what the <loop> value should be in this case, experiment with it...

<?xml version="1.0"?>
<Scheduler>

<job id="0">
<time>033000</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 30 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="1">
<time>034500</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 15 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="2">
<time>035000</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 10 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="3">
<time>035900</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 1 minute</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="4">
<time>040000</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>#restart</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="5">
<time>001500</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 This message shows up every 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

</Scheduler>

Remember to experiment with the loop values... let me know if it worked!
Click to expand...

ill try the way you post it atm, and it laoded up find with no errors now its just to see if it restarts
properly
 
Remember, when the mission restarts (with #restart in your scheduler) it does not affect the time; the clock will just go on as you #restart the mission. I mean the mission will slowly go into night time even if you #restart it.

If you wanna set a custom(fixed) starting time for your mission (let's say the server always starts with the clock at 7:00 AM), it will work everytime you #shutdown the server and start it with the proper .bat file.

In hiveext.ini use:
[Time]
Type = Static
Hour = 7

Then in the bec scheduler you call a .bat that kills the server and restarts it... this way it will always be 7AM when it starts... I do that every 6h.
 
That could be why my daytime usnt working.. Hkw would i go about wrinting a bat file.. I mean what codes do i use..
Im using stapos dayz+ any chance you could help me adding the command in the sched and make a bat file if possible.. Thx for reading
 
The scheduler will be like (new part in red):

<?xml version="1.0"?>
<Scheduler>

<job id="0">
<time>033000</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 30 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="1">
<time>034500</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 15 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="2">
<time>035000</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 10 minutes</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="3">
<time>035900</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Server will be rebooted in 1 minute</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="4">
<time>040000</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>C:\restart.bat</cmd>
<cmdtype>1</cmdtype>
</job>

<job id="5">
<time>001500</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 This message shows up every 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

</Scheduler>

And the restart.bat will be like this (you gotta adapt the paths, the part in blue doesn't need changes):

:: kill the server and bec..
taskkill /im arma2oaserver.exe
taskkill /im bec.exe

timeout 8

:: start the server..
set dayzpath="C:\Program Files\Steam\steamapps\common\Arma 2 Operation Arrowhead\"
cd /d %dayzpath%
start server_setup\silentcmd server_setup\server_chernarus_1.bat

timeout 30
:: start bec
set becpath="C:\"
cd /d %becpath%
start /D Bec\ Bec\Bec.exe -f Config.cfg

timeout 15
cls
@exit
 
Wow you made this look soo simple, this should be on top if the page.. im gonna try this when i get in thx

do i just point it to my server path c:\server2
 
Thx for the help guys, this works awesome, b4 o just had a restart thing in my sched, thats probally why my server would crash when restarting with pwople on it
 
Yes me too, but I need something server side. BEC implemented whitelisting but I can't find how to turn it on, someone else said #whitelist ON, but that does not work.
 
Strange, it was working last night now it's letting everyone in ... wasn't too sure about the whitelist format but worked with "guid space name" on each line but now i'm not so sure.
 
So you don't have to turn it on? it on by default? BEC loads the file because it does not give me any error on it.
 
just removing the hash # enables it in the config ... i'm moving from vanilla servers to CO now i think.
 
You must log in or register to reply here.
Back
Top