Jump to content

Question

Hello, i am having a bunch of issues with my BEC scheduler. I do not get any messages to show up at all in my server and the #shutdown doesnt work either in the scheduler. I also use infistar if that can some issues. Also my server doesnt tell me when people connect/disconnect.

 

Here is my bec config:
 

 

#GENERATED AUTOMATICALLY BY VERT HOSTING

[bec]
Ip = 216.244.84.154
Port = 2412
BePath = C:\TCAFiles\Users\JoshA\1182\Bliss\BattlEye
#Admins = Admins.xml
#Commands = Commands.xml
LogDir = Server1
 
[Misc]
Scheduler = Scheduler.xml
#AsciiChatOnly = True
#IgnoreChatChars = �����
ConsoleColor = 1f
Timeout = 60
KickLobbyIdlers = 500

 

Here is my sheduler.xml:

 

?xml version="1.0"?>

<!-- GENERATED AUTOMATICALLY BY VERT HOSTING -->
<Scheduler>
 
       <!-- show text ingame every 20 min -->
<job id="0">
<time>002000</time>
<delay>001000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop> 
<cmd>say -1 This Server is hosted by Vert Hosting</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="1">
<time>002000</time>
<delay>001000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop> 
<cmd>say -1  TS: 216.244.78.163:9989, WebSite: http://tsgc.freeforums.org/</cmd>
<cmdtype>0</cmdtype>
</job>
 
<!-- show text ingame every 10-15 min -->
<job id="2">
<time>001000</time>
<delay>001500</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop> 
<cmd>say -1 The server restarts Every 4hour, 00:00 | 04:00 | 08:00 | 12:00 | 16:00 | 20:00</cmd>
<cmdtype>0</cmdtype>
</job>
 
 
<!-- *** RESTARTS *** -->
<!-- 30 min to the 00:00 restart -->
<job id="3">
<time>23:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="4">
<time>23:40:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 20 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="5">
<time>23:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="6">
<time>23:50:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 10 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="7">
<time>23:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="8">
<time>23:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<!-- 00:00 restart -->
<job id="9">
<time>00:00:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>#shutdown</cmd>
<cmdtype>0</cmdtype>
</job>
 
<!-- 30 min to the 04:00 restart -->
<job id="10">
<time>03:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="11">
<time>03:40:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 20 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="12">
<time>03:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="13">
<time>03:50:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 10 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="14">
<time>03:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="15">
<time>03:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<!-- 04:00 restart -->
<job id="16">
<time>04:00:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>#shutdown</cmd>
<cmdtype>0</cmdtype>
</job>
 
<!-- 30 min to the 08:00 restart -->
<job id="17">
<time>07:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="18">
<time>07:40:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 20 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="19">
<time>07:15:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="20">
<time>07:10:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 10 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="21">
<time>07:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="22">
<time>07:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<!-- 08:00 restart -->
<job id="23">
<time>08:00:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>#shutdown</cmd>
<cmdtype>0</cmdtype>
</job>
 
<!-- 30 min to the 12:00 restart -->
<job id="24">
<time>11:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="25">
<time>11:40:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 20 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="26">
<time>11:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="27">
<time>11:50:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 10 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="28">
<time>11:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="29">
<time>11:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<!-- 00:00:00 restart -->
<job id="30">
<time>12:00:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>#shutdown</cmd>
<cmdtype>0</cmdtype>
</job>
 
<!-- 30 min to the 16:00 restart -->
<job id="31">
<time>15:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="32">
<time>15:40:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 20 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="33">
<time>15:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="34">
<time>15:50:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 10 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="35">
<time>15:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="36">
<time>15:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<!-- 16:00:00 restart -->
<job id="37">
<time>16:00:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>#shutdown</cmd>
<cmdtype>0</cmdtype>
</job>
 
<!-- 30 min to the 20:00 restart -->
<job id="38">
<time>19:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="39">
<time>19:40:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 20 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="40">
<time>19:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="41">
<time>19:50:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 10 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="42">
<time>19:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<job id="43">
<time>19:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>say -1 The server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>
 
