Sign in to follow this  
Followers 0
Dunsparth

[Solved] BEC Scheduler

4 posts in this topic

My Scheduler doesen't seem to be working maybe somebody can help me?
I Have no errors in my error log but still see nothing inside my chat.


Here is my config.cfg
 

Spoiler

# 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 = 23.250.112.194


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


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


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


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


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

# Auto run loadbans when ban file(s) changes. 
# 1 or True will turn it on.
# 0 or False will turn it off. 
# If this parameter is not defined it will use False as default.

AutoLoadBans = True

# 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 names of your custom ban files, Separate each file with "," (comma): file1.txt, banfile2.txt, newfile.txt
# If you do not use any custom ban files. delete this option or leave this option commented.
# This option will check ban files for changes and automatic do a loadbans file when a file gets changed
# Do not specify the default bans.txt file here.
# BeCustomBanFiles = Bans1.txt, file2.txt, file3.txt


# Set the height & width of Becs console window
ConsoleHeight    = 45
ConsoleWidth    = 165


# 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 = True


# 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 when they connect
# DisallowPlayerNameChars    = []{}()0123456789


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


# Max length, kicks players who has to long name when they connect.
# MaxPlayerNameLength    = 18


# 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 = arma3server.exe


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


# 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    = 180


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

# 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 = alfred


# Set the Password for your account
#Password = 123456


