Jump to content
  • 0

Bec won't start, closes instantly and no logs


Richie

Question

For the love of god will someone help me with Bec ? It surely hates me :(

I have Bec setup to run through FireDaemon, my startup looks like this :

 

wqojn4.png

 

FireDaemon just says it fails, running through a .bat file it starts a dos box and then instantly closes, I've no idea what's wrong :(

 

My Config.cfg looks like this :

# This config file is only provided as an example file.
# Edit it to sute your needs.
# For more info on how to edit this file. use the Readme.txt file or visit http://www.ibattle.org/install-and-configure


#--------------------------------------------------------------------------------------------------------
[Bec]
#--------------------------------------------------------------------------------------------------------

# Set the ip to your server. normally 127.0.0.1 will be fine.
Ip = 127.0.0.1


# Set the port to the server. default port is 2302
Port = 2302


# Set the path to the BattlEye directory that is currently in use by the server.
BePath = C:\ARMA3\Config_A3EPOCH\BattlEye


# Set the path to your Admins.xml file containing your admins.
Admins = A3_Admins.xml


# Set the path to your Commands.xml file.
Commands = Commands.xml


#--------------------------------------------------------------------------------------------------------
[Misc]
#--------------------------------------------------------------------------------------------------------

# Set which type of hacks that will be added to your banlist.
# 0 = none. 1 = GameHack. 2 = Battleye Hack. 3 = both GameHack & Battleye Hack.
# value 3 is set as default if this parameter is not defined.
Ban = 3

# Set the height & width of Becs console window
ConsoleHeight    = 30
ConsoleWidth    = 90


# Only allow english chars.
AsciiNickOnly = False


# Only allow english chars to be typed on the chat. Note, Warnings must be enabled. 0 or more.
AsciiChatOnly = False


# If AsciiChatOnly is set True. you can define none english chars that will be accepted.
# You separate each char with a , "note you need to define lower and upper case of the chars."
IgnoreChatChars    = €,£,æ,Æ,ø,Ø,å,Å,ö,ä,ü,ß


# Set the amount of warnings a player will get before kicked. -1 is disabled. 0 instant kick
# 1 == one warning on a bad word. next bad word results in kick
Warnings = 3


# Kick players who has listed chars in their name
#DisallowPlayerNameChars    = []{}()0123456789


# Min length, kicks players who has to short name.
MinPlayerNameLength    = 3


# Max length, kicks players who has to long name.
MaxPlayerNameLength    = 30


# Set the name of your Arma3server.exe if it has been renamed from arma3server.exe to something else!
# if the exe has its original name. comment it out.
# DO NOT SET FULL PATH TO THE EXE FILE
ServerExeName = arma3EPOCHserver.exe


# Set path to the file containing a list of bad words. Note, Warnings must be enabled. 0 or more.
WordFilterFile = BadWords.txt


# Set the path to the file containing whitelisted guids.
#WhiteListFile = WhiteList.txt


# Set custom whitelist kick message. Text must be in ascii letters.  MAX 58 CHARS. BE only does ascii on messages
#WhileListKickMsg = you are not whitelisted on this server.


# Kick people with offensive names
NickFilterFile = BadNames.txt


# Set the path to the Scheduler.xml file.
Scheduler = Scheduler.xml


# Kick people who are idleing in the lobby, kick will happen after given time, Min time is 90 sec. use 0 to disable this function.
KickLobbyIdlers    = 300


# If enabled. Bec will create seperate chat files for each channel along with the main file.
#ChatChannelFiles = false

# Set the amount of Normal players who can connect. Set it to -1 to disable it.
# If set to 0 it means only players who are listed in the Admins.xml, (or whatever you call it) will be able to connect to the server.
# Quick Example 1: server can holed 50 players. and you want to reserve 5 slots for admins. then set SlotLimit to 45.
# Quick Example 2: server can holed 50 players. and you want to reserve 5 slots for admins and 5 slots for friends. then set SlotLimit to 40,
# AND edit your admins.xml. ADD in all your frineds guid and remaining data, put them in group example 100. or whatever you feel likt.
# by using this method you can give some of your friends some access to some commands if you like or none.
# in general this is works like .Whitelisting X player slots for admins and friends, while leaving the remaining Y slots for public.
SlotLimit = -1

# Set the message people will get when they try to connect and is not whitelisted. Text must be in ascii letters.
SlotLimitKickMsg = The Server has reached its player limit.


# The amount of time Bec will wait for the server to start up.
Timeout = 30


#--------------------------------------------------------------------------------------------------------
[Reporter]
#--------------------------------------------------------------------------------------------------------
# Reporter account. Fill in the username and password for your reporter account.
# GameHacks, BattlEye Hacks will be reported to a database. all players who connect will also be checked against this database.

# Set the Username for your account
User = [Removed]


# Set the Password for your account
Password = [Removed]


#--------------------------------------------------------------------------------------------------------
[ChatRestriction]
#--------------------------------------------------------------------------------------------------------
# Set max amount of chat lines a player is allowed to send for each channel.
# Going passed the number will result in kick. -1 is disabled, 0 isntant kick.
# If the number is higher than 0 players will be sent warnings.

#Lobby = -1
#Global = -1
#Side = -1
#Group = -1
#Vehicle    = -1
#Command    = -1
#Commander = -1
#Direct = -1


#--------------------------------------------------------------------------------------------------------
[ChatSpam]
#--------------------------------------------------------------------------------------------------------

# Set max amount of chat lines per channel allowed within given time frame.
# Set the values to 0 to disable this function(s)

# Quick Example:
# Lobby = 5
# Lobby_Time_Lower = 10
# Lobby_Time_Upper = 15

# If the time between each new chatlines from a player is less than CHANNEL_Time_Lower the spam counter increases by + 1.
# Consider the CHANNEL (Lobby) as the spam counter.
# When a player has (CHANNEL - 1) in spam counting. a warning will be sent to whom it may consern.
# If the time between each new chatline from the player is Greater than CHANNEL_Time_Lower and Less than CHANNEL_Time_Upper the spam counter stay as it is.
# If the time since the last chatline is greater then CHANNEL_Time_Upper the spam counter is reset to 1.
# To get optimal result play around a bit with the values on your server.

#Lobby = 0
#Lobby_Time_Lower = 0
#Lobby_Time_Upper = 0

#Global = 0
#Global_Time_Lower = 0
#Global_Time_Upper = 0

#Side = 0
#Side_Time_Lower    = 0
#Side_Time_Upper    = 0

#Group = 2
#Group_Time_Lower = 1
#Group_Time_Upper = 3

#Vehicle    = 0
#Vehicle_Time_Lower = 0
#Vehicle_Time_Upper = 0

#Command = 0
#Command_Time_Lower = 0
#Command_Time_Upper = 0

#Commander = 0
#Commander_Time_Lower = 0
#Commander_Time_Upper = 0

#Direct = 0
#Direct_Time_Lower = 0
#Direct_Time_Upper = 0

 

My schedular.xml looks like this :

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

<Scheduler>

    <job id='0'>
        <day>1,2,3,4,5,6,7</day>
        <start>023000</start>
        <runtime>000000</runtime>
        <loop>0</loop>
        <cmd>say -1 Server will restart in 30 minutes</cmd>
    </job>

    <job id='1'>
        <day>1,2,3,4,5,6,7</day>
        <start>024500</start>
        <runtime>000000</runtime>
        <loop>0</loop>
        <cmd>say -1 Server will restart in 15 minutes</cmd>
    </job>
    
    <job id='2'>
        <day>1,2,3,4,5,6,7</day>
        <start>025000</start>
        <runtime>000000</runtime>
        <loop>0</loop>
        <cmd>say -1 Server will restart in 10 minutes</cmd>
    </job>

    <job id='3'>
        <day>1,2,3,4,5,6,7</day>
        <start>025400</start>
        <runtime>000000</runtime>
        <loop>0</loop>
        <cmd>#lock</cmd>
    </job>

    <job id='4'>
        <day>1,2,3,4,5,6,7</day>
        <start>025500</start>
        <runtime>000000</runtime>
        <loop>0</loop>
        <cmd>say -1 Server will restart in 5 minutes | LOG OUT NOW </cmd>
    </job>    
    
    <job id='5'>
        <day>1,2,3,4,5,6,7</day>
        <start>025900</start>
        <runtime>000000</runtime>
        <loop>0</loop>
        <cmd>say -1 Server will restart in 1 minute</cmd>
    </job>    
    
    <job id='6'>
        <day>1,2,3,4,5,6,7</day>
        <start>030000</start>
        <runtime>000000</runtime>
        <loop>0</loop>
        <cmd>C:\ARMA3\Kill_A3EPOCH_Server.bat</cmd>
    </job>    

    <job id='7'>
        <day>1,2,3,4,5,6,7</day>
        <start>000500</start>
        <runtime>001500</runtime>
        <loop>-1</loop>
        <cmd>say -1 Support this server, donate what you can afford to [email protected].</cmd>
    </job>
    
</Scheduler>



 

Link to comment
Share on other sites

13 answers to this question

Recommended Posts

  • 0

Which version of BEC.exe? :)

 

also your missing <cmdtype></cmdtype> from your xml, this will make it freak too ;)

 