<!-- 20:00 restart -->
<job id="44">
<time>20:00:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop> 
<cmd>#shutdown</cmd>
<cmdtype>0</cmdtype>
</job>
 
  
</Scheduler>

 

Share this post


Link to post
Share on other sites

22 answers to this question

Recommended Posts

  • 0

Add a < to the top of your scheduler.xml (?xml version="1.0"?>) unless you just forgot to copy that part, and delete the # before #Admins = Admins.xml #Commands = Commands.xml in your main config file

Share this post


Link to post
Share on other sites
  • 0

Take out the # before #Commands = Commands.xml, I believe scheduler uses them to #shutdown, etc.

Here is the thing, does #shutdown restart the server or does it shut it down completely and wont start back up till i start it manually?

Share this post


Link to post
Share on other sites
  • 0

Here is the thing, does #shutdown restart the server or does it shut it down completely and wont start back up till i start it manually?

#shutdown will shut it down and you have to turn it back on, before I had my dedicated server and used .bat files I had my host setup restarts for me via ticket system. You could make a .bat file to launch the server and have the scheduler launch the bat file 3 seconds before it shuts down the server.

Share this post


Link to post
Share on other sites
  • 0

Make sure you have a bans.txt file into your battleye folder, If you don't have one simply create a blank one. Even that can cause messages not showing up. Otherwise just put a support ticket at verthosting i have been struggling with this for over 16 hours..  ;)

Share this post


Link to post
Share on other sites
  • 0

apparently BEC isnt creating a log for me, i change the logdir = server1 to logdir = BEC.log and i created a blank file called BEC.log in the same folder as the config..i started up my server again and no logs are coming in.

Share this post


Link to post
Share on other sites
  • 0

apparently BEC isnt creating a log for me, i change the logdir = server1 to logdir = BEC.log and i created a blank file called BEC.log in the same folder as the config..i started up my server again and no logs are coming in.

When you first start your server and on your personal computer you're in lobby does it say "BEC initilizing"?

Share this post


Link to post
Share on other sites
  • 0

apparently BEC isnt creating a log for me, i change the logdir = server1 to logdir = BEC.log and i created a blank file called BEC.log in the same folder as the config..i started up my server again and no logs are coming in.

Just create a support ticket, james will fix it within some hours. ;) 

Share this post


Link to post
Share on other sites
  • 0

nope, i get Battleye Initilized but thats it.

I believe when I was with survivalservers I had set passwords on the config.cfg in the cfg's folder and I had a different one somewhere else and it was causing BEC to not start up. I'm not sure if that's your problem here but may aswell check if you have any mismatched passwords

Share this post


Link to post
Share on other sites
  • 0

I believe when I was with survivalservers I had set passwords on the config.cfg in the cfg's folder and I had a different one somewhere else and it was causing BEC to not start up. I'm not sure if that's your problem here but may aswell check if you have any mismatched passwords

are you talking about rcon passwords? i have an rcon passwords in the config but what different one are you talking about?

Share this post


Link to post
Share on other sites
  • 0

are you talking about rcon passwords? i have an rcon passwords in the config but what different one are you talking about?

re

There is the config.cfg file in your instance folder then there should be another password somewhere else, I'm not really sure it's been a really long time.

Share this post


Link to post
Share on other sites
  • 0

I use Vert Hosting and had the same problem. There are actually a few threads here about this same issue.

 

They will add a blank bans.txt file to your files. Basically, BEC is crashing because of no bans.txt file or something to that effect.

 

 

The bans.txt file in Bliss\BattlEye was missing, causing BEC to quit immediately after launching.

I've created a blank bans.txt file and BEC now appears to be connecting properly, so you may want to watch over the sohervice next time a restart/message is due.

 

oh and also about the batch file

 

 

