Admin file contains a error guid tag is not correct location id 0

Менял сборку, долгая история, в общих чертах до этого работало, сейчас при запуске он чекает апдейт и падает В belog Скрытый текст 01:24:29 : Closing socket & exiting! В error Скрытый текст 01:24:24 : Admin file contains a error. guid tag is not correct, Location id=0 01:24:29 : Unexpected e...

# Конфигурация BEC.
# Перевод TheFirstNoob.
# Обновления тут (ENG) http://www.ibattle.org/
# Если вы хотите что-то отключить, то используйте значок # — Это закомментирует команду или нужную вам строчку.

#———————————————————————————————————
[Bec]
#———————————————————————————————————

# Укажите IP-Адрес вашего сервера. Можете использовать 127.0.0.1 и все будет нормально.
Ip = 127.0.0.1


# Укажите порт вашего сервера. По умолчанию 2302.
Port = 2302

#———————————————————————————————————

# Укажите путь в BattEye. То есть там где стоят фильтра.
BePath = D:GamesSteamsteamappscommonArma 2 Operation ArrowheadBattlEye

# Подключите файл Commands.xml (По умолчанию уже подключен).
# Позволяет выполять внутриигровые команды из списка commands.xml
Commands = Commands.xml

# Подключите файл Admins.xml (По умолчанию уже подключен).
# Отвечает за список администрации BEC и резервные слоты (Настраивается в Admins.xml)
Admins = Admins.xml


#———————————————————————————————————
[Misc]
#———————————————————————————————————

# Автозапуск лоадбанса,когда стоит запрет на изменение фаилов
# 1 включить
# 0 выключить 
# Если параметр не определен он будет использовать значение False по умолчанию. 

AutoLoadBans = True

# Укажите как BEC будет банить читаков.
# 0 = Никак. 1 = Только Встроенный игровой АнтиЧит. 2 = Только BattEye АнтиЧит. 3 = Оба варианта. 
# Установите 3 если не можете определиться.
# Внимание! InfiSTAR и другие АнтиЧиты не считаются!!!
Ban = 0

#———————————————————————————————————

# Укажите размеры Консольного окна BEC.
ConsoleHeight    = 30
ConsoleWidth    = 100

# Сколько секунд BEC будет ждать при зависании или включении сервера.
# Рекомендуется: 30
Timeout = 30

# Если указать = True, то BEC будет создавать Логи чата на каждый канал.
# Если указать = False, то BEC будет создавать Лог чата в котором будут сразу все каналы.
ChatChannelFiles = false

#———————————————————————————————————

# Использовать на сервере только ASCII НикНеймы (Имеется ввиду English Only!)
# Рекомендуется: True (Если отключить, то могут быть проблемы)
AsciiNickOnly = False

# Кикать игроков, если они имеют следующие символы в НикНейме.
#DisallowPlayerNameChars =

# Минимальная допустимая длина НикНейма.
MinPlayerNameLength    = 4

# Максимальная допустимая длина НикНейма.
MaxPlayerNameLength    = 16

#———————————————————————————————————

# Использовать на сервере только ASCII чат (Имеется ввиду English Only!)
# Рекомендуется: False (Если включить, то все смогут писать в чат только на Английском!)
AsciiChatOnly = False

# Для работы данной функции убедитесь что AsciiChatOnly = True!
# Какие символы BEC будет разрешать использовать в чате.
#IgnoreChatChars =

# Укажите количество предупреждений за плохие слова BadWords.txt.
# Укажите = -1, чтобы Выключить. Укажите = 0, чтобы сразу Кикало. Укажите = N, чтобы было N-ое количество предупреждений, а последний Кик. (N — Любое число)
Warnings = -1

#———————————————————————————————————

# Подключите файл BadNames.txt (По умолчанию пуже подключен).
# Отвечает за плохие или запрещенные ники на сервере (Настраивается в BadNames.txt)
NickFilterFile = BadNames.txt