If your still having issue after adding cmdtypes to your schedule I can come to your TS

Link to comment
Share on other sites

  • 0

Pro-tip:

 

Your .bat file windows close instantly when running a command?

Open an actual command window and run the command manually with all parameters you use in the .bat file. The window won't close and you'll see any error messages it's displaying.

Link to comment
Share on other sites

  • 0

I had posted this in an older thread that I found  before this one  but since this thread is way more recent, I figured I'd post here, too.

 

So for those of you that are running FireDaemon successfully, how did you do it, including BEC and scheduler.xml integration?

 

I'm running a main server and a test server on hosted bare iron (Win Server 2012R2 installed).  I had to enable Interactive Services Detection in order for FD to even work properly since ISD is no longer enabled by default.   I now have FD running and want to set processor affinity so my test instance and main instance don't step on each other.  So I imported the .XML config files from FD for both BEC and Arma2/Epoch and changed paths, etc. for ,my servers.  So first problem, where does the /affinity go?  I put it in the parameters string and get an "unknown hive error".  Anyway, I have four FD processes running.  1 - main server, 2 - main server BEC, 3 - test server, 4 - test server BEC.  They all start OK and if the Armas stop, FD restarts them.  But although the BEC processes are running, they cannot connect to the servers and therefore the scheduler never runs - so no in-game messages and no #shutdown.  They are referencing the proper Arma instances because I went to move my test server files to another location and couldn't move the BEC folder because something (the BEC FD process) had it open.  Once I stopped the process, I could move the directory and files.  I've gone over the BEC tabs in FD over and over and cannot see anything obvious that is wrong.  So is there something subtle that I missed? 

 

I had both main and test server with BEC running fine with batch files I had created.  So I know my BEC, Arma/Epoch config files, and scheduler.xml are correct.  All I did was stop the batch file execution and created the FD processes as outlined above.

 

Thanks,

Bob

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement
  • Discord

×
×
  • Create New...