A batch script should not be required to restart the server through the scheduler, you should use the #shutdown command instead (will terminate the ArmA process, which TCAdmin will automatically restart).

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

  • Similar Content

    • By HadeYZ
      Hello
       
      I've just bought myself a DayZ Epoch server, but I have some trouble with it.
      I've installed noxsicarius Epoch admin tools, but now whenever I try to buy building supplies as a non admin I get kicked by battleye.
      The error code is 214.
       
      Thanks in advance for any help
    • By C4-timah
      I am enjoying Grahame's EpochZ immensely.  However, if you are infected by the z's, after 30min you will die (animation for the 30min infection period is excellent btw). Upon death you will be shown the option to re-spawn. At that time you are promptly kicked by BattlEye for setvariable restriction #0:
      04.10.2018 00:14:33: C4-timah (23.119.200.220:2304) 57f9a830eeb99412623ce1c3d14b7d50 - #0 "ryanzombiesinfected" = 0 2:2877 Epoch_Male_F  
      If you are killed by the z's (beaten to death), upon your death you will also be shown a re-spawn option and then promptly kicked again for a BattlEye setvariable restriction #0:
      05.10.2018 21:53:02: C4-timah (23.119.200.220:2304) 57f9a830eeb99412623ce1c3d14b7d50 - #0 "ryanzombiesimmunity" = false 2:17479 Epoch_Male_F Adding
      !"ryanzombiesinfected" = 0 or
      !"ryanzombiesimmunity" = false does not appear to stop the BE kick. All the other filters in the setvariable.txt all start with  !=  which would indicates the filter must match exactly which would lead me to believe the key word that I need is something entirely different. I am using BattlEye Filter Manager to add the exceptions to the setvariable.txt. As you'll see, all the exceptions have !=" instead of !" unlike the last two that I have placed.
      //new2 5 "" !=(traderName|Offer|Accept|BUILD_SLOT|TRADE_ACTIVE|last_targeter|epoch_(antagobj|antagBomb)) !="bis_fnc_objectvar_var" !="bis_fnc_selectrespawntemplate_respawned" !="#(rev_enabled|var)" !="cup_tow_towedveh" !"ryanzombiesimmunity\" = false" !"ryanzombiesinfected\" = 0"  
      My rpt file shows the following error when killed by an EpochZ Zombie:
      17:44:02 BE protection activated for player id=726964973, name='whitehorse', msgType=285 setvariable.log:
      11.10.2018 17:44:02: whitehorse (75.80.233.157:1024) c2568b411cbd25fa774021698eade7c5 - #0 "ryanzombiesinfected" = 0 2:15917 Epoch_Male_F Ideas? Getting kicked every time you get killed by a Z has to be annoying to theses guys and I'd rather not lose the few that are consistently playing on our server. Any help is greatly appreciated.
    • By npploveyou
      Hi,
      I' using the plm script. When moving and releasing a crate, users are being kicked by SetPos #0. The log is as below:
      xxxx - #0 2:1469 USOrdnanceBox [6329,7782,306] xxxx - #0 2:535 USVehicleBox [1897,9119,289] I tried to add those box names to SetPos.txt under 5 line:
      5 !="RUVehicleBox" !="USVehicleBox" But it doesn't seem to work, users are still being kicked.
      Can you please provide some help how to add these boxes names (or actions) into BE filter?
      Thanks.
       
       
    • By Honey Bee
      Hey,
      after last Arma Update, BEC doesn´t work for my Epoch Servers. Did anybody had the same problem and con help me?
      Thanks
      Honey Bee
    • By XxPRkickassxX
      So I've tried many many times already to update my Battleye and nothing happens. I've uninstalled it and deleted the files and then gone to steam and verified the integrity of game files and still nothing! Whenever I try to join a game its starts downloading the mission files then I get kicked and in the bottom left side of my screen it says Server requiring Battleye version 1.239 up-to-date. I don't know what to do. This is not the first time that this has happened. In the past I used to to just be able to download it from the Battleye website but they no longer have the downloads. I'm trying to play Overwatch and Epoch. Those two mods are up to date. I've verified them like 10 times already. Maybe someone could share with me their battleye folders?
      Anyways please help and thanks in advanced!
  • Advertisement
  • Supporters
  • Discord

×
×
  • Create New...