# Подключите файл BadWords.txt (По умолчанию пуже подключен).
# Отвечает за плохие или запрещенные слова в чате (Настраивается в BadWords.txt)
WordFilterFile = BadWords.txt

# Подключите файл WhiteList.txt (По умолчанию Отключен!).
# Отвечает за Белый Лист по GUID и только!
# WhiteListFile = WhiteList.txt

# Укажите сообщение которое будет выводиться если BEC не находит игрока в Белом Списке. (Поддерживается только ASCII!)
#WhileListKickMsg = Sorry, you are not WhiteListed!

# Подключите файл Scheduler.xml (По умолчанию уже подключен).
# Это планировщик. Отвечает за рестарты, сообщение, определенные доступные команды в любой удобный вам промежуток времени и количестве использования.
Scheduler = Scheduler.xml

#———————————————————————————————————

# Если игрок будет слишком долго находиться в Лобби, то его кикнет с сервера.
# Укажите время через которое игрока кикнет с сервера (В секундах!)
# Укажите = 0, чтобы отключить эту функцию.
KickLobbyIdlers    = 600

#———————————————————————————————————

# Данная функция резервирует слоты под Нужных вам людей, то есть вы сможете попасть на сервер при Любом Онлайне на вашем сервере.
# Пример №1: Ваш сервер поддерживает всего 50 игроков и вы хотите зарезервировать 5 слотов под Администрацию, то установите в SlotLimit = 45.
# Пример №2: Ваш сервер поддерживает всего 50 игроков и вы хотите зарезервировать 5 слотов под Администрацию и 5 слотов под ваших Друзей, то установите в SlotLimit = 40.
# Пример №3: Ваш сервер поддерживает всего 50 игроков и вы хотите зарезервировать 5 слотов под Администрацию, 5 слотов под ваших Друзей и 5 слотов под VIP, то установите в SlotLimit = 34.
# Список для Резервных слотов редактируется в файле Admins.xml.
# Резервные Слоты работают так же с Белым Листом.
# Установите = -1, чтобы отключить данную функцию.
SlotLimit = -1


#———————————————————————————————————
#[Reporter]
#———————————————————————————————————

# Укажите данные вашего аккаунта от MySQL которые вводили в HiveExt.ini.
# Читы, логи BattEye будут регистрироваться через вашу Базу Данных. Каждый игрок будет проверяться через БД при присоединении на сервер.

#Host = localhost
#Type = MySQL
#Port = 3306
#Database = dayz_epoch
#Username = root
#Password = 

#———————————————————————————————————
[ChatRestriction]
#———————————————————————————————————

# Укажите количество сообщений которые могут писать игроки в течении игры на каждый Чат-Канал. 
# Укажите = -1 чтобы отключить, 0 кикать сразу без предупреждений.
# Если указать более 0, то игрок будет получать предупреждения сколько он еще может писать в чат.

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


# Укажите промежуток времени между сообщениями, которое сможет написать игрок в определенном Чат-Канале.
# Укажите = 0 чтобы отключить.

# Пример заполнения:
# Lobby = 5
# Lobby_Time_Lower = 10
# Lobby_Time_Upper = 60

# Параметр Lobby отвечает за какой-то канал чата, в данном случае чат в лобби. 
# Параметр Lobby_Time_Lower отвечает за допустимый интервал между сообщениями (В секундах).
# Параметр Lobby_Time_Upper сбрасывает счетчик ограничения чата (В секундах).
# Рассмотрим более подробно.
# Если игрок напишет первое сообщение в лобби, то следующее он напишет только через 10 секунд, но будет оповещен об ограничении в чате и будет иметь лимит сообщений.
# Как только пройдет 60 секунд после написания сообщения, то счетчик лимита сброситься до нуля (То есть ограничения обнуляться).

#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

Источник

  • Home

  • Forums

  • DayZ Mod / Arma Scripting & Editing

  • Trouble Shooting

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