#--------------------------------------------------------------------------------------------------------
[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 instant 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 concern.
# 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


 



Here is my Scheduler.xml

 

Spoiler

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

<!-- 
This file is only provided as an example file and is not practical to use in real life.
Make sure you take a copy of this file rename it and keep the orginale intact for orginale refrance.
And Start using your new file Now!!

Web Doc : http://www.ibattle.org/install-and-configure/setting-up-the-scheduler/

BE Commands supported by the scheduler system are:

say -1 some text
loadbans
loadscripts
loadevents
writebans
maxping 250
#shutdown
#restart
#reassign
#lock
#unlock
#mission filename (without the .pbo extension)
systime
uptime
fortune
exit


*****************************************************************************************************
Description:
*****************************************************************************************************


Schedules are created by adding a job with id.
The first schedule should always start with id="0"

<Scheduler>
    <job id="0">
        <day></day>
        <start></start>
        <runtime></runtime>
        <loop></loop>
        <cmd></cmd>
    </job>
    <job id="1">
        <day></day>
        <start></start>
        <runtime></runtime>
        <loop></loop>
        <cmd></cmd>
    </job>
</Scheduler>    

The job tag has 5 sub tags.

starting with:

<day>.../day>

The day of the week the schedule should run on.
Days are seperated by ',' 
<day>n</day> or <day>n,n+</day>

Monday starts with 1!

All days
<day>1,2,3,4,5,6,7</day>

Monday and Friday only.
<day>1,5</day>

Next:
<start>......</start> 
This tag may have one of two input format.

Format 1:
Contains 3 segments where each segment is a size of 2 in range of 00 - 99
Hour Min  Sec
[nn] [nn] [nn]
nnnnnn
Max value is 999999 and min value is 000000

<start>000090</start>
This will make the schedule execute 90 seconds after bec has started up and logged in.
Note that:

<start>000130</start>
Will also make the schedule execute 90 seconds after bec has started up.
as 90 sec is the same as 1 min and 30 sec

 
Format 2:
Contains 2 segments where each segment is a size of 2 in range of 00 - (23&59) and each segment is seperated by ':'

Hour   Min    Sec
[nn] : [nn] : [nn]

<start>23:05:30</start>
This will make the schedule execute precice at 23:05:30

To execute a schedule at midnight use:
<start>00:00:00</start>

To execute a schedule at noon use:
<start>12:00:00</start>


Next:
<runtime>....../runtime>
This tag uses the same format as the <start> tag format 1 (hhmmss), it also only work when the loop is set to -1 or higher than 0. ie 10
<runtime>hhmmss</runtime>


Next:
<loop>N</loop> 

If -1 is used it means it will loop forever.
If 0 is used the job will only be run once.
If a number higher than 0 is used it will loop the set numbers.
Each loop interval is set in the runtime tag. 

Example.
<runtime>001000</runtime>
<loop>5</loop>

this means that the job will loop 6 times with a 10 minute delay between each job after the jobstart
once "start" + number of loops

Next:
<cmd>Command</cmd>
Set the command that is to be executed.

you can use external commands. example 
<cmd>c:\path\myfile.bat</cmd>

or just use a internal command.
<cmd>uptime</cmd>

SEE THE SCHEDULER_FAQ.txt for more info

-->


<Scheduler>

    <job id='0'>
        <day>1,2,3,4,5,6,7</day>
        <start>001000</start>
        <runtime>003000</runtime>
        <loop>-1</loop>
        <cmd>say -1 DONATIONS HELP KEEP THE SERVER ALIVE FEEL FREE TO DONATE AT WWW.CONVICTIONGAMING.COM</cmd>
    </job>
    
    <job id='1'>
        <day>1,2,3,4,5,6,7</day>
        <start>001300</start>
        <runtime>003000</runtime>
        <loop>-1</loop>
        <cmd>say -1 IF YOU NEED TO CONTACT AN ADMIN PLEASE HOP ONTO DISCORD, OUR DISCORD CAN BE FOUND ON OUR WEBSITE.</cmd>
    </job>
    
    <job id='2'>
        <day>1,2,3,4,5,6,7</day>
        <start>001600</start>
        <runtime>003000</runtime>
        <loop>-1</loop>
        <cmd>say -1 PLEASE VISIT WWW.CONVICTIONGAMING.COM FOR SERVER RULES AND INFO.</cmd>
    </job>
    
    <job id='3'>
        <day>1,2,3,4,5,6,7</day>
        <start>002000</start>
        <runtime>003000</runtime>
        <loop>-1</loop>
        <cmd>say -1 PLEASE REPORT PROBLEMS AND BUGS ON OUR WEBSITE.</cmd>
    </job>
    
    <job id='4'>
        <day>1,2,3,4,5,6,7</day>
        <start>002500</start>
        <runtime>003000</runtime>
        <loop>-1</loop>
        <cmd>say -1 WE ASK YOU KINDLY TO RESPECT ALL MEMBERS AND STAFF AT CONVICTION GAMING.</cmd>
    </job>
    
    <job id='5'>
        <day>1,2,3,4,5,6,7</day>
        <start>003000</start>
        <runtime>003000</runtime>
        <loop>-1</loop>
        <cmd>say -1 THIS SERVER RESTARTS EVERY 3 HOURS - TYPE !UPTIME IN SIDE CHAT TO SEE THE SERVER UPTIME</cmd>
    </job>
    
    <job id='6'>
        <day>1,2,3,4,5,6,7</day>
        <start>000400</start>
        <runtime>003000</runtime>
        <loop>-1</loop>
        <cmd>say -1 WELCOME TO CONVICTION GAMING.</cmd>
    </job>

    
    <job id='7'>
        <day>1,2,3,4,5,6,7</day>
        <start>020000</start>
        <runtime>020000</runtime>
        <loop>0</loop>
        <cmd>say -1 RESTART IN ONE HOUR</cmd>
    </job>
    
    <job id='8'>
        <day>1,2,3,4,5,6,7</day>
        <start>023000</start>
        <runtime>023000</runtime>
        <loop>0</loop>
        <cmd>say -1 RESTART IN 30 MINUTES -- RESTART IN 30 MINUTES</cmd>
    </job>
    
    <job id='9'>
        <day>1,2,3,4,5,6,7</day>
        <start>025000</start>
        <runtime>025000</runtime>
        <loop>0</loop>
        <cmd>say -1 RESTART IN 10 MINUTES - START PREPARING TO LOG OUT</cmd>
    </job>
    
    <job id='10'>
        <day>1,2,3,4,5,6,7</day>
        <start>025500</start>
        <runtime>025500</runtime>
        <loop>0</loop>
        <cmd>say -1 RESTART IN 5 MINUTES - SAVE GEAR AND LOG OUT</cmd>
    </job>
    
    <job id='11'>
        <day>1,2,3,4,5,6,7</day>
        <start>025800</start>
        <runtime>025800</runtime>
        <loop>0</loop>
        <cmd>say -1 RESTART IN 2 MINUTES - SAVE GEAR AND LOG OUT</cmd>
    </job>
    
    <job id='12'>
        <day>1,2,3,4,5,6,7</day>
        <start>025900</start>
        <runtime>030000</runtime>
        <loop>0</loop>
        <cmd>say -1 RESTART IN 1 MINUTES - SAVE GEAR AND LOG OUT</cmd>
    </job>
</Scheduler>


 

I have nothing in the error log.

Share this post


Link to post
Share on other sites

Inside the config edit this:

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

to this

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

1 person likes this

Share this post


Link to post
Share on other sites
Advertisement
25 minutes ago, StokesMagee said:

Inside the config edit this:

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

to this

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

Wow i am stupid...
Thanks sometimes that extra eye helps.

 

Share this post


Link to post
Share on other sites
Advertisement
Guest
This topic is now closed to further replies.
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.