Scheduler problem ;)


  • Thread starter

    IvertizPL


  • Start date

    Jan 26, 2015

  • #1

Hello! Sorry for new thread, I have problem with my Scheduler.xml it doesn’t work. I try other settings but nothing. Please help my i have 4 hours restarts on server at : 04:00, 08:00, 12:00, 16:00, 20:00, 00:00 hrs. I delete some lines from code ( too many words)

Color = 0e

AsciiNickOnly = False

# DisallowPlayerNameChars    = [](){}<>/^|§!#%&@£¤¨

MaxPlayerNameLength    = 24

sofortiger Kick.
Warnings = 4

AsciiChatOnly = False

IgnoreChatChars    = æøåáàéèäöüß

WordFilterFile = BadWords.txt

# WhiteListFile = WhiteList.txt

NickFilterFile = BadNames.txt

Timeout = 200

KickLobbyIdlers    = 300

Scheduler = Scheduler.xml

ChatChannelFiles = true

# Ts3 = Ts3.xml

Scheduler.xml

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<?xml-stylesheet href="acs.xsl" type="text/xsl" ?>
<!--

<Scheduler>

<!-- Schedular to be shown all days in the week. -->
<!-- show text ingame every 20 min -->
<job id="0">
<time>000005</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Don't glitch! </cmd>
<cmdtype>0</cmdtype>
</job>

<!-- show text ingame every 60 min -->
<job id="1">
<time>006000</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 This server restarts 6 times per day, 04:00, 08:00, 12:00, 16:00 and 00:00.</cmd>
<cmdtype>0</cmdtype>
</job>


<!-- *** RESTARTS *** -->
<!-- 5 min to the 04:00 restart -->
<job id="2">
<time>03:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="3">
<time>03:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="4">
<time>03:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="5">
<time>03:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>
<!-- 08:00 restart -->
<job id="6">
<time>07:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="7">
<time>07:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="8">
<time>07:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="9">
<time>07:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<!-- 30 min to the 12:00 restart -->
<job id="10">
<time>11:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>
<!-- 12:00:00 restart -->

<job id="11">
<time>11:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="12">
<time>11:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="13">
<time>11:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="14">
<time>15:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="15">
<time>15:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="16">
<time>15:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="17">
<time>15:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="18">
<time>19:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="19">
<time>19:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="20">
<time>19:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="21">
<time>19:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="22">
<time>23:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="23">
<time>23:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="24">
<time>23:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="25">
<time>23:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>
</Scheduler>

It’s Scheduler for 4 hours restarts at 04:00, 08:00, 12:00, 16:00, 20:00, 00:00 hrs Please help me and sorry for many threads ;) Greetings

Last edited: Jan 26, 2015

  • #2

ShootingBlanks


  • #3

08:51:39 : Admin file contains a error. guid tag is not correct, Location id=0
08:54:47 : Admin file contains a error. guid tag is not correct, Location id=0
08:58:11 : Scheduler file contains a error. start tag missing where id=0
09:03:45 : Admin file contains a error. guid tag is not correct, Location id=0

Error log from latest restart

Full Scheduler.xml:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<?xml-stylesheet href="acs.xsl" type="text/xsl" ?>
<!--



#TIME/ZEIT

    <time>......</time>
    Diese Einstellung hat Zwei mögliche Formate:

#DELAY/VERZÖGERUNG
 
    <delay>nnnnnn</delay>
    Stunde Minute Sekunde
    [nn] [nn] [nn]
    Diese Einstellung verwendet das "Format 1" von <time>.
    Das Delay (Verzögerung) funktioniert nur, wenn bei <time> ebenfalls das Format 1 verwendet wird.

    Beispiel:
    <delay>001000</delay>
    Der Job wird 10 Minuten nach dem Serverstart ausgeführt (sofern <time>000000</time> gesetzt wurde)
    Ansonsten läuft nach Ablauf des Delays der Timer an.
    Hat man <delay>001000</delay> und <time>001000</time> gesetzt, läuft nach 10 Minuten der Timer an, der Job wird also erst nach 20Minuten ausgeführt.


#DAY/WOCHENTAG

    <day>...</day>
    An welchen Wochentagen der Job ausgeführt werden soll.
    Die Tage werden durch ein ',' (Komma) getrennt.
    <day>n</day> oder <day>n,n,n</day>

    1=Montag
    2=Dienstag
    3=Mittwoch
    4=Donnerstag
    5=Freitag
    6=Samstag
    7=Sonntag

    <day>1,2,3,4,5,6,7</day>
    Der Job wird an allen Wochentagen ausgeführt.

    <day>1,5</day>
    Der Job wird nur am Freitag und am Sonntag ausgeführt.


#LOOP/WIEDERHOLUNG

    <loop>1</loop>
    Der Job wird wiederholt ausgeführt (wie oft wird mittels Time festgelegt).
    Hierzu wird ebenfalls das Time Format 1 benötigt.

    <loop>0</loop>
    Der Befehl wird nur einmalig ausgeführt.
    Bei <time>000200</time> Zwei Minuten nach dem Serverstart und dann nie wieder.
    Bei <time>20:00</time> um genau 20:00Uhr


#COMMAND/BEFEHL

    <cmd></cmd>
    Der Befehl, welcher ausgeführt werden soll
    Beispiele:
    <cmd>say -1 TEXT</cmd>
    <cmd>#shutdown</cmd>
    etc.


#CMDTYPE/BEFEHLSTYP

    <cmdtype>0</cmdtype>
    0 = Interner Befehl (say -1, #shutdown, #restart, etc.)

    <cmdtype>1</cmdtype>
    1 = Extern auszuführendes Script (loadscript *.bat oder loadscript *.cmd)
    Diese Funktion steht bei Nitrado, aus sicherheitsgründen, nicht zur Verfügung!
    Deswegen immer <cmdtype>0</cmdtype> verwenden.

Folgende Befehle werden bei <cmdtype>0</cmdtype> unterstützt:
say -1 TEXT        // Textnachricht an alle Spieler
#lock            // Server abschliessen (keine neuen Spieler können mehr drauf)
#unlock            // Server wieder öffnen
#shutdown        // Herunterfahren des Server (Nitrado.net Server werden automatisch neu gestartet)
#restart        // Neustarten der Mission (Server läuft weiter)
loadbans        // Lädt die Banliste
loadscripts        // Lädt die Scriptliste (scripts.ini)
loadevents        // Lädt die Events Liste
writebans        // Schreibt alle Bans in eine Datei
maxping 250        // Maximal erlaubter Ping
#reassign        // Missionsneustart mit Erkennung der Spieleranzahl (wird für DayZ nicht benötigt)
#mission filename (ohne die .pbo Endung) // Bestimmte Mission starten (wird für DayZ nicht benötigt)


Der erste Job beginnt immer mit der id="0"

*****************************************************************************************************
Anfang des Schedulers:
*****************************************************************************************************
-->


<Scheduler>

<!-- Schedular to be shown all days in the week. -->
<!-- show text ingame every 20 min -->
<job id="0">
<time>000005</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Don't glitch! </cmd>
<cmdtype>0</cmdtype>
</job>

<!-- show text ingame every 60 min -->
<job id="1">
<time>006000</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 This server restarts 6 times per day, 04:00, 08:00, 12:00, 16:00 and 00:00.</cmd>
<cmdtype>0</cmdtype>
</job>


<!-- *** RESTARTS *** -->
<!-- 5 min to the 04:00 restart -->
<job id="2">
<time>03:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="3">
<time>03:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="4">
<time>03:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="5">
<time>03:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>
<!-- 08:00 restart -->
<job id="6">
<time>07:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="7">
<time>07:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="8">
<time>07:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="9">
<time>07:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<!-- 30 min to the 12:00 restart -->
<job id="10">
<time>11:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>
<!-- 12:00:00 restart -->

<job id="11">
<time>11:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="12">
<time>11:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="13">
<time>11:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="14">
<time>15:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="15">
<time>15:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="16">
<time>15:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="17">
<time>15:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="18">
<time>19:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="19">
<time>19:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="20">
<time>19:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="21">
<time>19:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="22">
<time>23:30:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 30 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="23">
<time>23:45:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 15 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="24">
<time>23:55:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 5 min.</cmd>
<cmdtype>0</cmdtype>
</job>

<job id="25">
<time>23:59:00</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>0</loop>
<cmd>say -1 This server will restart in 1 min.</cmd>
<cmdtype>0</cmdtype>
</job>
</Scheduler>

Last edited: Jan 27, 2015

  • #4

ShootingBlanks


I see the problem now .. someone wrote it all in a gobbledegook :p

As I said before, the format of scheduler jobs has changed
this is what you used

<job id="0">
<time>000005</time>
<delay>000000</delay>
<day>1,2,3,4,5,6,7</day>
<loop>1</loop>
<cmd>say -1 Don't glitch! </cmd>
<cmdtype>0</cmdtype>
</job>

this is how its used on the ibattle.org documentation for scheduler.xml

<job id="0">
<day>1,2,3,4,5,6,7</day>
<start>000005</start> 
<runtime>003000</runtime>
<loop>1</loop> 
<cmd>say -1 Don't glitch!</cmd>   
</job>

So that would probably be the error in your scheduler.xml file. BEC is looking for the <day> tag but you supply the <time> tag.

And you have a malformed guid in the admin file. http://ibattle.org/install-and-configure/define-admins/ You need to use the BE guid that you get from typing #beguid in chat

  • #5

Really thanks for help but now I have other problem, second day and I have hackers attack, they are destroy all base and delete all vehicles. I resque base but I can’t resque vehicles. And server work some hours and now all my players can’t get in to the servers because they are stuck on Loading Screen ;(

Last edited: Jan 27, 2015

  • #6

ShootingBlanks


  • Home

  • Forums

  • DayZ Mod / Arma Scripting & Editing

  • Trouble Shooting

  • This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
Источник

I never been baaned but now I feel myself in danger because there is possiblity to be banned without beeing a cheater.

Why do you feel your self in danger?

You have nothing to worry about if your not using any cheat tools while playing arma on servers utilizing Bec + Reporter

You haven’t answeared my question … and you don’t want to read carefully one sentence.

«If someone is banned and don’t know which server banned him first who should that «banned guy» ask about baan reason and baan appeal?»

Eventually you can answear — what that «banned player» should do next to figure out what happened?

I choose not to answer that because… (now this may come of a bit blunt but …)

If he cant remember when and where he was banned by Bec. maybe its time to visit the doctor for a headcheck…

How often do you get banned with reason GameHack XY or Battleye Hack XY ?

And as of what he should do. simple, contact server owners. We can provide contact info if GUID is provided if absolutely necessary.

1. Battleye will baan confirmed cheaters. That guy is not banned globally by BE that’s mean BE don’t see him as user of cheat engine, am I right?

2. Do you think that your program knows better than BE who cheats or not? — BE means fully professional program, years of experince, tons of money spend for it ect. Your program use just a litle part of BE.

1 * That correct. BE does not put a global ban #XYZ for CheatEngine, it kicks players using it.

However. CheatEngine is used 99.9% of the time for cheating and i dont give a rats ass if you only use it in game X,Z,Y.

In my opinion as with many other server admins is that, using tools like this means you have a cheaters mentality, and we dont want people like that on our server.

If you absolutely need to use tools like this, make sure you close it before playing arma. You never know which server uses Bec + Reporting.

2 * Better ? sorry you have misunderstood the purpose of Bec. its only used to extend actions done by BE.

I never stated that Bec is better than BE, When in fact Bec will not work without BE.

And Bec does not do any Cheatdetection by itself, its all done by BE.

In my opinion idea of your program is good but not without bugs.

For example there are no rules who contact when someone is banned,

what exactly hacker done (cheating is not an aswear — everyone can sad that, if BE will baan telling only this it will never be official tool in games), ect.

In real life when you made a crime you will be informed what you done , who you harmed ect.

but here just punishment without information. Blind banning players is bad as cheating.

I don’t wanted offence you but honest players need to know what to do if they are banned by mistake or other reason.

My intention is to help you make that programm more fair and more usefull.

Please distinguish Bugs from lack of contact info or ways to reach server owners.

Its clearly stated that you should contact the server where the ban happened on. (usually a quick google should give you their website)

Once you get in contact with the admin and provide him the GUID he should be able to tell you why the ban was set.

Ie. Battleye Hack #25 and decide to set it inactive if they choose to.

Also If BE does false positive on detections. Bans happened during this period will be deleted.

In real life admins decide them self who they want playing on their server and what tools to use.

Usually its not a democracy on servers. communities|clans has to pay rent for servers.

So they are in their full right to decide, what they want to run on their server and who they want playing on their server.

Their server, their rules, they are not obligated to do anything about bans|kicks issues.

They do as they feel fit on their own server that they pay for..

When server admins are using the Bec Reporter they have the option to set the ban inactive or put an exception on the banned GUID through bansys.info

I dont get offended. a little criticism is always good.

Bec is not the perfect tool, there is no such this as a perfect tool.

Finally,

Bec is a tool for the community and no server is required to use it. «to my knowledge».

If they use Bec they are also not obligated to use the «(game hack|battleye hack) Reporter» its fully optional.


Edited August 3, 2014 by nuxil

Источник
  • Remove From My Forums

  • Вопрос

  • When trying to export a site from a development environment using the stsadm command I am getting the following error in the export log and nothing is export at all from the site:

    [8/14/2007 12:10:57 AM]: FatalError: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
       at System.Guid..ctor(String g)
       at Microsoft.SharePoint.Deployment.FieldTemplateSerializer.ParseLookups(SPField fieldTemplate, ExportObjectManager objectManager)
       at Microsoft.SharePoint.Deployment.FieldTemplateSerializer.GetDataFromObjectModel(Object obj, SerializationInfo info, StreamingContext context)
       at Microsoft.SharePoint.Deployment.DeploymentSerializationSurrogate.GetObjectData(Object obj, SerializationInfo info, StreamingContext context)
       at Microsoft.SharePoint.Deployment.XmlFormatter.SerializeObject(Object obj, ISerializationSurrogate surrogate, String elementName, Boolean bNeedEnvelope)
       at Microsoft.SharePoint.Deployment.XmlFormatter.Serialize(Stream serializationStream, Object topLevelObject)
       at Microsoft.SharePoint.Deployment.ObjectSerializer.Serialize(DeploymentObject deployObject, Stream serializationStream)
       at Microsoft.SharePoint.Deployment.SPExport.SerializeObjects()
       at Microsoft.SharePoint.Deployment.SPExport.Run()

    The site is working perfectly in the development environment.

    Any clues?

Ответы

  • For anyone else who might stumble across this thread…
     I Found that I had to remove the  {  and the }  from every ID= 
    were there was a {  and a }   in the fields.xml

    basicly when i was done there were no  {  or  }  in the eniter XML file.

    This seems to have made it work…  
    The

    xml file is called «fields.xml» and was located at c:program filescommon filesmicrosoft sharedweb server extensions12/templatefeaturestsatypes

    • Предложено в качестве ответа

      30 марта 2009 г. 8:44

    • Помечено в качестве ответа
      Mike Walsh FIN
      30 марта 2009 г. 11:17

Источник

Got an error

«Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)»

The GUID input is «68f0eaed-189e-4c65-8cf8-475539d6f21b»

    context.Countries.AddRange(GetCountryData(Path.Combine(AppDomain.CurrentDomain.BaseDirectory, "csv", "country.csv")));

    await context.SaveChangesAsync();


    public List<Data.Country> GetCountryData(string filePath)
    {
        string csvRead = File.ReadAllText(filePath);
        string[] csvFileRecord = csvRead.Split('n');
        List<Data.Country> dataRecordList = new List<Data.Country>();

        foreach (var row in csvFileRecord.Skip(1))
        {
            if (!string.IsNullOrEmpty(row))
            {
                var cells = row.Split(',');
                var dataRecord = new Data.Country
                {
                    Id = Guid.Parse(cells[0]),
                    Code = cells[1],
                    Name = cells[2]
                };
                dataRecordList.Add(dataRecord);
            }
        }

        return dataRecordList;
    }

CSV file

"id","code","name"
"68f0eaed-189e-4c65-8cf8-475539d6f21b","AX","Åland Islands"
"76cf600f-7bf6-40fb-8803-142eac60f3dd","AL","Albania"
...

EDITED Updated code, it now gets the correct GUID value yet an error still occurs

My input "68f0eaed-189e-4c65-8cf8-475539d6f21b"

fail: MyApp.ContextSeed[0]
      Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
info: Microsoft.EntityFrameworkCore.Database.Command[20101]
      Executed DbCommand (1ms) [Parameters=[], CommandType='Text', CommandTimeout='30']
      SELECT CASE
          WHEN EXISTS (
              SELECT 1
              FROM public.country AS c)
          THEN TRUE::bool ELSE FALSE::bool
      END

Источник

Here’s a copy of the full stack trace for this issue:

System.FormatException: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
at System.Guid.GuidResult.SetFailure(ParseFailureKind failure, String failureMessageID, Object failureMessageFormatArgument, String failureArgumentName, Exception innerException)
at System.Guid.TryParseGuidWithNoStyle(ReadOnlySpan1 guidString, GuidResult& result) at System.Guid.TryParseGuid(ReadOnlySpan1 guidString, GuidStyles flags, GuidResult& result)
at System.Guid..ctor(String g)
at Microsoft.SqlTools.ServiceLayer.Connection.ReliableConnection.ReliableSqlConnection.RetrieveSessionId() in D:a1ssrcMicrosoft.SqlTools.ServiceLayerConnectionReliableConnectionReliableSqlConnection.cs:line 437
at System.Data.Common.DbConnection.OnStateChange(StateChangeEventArgs stateChange)
at System.Data.ProviderBase.DbConnectionClosedConnecting.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource1 retry, DbConnectionOptions userOptions) at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource1 retry)
at System.Data.SqlClient.SqlConnection.OpenAsyncRetry.Retry(Task`1 retryTask)
— End of stack trace from previous location where exception was thrown —
at Microsoft.SqlTools.ServiceLayer.Connection.ReliableConnection.ReliableSqlConnection.<>c__DisplayClass28_0.<b__0>d.MoveNext() in D:a1ssrcMicrosoft.SqlTools.ServiceLayerConnectionReliableConnectionReliableSqlConnection.cs:line 298
— End of stack trace from previous location where exception was thrown —
at Microsoft.SqlTools.ServiceLayer.Connection.ConnectionService.TryOpenConnection(ConnectionInfo connectionInfo, ConnectParams connectionParams) in D:a1ssrcMicrosoft.SqlTools.ServiceLayerConnectionConnectionService.cs:line 542

Источник

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Adjusttokenprivileges error 0x00000006
  • Adjustment program for epson communication error
  • Adjustment program error code 21000069
  • Adjustment program error code 20000101
  • Adjustment program error code 200000101

    • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии