Jump to content

All you need to know about BE Filters but were too lazy to Google

Recommended Posts

This is not my Guide!


All credits goes to ebay over at opendayz.net and his original post: http://opendayz.net/threads/a-guide-to-battleye-filters.21066/


This is reposted here in part only – you need to check out the original post for the full guide.  

I have chosen to post this in this way for a few reasons:

·         I am tired of people just posting “BE Files?” when they encounter Restriction kicks from putting in random scripts in their mission files.

·         I want to make sure that people learn how to do it and work on learning some basic skills in how to manage their own server – adjusting their filters when they put more stuff into the server seems to be lacking so far…


A simple google search provides all the information you will ever need on the topic of BE filters.  (http://bit.ly/1DgDAAE) (http://lmgtfy.com/?q=Editing+BattleEye+filters+for+Arma+3)

So without further details let me present:


Ebay’s: A Guide to BattlEye Filters

I noticed a severe lack of information on BattlEye across Arma and DayZ modding communities. This guide will give an overview of BE filters, BEServer.cfg and automatic banning with BE.

What they are:
BE filters are an optional feature of BattlEye Anti-Cheat for Arma games. They provide some additional protection that is customizable by mod makers and server admins. Currently Bastian ($able) is the sole developer of BE for Arma. However, other Bohemia devs like Dwarden contribute ideas for him to implement. Dwarden also made the original filters for DayZ mod a few years ago.

Mod developers usually provide filters with their server files. Below are links to current filters for popular DayZ mods:

Infistar also maintains filters for compatibility with his antihack here. Place the .txt files in your dedicated server config directory\BattlEye\ folder. If you are using a managed host this will usually be accessible through FTP.

How they work:
BE searches all scripts running on the client (scripts.txt) and specific command parameters (other filters) for the keywords provided in the filter .txt files. If a match is found it can take one of the following actions:

1 = Log to .log file only
2 = Log to console only
= Log to both
4 = Kick with no log
5 = Kick and log to .log file only
6 = Kick and log to console only
7 = Kick and log to both

Console refers to the window which opens when running the Arma server.exe. The console always shows all connects, disconnects and kicks. Its output is saved in a .txt file in the config directory if logFile option is set in server.cfg. It is also visible when connected over Rcon.

Logging to .log is recommended because it creates separate .log files in the \BattlEye\ folder for each restriction type. This makes it much easier to review than one large console log file with all types mixed together.

Logging to console is only useful if a live stream of BE logs is needed over Rcon. Beware it increases server resource usage, especially when streaming frequently written to logs. It also tends to flood Rcon and make connect, disconnect and kick messages difficult to read. For this reason logging to console is not advised unless your filters are configured to log very little. It should also be noted logging to both console and .log with logFile set in server.cfg is writing the same data to disk in two different files.

Adding keywords:
On a new line add the number followed by a single space and a keyword:
5 keyword

If a keyword contains spaces it must be enclosed in double quotes:
5 "key word"

If a keyword contains double quotes " they must be preceded by a \ like so:
5 "key \"word\""

If a keyword contains regex metacharacters ({}[]()^$.|*+? and \) they must also be preceded by a \ like so:
5 "key \(word\)"

Note: The one exception to this rule is scripts.txt. Currently it is the only filter that does not support regex. It will be added later according to Bastian. This means the only characters that need to be preceded with a \ in scripts.txt are double quotes " for now.

Use keywords that catch multiple strings when possible. For example, say in createVehicle.txt you want to kick for spawning humvees. Instead of adding a keyword for each class name like this:
5 HMMWV_Ambulance_DES_EP1

It is more efficient to use a single keyword that covers all humvees:

To catch everything use empty double quotes for the keyword "" or leave it blank:
5 ""

Adding exceptions (fixing unwanted kicks):
On the same line add a single space after the keyword. Then add either != or ! with the exception:
5 keyword !keywordException

Exceptions follow the same rules as keywords. If an exception contains spaces it must be enclosed in double quotes:
5 keyword !"keyword exception"

If an exception contains double quotes " they must be preceded by a \ like so:
5 "key word" !"key word \"exception\""

If an exception contains regex metacharacters ({}[]()^$.|*+? and \) they must also be preceded by a \ like so:
5 keyword !"keyword \(exception\)"

Note: Again this regex rule does not apply to scripts.txt.

The two options for exceptions are:

  • != The parameter must exactly match the exception. In scripts.txt the entire statement the keyword is found in must exactly match the exception.
  • ! The parameter must contain the exception. In scripts.txt the statement the keyword is found in must contain the exception.

For example, if this is our createvehicle.txt filter:
5 "HMMWV_" !"HMMWV_Ambulance"

The code example below will not kick because the type parameter contains HMMWV_Ambulance which is an exception:
createVehicle ["HMMWV_Ambulance_DES_EP1",getPosATL player,[],10,"NONE"];

The code example below will kick because the parameter does not contain HMMWV_Ambulance:
createVehicle ["HMMWV_DES_EP1",getPosATL player,[],10,"NONE];

If we change our filter to use != like so:
5 "HMMWV_" !="HMMWV_Ambulance"

Now both of the above code examples will kick because the parameters are not exact matches to HMMWV_Ambulance. The below code example will not kick because it is an exact match:
createVehicle ["HMMWV_Ambulance",getPosATL player,[],10,"NONE"];

Exceptions work differently in scripts.txt as noted above. For example, if this is our filter in scripts.txt:
5 keyword !=keywordException

The code example below will kick because the exception is not an exact match to the statement:
systemChat "keywordException";

To fix we need to change the filter to include the entire statement as an exception:
5 keyword !="systemChat \"keywordException\";"

Now the above code example will not kick.

statements should be one line by convention in SQF, but they can span multiple lines. For example the statement below will work without error, but spans four lines:

Code (Text):

if (2 > 1) then
    systemChat "keywordException"

Because there is no semicolon ; on the end of the systemChat line, the above code will still kick. To avoid this the script should be written so the systemChat line ends with a semicolon.

Alternatively, the filter could be changed to use ! instead of != so the statement the keyword is found in must onlycontain the exception:
5 keyword !keywordException
Now both of the above code examples will not kick.

In general exceptions should be written with != when ever possible. Using ! allows much more through the filter. There are some exceptions to this, such as the 
createvehicle.txt HMMWV_Ambulance example above. In that case it is more efficient to use a single ! exception to allow multiple class names, rather than multiple != exceptions. Many more fancy things can be done in filters that support regex. To learn more about regex check this out.

Note: BE filters are not case sensitive, but they are sensitive to spaces and line breaks.

Below is a walk through of each filter file in this format:


  • [Filters] Which command(s) parameter(s) are searched for keywords
  • [Kick] Suggested keywords to kick and log (5)
  • [Log] Optional keywords to log (1). Opting to log extra keywords may provide more information for identifying cheaters and monitoring server activity. The trade off is larger logs to review, extra resource usage from searching for more keywords and more writes to disk.
  • [Logs] Additional info the log file shows
  • [Abuse] How the command(s) can be abused by cheaters (if no other prevention is in place)


Share this post

Link to post
Share on other sites

I just skimmed the post real quick so maybe I missed it but it's missing a key piece of information. 


How to figure out what line to edit


In the BE filters, the first line is line 0. Any lines that are commented out with // are not included.




Here is the line in my scripts.log:

07.12.2014 01:18:30: BetterDeadThanZed (IP DELETED) GUID DELETED - #20 "[] execVM "custom\messages\welcome.sqf";

In the scripts.txt file, I go to the 21st line, which is line 20 (Because the first line is line 0). This is the line before making any changes:

7 exec !="<execute expression=" !"RscDebugConsole_execute" !"execFSM" !"_executeStackedEventHandler" !"fn_execVM" !"fn_moduleExecute" !"fn_execRemote" !"fn_MPexec" !"bis_fnc_moduleExecute_activate" !"fn_tridentExecute" !"randomize_civ1" !"executed from" !"EPOCH_DebugGUI_exec" !"_handle = [_display] execVM _script;" !"execVM \"\A3\Structures_F\scripts" !="execVM \"\A3\Structures_F_EPC\Civ\PlayGround\scripts\Carousel_spin.sqf\""

Here's the modified line. Note the addition at the end of the line:

7 exec !="<execute expression=" !"RscDebugConsole_execute" !"execFSM" !"_executeStackedEventHandler" !"fn_execVM" !"fn_moduleExecute" !"fn_execRemote" !"fn_MPexec" !"bis_fnc_moduleExecute_activate" !"fn_tridentExecute" !"randomize_civ1" !"executed from" !"EPOCH_DebugGUI_exec" !"_handle = [_display] execVM _script;" !"execVM \"\A3\Structures_F\scripts" !="execVM \"\A3\Structures_F_EPC\Civ\PlayGround\scripts\Carousel_spin.sqf\"" !=execVM "custom\welcome\welcome.sqf";"

Share this post

Link to post
Share on other sites

ok I could use abit more schooling on BE filters mostly script restrictions...


I have overcome most filters with the !=""

but script restrictions are abit different...

I really need to learn this as I am always adding scripts to my servers but I have never had script restrictions on arma 2


I am getting this error..


kicked for the last one now #20

22.12.2014 15:38:52: Calamity ( d77eed01d160424505535d1938b21bf3 - #20 " 1];

09.12.2014 14:38:02: Calamity ( d77eed01d160424505535d1938b21bf3 - #15 "setPos _junkPosition;
_junk enableSimulation false;
_junk allowDamage false;

_fakeName = call CREATE_RANDOM_IED_NAME;
09.12.2014 14:46:14: Calamity ( d77eed01d160424505535d1938b21bf3 - #13 "xit", [13], "", -3, [["expression", ""]], "1", "1"]
showCommandingMenu "#USER:cloakmenu";"
09.12.2014 15:34:33: Calamity ( d77eed01d160424505535d1938b21bf3 - #21 "CargoGlobal ["arifle_MXM_RCO_pointer_snds_F", 2];
_box1 addMagazineCargoGlobal ["30Rnd_65x39_caseless_mag_Tracer", 4];
_box1 add"
09.12.2014 16:04:20: Calamity ( d77eed01d160424505535d1938b21bf3 - #3 ";

if ((getPosASL player) select 2 > 0) then

player attachTo [_remorqueur, [
(boundingBox _remorqueur select 1 select 0)"
09.12.2014 16:08:28: Calamity ( d77eed01d160424505535d1938b21bf3 - #47 "WrflDnon_medic") then
player switchMove "";
player removeAllEventHandlers "AnimDone";

if ((getPosASL player) select 2 "
09.12.2014 17:08:04: Calamity ( d77eed01d160424505535d1938b21bf3 - #3 ""R3F_LOG_est_transporte_par", _heliporteur, true];

_objet attachTo [_heliporteur, [
(boundingBox _heliporteur select 0 s"
22.12.2014 06:24:35: Calamity ( d77eed01d160424505535d1938b21bf3 - #4 " 0, "", "", _Unit]; 
_source setDropInterval 0.1;  
_source attachto [_Unit,[0,0,0]]; 

sleep 1; 

_Unit hideObjectGlobal true; "
22.12.2014 10:00:43: Calamity ( d77eed01d160424505535d1938b21bf3 - #14 "it", [13], "", -3, [["expression", ""]], "1", "1"]

showCommandingMenu "#USER:adminmenu";"
22.12.2014 10:16:40: Calamity ( d77eed01d160424505535d1938b21bf3 - #35 "elect 0;
if ("ItemGoldBar10oz" in magazines player) then{
createDialog "RecruitUnitsDialog";
} else {
SystemChat "You need one 1"
22.12.2014 15:38:52: Calamity ( d77eed01d160424505535d1938b21bf3 - #20 " 1];
_box1 addWeaponCargoGlobal ["Rollins_F", 1];
_box1 addMagazineCargoGlobal ["16Rnd_9x21_Mag", 4];
_box1 addMagazineCargoGlob"

Share this post

Link to post
Share on other sites

German Translation

Were too lazy to Google AND too learn englisch ^^



Das ist nicht meine Anleitung!


Jeglicher Dank geht an ebay von opendayz.net und seinem original Post: http://opendayz.net/threads/a-guide-to-battleye-filters.21066/


Der original Post wird hier nur teilweise wiedergegeben. Um eine komplette Übersicht zu bekommen, lest den original Post.

Ich habe mich aus diversen Gründen dazu entschlossen, das Thema hier auf diese Weise nochmal wiederzugeben:

·         Ich kann die vielen Threads nicht mehr sehen, wenn Leute irgendein Script auf ihren Server machen und dann nach Hilfe     

           schreien, wenn sie einen BattlEye-Kick bekommen

·         Ich möchte sicherstellen, das die Leute lernen, wie sie ihren Server selbst administrieren und nicht immer wieder Hilfe von

          anderen benötigen– so wie es aussieht, ist das selbständige Nachjustieren der BE-Filter nur bedingt bekannt

Eine einfache Google-Suche stellt alles erforderliche Wissen zum Thema BE-Filter bereit.  (http://bit.ly/1DgDAAE) (http://lmgtfy.com/?q...ters for Arma 3)

Lange Rede, kurzer Sinn....

Also präsentiere ich euch hiermit:


Ebay’s: Anleitung zu BattlEye Filter

Ich habe ein großes Fehlwissen in Bezug auf BE-Filter in der ganzen Epoch und DayZ-Community festgestellt. Diese Anleitung soll einen Überblick über die Möglichkeiten der BE-Filter-Konfiguration geben.

Was sind diese BE-Filter:
BE Filter sind sozusagen ein Anti-Cheat-Tool für alle Arma Spiele. Sie bieten einen gewissen Schutz, der es jedoch Server-Admins und Mod-Entwickler erlaubt, diesen Schutz anzupassen. Im Moment ist Bastian ($able) der Einzige Herrausgeber von BE für Arma. Wie auch immer, Bohemia Enwickler wie zb.  Dwarden haben einige Ideen dazu beigetragen. Dwarden war auch derjenige, der die originalen DayZ-Filter gestaltet hat vor ein paar Jahren.

Mod-Entwickler stellen in der Regel Filter bereit, die für ihren Mod angepasst wurden. Hier ein paar Links zu den bekanntesten DayZ-Mods:

Infistar stellt ausserdem regelmässig aktuelle Filter bereit, die auf sein Antihack abgestimmt sind http://infistar.de/xtra.html. Die .txt Dateien gehören in den passenden Ordner: server config directory\BattlEye\ . Wer einen Root betreibt, sollte wissen wie und wo die Dateien eingefügt werden, wer einen Server gemietet hat, sollte dies via FTP machen können. Weitere Infos dazu erfragt bei eurem Server-Hoster.

Wie arbeiten die Filter:
BE durchsucht/scannt alle Scripte, die über den  client (scripts.txt) laufen und diversen command Parameter (other filters) nach Schlüsselwörtern, die in den Filter .txt Dateien aufgeführt sind. Wird dabei ein Treffer gelandet, passiert eines der folgenden Dinge, je nachdem, welche Zahlen in der entsprechenden Zeile am Anfang steht:

1 = Nur ein Log/Eintrag in der .log
2 = Nur ein Log/Eintrag in der Konsole
= Nur ein Log/Eintrag in beide
4 = Kick ohne Log/Eintrag
5 = Kick und Log in der  .log Datei
6 = Kick und Log in der Konsole
7 = Kick und Log in beide

Konsole bezieht sich auf das Fenster, das sich öffnet wenn ihr die arma.exe startet. Die Konsole zeigt immer alle Connects, Disconnects und Kick s an. Gespeichert wird das ganze in einer .txt Datei im Config-Ordner, vorrausgesetzt die Option logFile ist in der  server.cfg aktiviert. Ist man über Rcon angemeldet, sieht man diese Meldungen ebenfalls.

Der Eintrag in die .log ist empfehlenswert, weil unterschiedliche .log Dateien im \BattlEye\ Ordner für jede Einschränkung erstellt wird. Das macht das Nachvollziehen eines Eintrages leichter, da mehrere kleinere Dateien erstellt werden. Somit kann man gezielter suchen und muss nicht die riesige Log-Datei der Konsole durchsuchen.

Ein Log in die Konsole ist nur dann sinnvoll, wenn ein live stream von BE logs über Rcon gebraucht wird. Dies kann aber sehr schnell zu Performence-einbussen führen. Ausserdem überflutet damit Rcon und macht das Auslesen von z.b. Connect und Disconnect Einträge sehr schwer. Aus diesen Gründen ist ein Log in der Konsole nur dann empfehlenswert, wenn die Filter so eingestellt sind, das sie recht wenig Logs eintragen. Es sollte auch bedacht werden, Log-Einträge in der Konsole UND den .log Dateien verbraucht den doppelten Speicherplatz für die selben Informationen, eben nur an zwei verschiedenen Orten.

Zufügen von Schlüsselwörtern:
Bei einer neuen Zeile beginnt mit der gewünschten Option (Zahl), danach ein Leerzeichen und das Schlüsselwort:
5 Schlüsselwort

Enthält das Schlüsselwort ein oder mehrere Leerzeichen, muss es in Anführungszeichen gesetzt werden:
5 "Schlüssel Wort"

Wenn ein Schlüsselwort selbst Anführungszeichen enthält, muss vor jedem Anführungszeichen ein Schrägstrich gesetzt werden :
5 "Schlüssel \"Wort\""

Gleiches gilt für andere Sondersymbole wie ({}[]()^$.|*+?\) :
5 "Schlüssel \(Wort\)"

Beachte: Die einzige Ausnahme bildet hier die scripts.txt. Im Moment ist dies die einzige Datei, in der nur Anführungszeichen einen vorhergehenden \ brauchen.

Benutze wenn möglich immer Schlüsselwörter, die mehrere Sachen abdecken können. Beispiel: Du möchtest einen Kick für das Spawnen von HUMVEES einfügen in der createVehicle.txt Bevor du nun für jedes einzelne Modell einen Eintrag machst,..... also so z.B.:
5 HMMWV_Ambulance_DES_EP1

...ist es effizienter den Eintrag so zu wählen, das alle HUMVEES betroffen sind, nämlich so:

Um alles zu blocken, einfach nur 2 "" eintragen oder leer lassen:
5 ""

Ausnahmen hinzufügen (ungewollte Kicks verhindern):
In der selben Linie ein Leerzeichen hinter dem Schlüsselwort machen und die Ausnahme mit einem != oder ! vorne dran eintragen:
5 Schlüsselwort !SchlüsselwortAusnahme

Ausnahmen folgen den selben Regeln wie Schlüsselwörter, enthalten sie Leerzeichen, müssen sie in "" gesetzt werden:
5 Schlüsselwort !"Schlüsselwort Ausnahme"

Und auch die \ vor Sonderzeichen wie ({}[]()^$.|*+?" und \):
5 Schlüsselwort !"Schlüsselwort \"Ausnahme\""

Beachte: Auch diese Regel gilt nicht in der scripts.txt.

Es gibt folgende 2 Optionen um Ausnahmen hinzu zufügen:

  • != Der Parameter muss exakt zur Ausnahme passen. In der scripts.txt muss das komplette Schlüsselwort (zb mit Sonderzeichen) exakt zur Ausnahme passen.
  • ! Der Parameter passt zur Ausnahme. In der scripts.txt muss das Schlüsselwort zur Ausnahme passen.

Z.B., wenn du das in deinem createvehicle.txt Filter stehen hast:
5 "HMMWV_" !"HMMWV_Ambulance"

Das nachfolgende Beispiel führt NICHT zum Kick weil das Beispiel die Ausnahme HMMWV_Ambulance im Namen trägt:
createVehicle ["HMMWV_Ambulance_DES_EP1",getPosATL player,[],10,"NONE"];

Dieses Beispiel führt zum Kick, weil HMMWV_DES nicht zu HMMWV_Ambulance passt:
createVehicle ["HMMWV_DES_EP1",getPosATL player,[],10,"NONE];

Wenn wir den Filter abändern und ein != einsetzen:
5 "HMMWV_" !="HMMWV_Ambulance"

Nun wird für beide oben genannte Beispiele gekickt, weil die exakte Schreibweise gefordert wird.


Der nachfolgende Code allerdings wird NICHT gekickt, weil er den exakten Wortlaut beinhaltet:
createVehicle ["HMMWV_Ambulance",getPosATL player,[],10,"NONE"];


In der scripts.txt werden Ausnahmen noch etwas schärfer behandelt. Steht das zb darin:
5 keyword !=keywordException

Wird der nachfolgende Code zum Kick führen, obwohl das Schlüsselwort eigentlich passt:
systemChat "keywordException";

Allerdings sind hier noch die " dabei und das umgehen wir dann so:
5 keyword !="systemChat \"keywordException\";"

Nun bekommt man keinen Kick mehr für den Code.

Angaben sollten in einer SQF eigentlich immer in EINER Zeile stehen, aber sie können sich auch über mehrere Zeilen ziehen. Z.B. die folgende Angabe funktioniert ohne Fehler, aber zieht sich über 4 Zeilen:

Code (Text):

if (2 > 1) then
    systemChat "keywordException"

Weil da kein Semicolon ; am Ende der Zeile systemChat ist, führt der Code immernoch zum Kick. Um das zu verhindern sollte der Code so geschrieben werden, das die Zeile mit systemChat ein Semikolon am Ende hat.

Alternativ kann man im Filter ein ! setzen anstelle von != Damit wiederum muss ja nur ein Teil der Ausnahme zutreffen...:
5 keyword !keywordException

Nun führen beide oben genannte Codes nicht mehr zum Kick.
Generell sollten Ausnahmen immer mit != eingetragen werden, sofern dies möglich ist. Ein ! allein erlaubt schon fast zuviel und könnte somit den Missbrauch begünstigen. Natürlich ist es etwas anderes, wenn es wie in dem Beispiel mit dem HMMWV in der
createvehicle.txt HMMWV_Ambulance oben Sinn macht. In diesem Beispiel waren wir mit einem ! effektiver um eben mehrere Classnames abzudecken. Es können noch viel mehr tolle Sachen mit Filtern erreicht werden, das würde aber hier zuweit ins Detail gehen. Um mehr darüber zu erfahren check this out.

Beachte: BE Filter beachten keine Groß/Kleinschreibung, aber Leerzeichen und Zeilenumbrüche.


Welche Zeile muss bearbeitet werden?


Das hier genannte Beispiel kann auf alle anderen Kicks angewendet werden. Man muss eben in den entsprechenden .log Dateien nachsehen und die passende Zeile herrausfinden (zb, #0 oder #42 usw)

In den BE Filtern ist die erste Zeile die Zeile 0 (#0). Alle Zeilen die mit // ausgeklammert sind, werden NICHT mitgezählt.

Also ist bei der Angabe #0 eigentlich Zeile 1 gemeint.

Demnach wäre #42 die Zeile 43 und so weiter




Hier eine Zeile aus der scripts.log:

07.12.2014 01:18:30: BetterDeadThanZed (IP DELETED) GUID DELETED - #20 "[] execVM "custom\messages\welcome.sqf";

Der Grund für den Kick ist also "[] execVM "custom\messages\welcome.sqf";


In der scripts.txt Datei gehen wir nun zur Zeile 21. So sieht die Zeile vor der Änderung aus:

7 exec !="<execute expression=" !"RscDebugConsole_execute" !"execFSM" !"_executeStackedEventHandler" !"fn_execVM" !"fn_moduleExecute" !"fn_execRemote" !"fn_MPexec" !"bis_fnc_moduleExecute_activate" !"fn_tridentExecute" !"randomize_civ1" !"executed from" !"EPOCH_DebugGUI_exec" !"_handle = [_display] execVM _script;" !"execVM \"\A3\Structures_F\scripts" !="execVM \"\A3\Structures_F_EPC\Civ\PlayGround\scripts\Carousel_spin.sqf\""

Hier ist die modifizierte Zeile, mit der Änderung am Ende:

7 exec !="<execute expression=" !"RscDebugConsole_execute" !"execFSM" !"_executeStackedEventHandler" !"fn_execVM" !"fn_moduleExecute" !"fn_execRemote" !"fn_MPexec" !"bis_fnc_moduleExecute_activate" !"fn_tridentExecute" !"randomize_civ1" !"executed from" !"EPOCH_DebugGUI_exec" !"_handle = [_display] execVM _script;" !"execVM \"\A3\Structures_F\scripts" !="execVM \"\A3\Structures_F_EPC\Civ\PlayGround\scripts\Carousel_spin.sqf\"" !=execVM "custom\welcome\welcome.sqf";"

Share this post

Link to post
Share on other sites



Hallo zusammen,


ich versuche mich aktuell mit den BE-Filtern zu befassen. Problem: Oftmals sind die Fehlermeldungen aus der Log-File nicht so kurz. Daher habe ich Probleme, die Ausnahme vernünftig zu definieren.

Ich weiß also nicht, wie ich diese raus schreiben soll!


Hier mal ein aktuelles Problem mit dem Earplugscript:


Ich werde aus folgendem Grund gekickt:



20.04.2015 16:30:11: Headi (IP Removed) GUID Removed - #53 "EP_LOOP;};

[] spawn {cmKeyPress = (findDisplay 46) displayAddEventHandler ["KeyDown","if ((_this select 1) == cmEarplugs_hotke"


Das Problem hier sind die vielen Zeichen, dazu kommt noch ne Lehrzeile, und dann geht es erst weiter.


Wie müsste ich dieses Problem dann lösen? 


Müsste ich dann so rausschreiben?




"EP_LOOP;}; [] spawn {cmKeyPress = (findDisplay 46) displayAddEventHandler ["KeyDown","if ((_this select 1) == cmEarplugs_hotke"


Über eine Erklärung dazu wäre ich Dankbar!


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.

Reply to this topic...

×   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.


  • Similar Content

    • By Birgitte
      OK, I'm giving up the ghost on I created a new 1.0.6 server using a hosting service because they do not have the newest version yet. I need to know the quickest and easiest way to upgrade to keeping in mind that I do not need to save any data from the old database. I wiped the tables and imported epoch.sql. What files do I need to change/remove/delete in order to upgrade?
    • By Pegasus177
      Hey guys!
      So i have been playing this game for quite a while now and everyday i come across people having client side issue when connecting to their favorite servers or just to the game in general.
      So much so that i have been taken on as a Tech Support of sorts for a few servers.
      Nothing is more annoying than when you are having connection problems to a server and all the guides say the same thing... Uninstall Arma.. re install Arma.
      Well i have never had to uninstall or re install the game and i usually have found fixes that avoid a requirement for this.
      so i have decided to post a guide to some of the common faults i see and a list of my fixes here.
      ** i Have actually found a pretty good guide which more or less outlines many of the fixes i was planning to put in this post. I have a few more that require a little less effort and can get you back playing quicker so i shall use excerpts of the guide and furnish it with my own solutions too**
      Here is a list of some of the more common errors i see. (before you go through this list please PLEASE check that all of your settings/ perameters/ install folder path files are correct and that you have the required mods for the server you are planning to play on. If you are attempting to join CCG servers i would recommend getting their own personal launcher from their website as the mod versions they run differ from those you can download on launchers such as DayZ Commander. You wouldn't believe how often it turns out the client side user has a error in their mod string or has missed a setting.)
      1. ERROR: "Bad Serial Number Given on Setup" or "Invalid or Missing Serial Number" 2. ERROR: "Connection Failed" or "Bad version, server rejected connection" 3. PROBLEM: v1.62 instead of v1.62.xxxxxx 4. ERROR: "BattleEye initialization failed." (see also for battleye update failure) 5. ERROR: "No entry 'bin\config.bin/CfgInGameUI/MPTable.shadown'." 6. ERROR: "Error compiling pixel shader PSSpecularAlpha:0" 7. ERROR: "Addon 'dayz_anim' requires addon 'CA_Dubbing_Counterattack'" 8. PROBLEM: Black screen and/or Crash to desktop on start-up 9. PROBLEM: Spawn as a crow/bird. 10. PROBLEM: No servers showing up in the server browser. 11. PROBLEM: Really low FPS. (i7-processor) 12. PROBLEM: Missing Czech Republic DLC 13. ERROR: "Instruction at X referenced memory at 0x000000XX. The memory could not be read." 16. ERROR: "No Entry 'bin\config.bin/CfgMagazines.ItemNails'." 17.ERROR. Failed to load file "pmc|addons|air_pmc.pbo" - decryption of headers failed" ( likewise this one can also say baf in place of pmc. This is just an extension on missing Czech republic DLC error       ERROR: "Bad Serial Number Given on Setup" or "Invalid or Missing Serial Number"   SOLUTION 1: Close Steam, then run as administrator. Run ARMA 2. Run ARMA 2: Operation Arrowhead.   SOLUTION 2: Delete a file called "localconfig.vdf" in .\Steam\userdata\#\config The # is a series of digits that varies depending on your account. (If you've had multiple accounts active through your computer.) Restart Steam and run it as administrator.   SOLUTION 3:  ( I hate suggesting this and always recommend it as a last resort but sometimes it is required) 1. Uninstall A2/A2:OA entirely. (Including the folders in registry.) 2. Close Steam. 3. Run Steam as administrator and reinstall the games.   WHY: (solution 1) Steam writes your serial numbers into your registry , but cannot do it if it doesn't have the rights to edit registry. Running both games means that Steam will re-write both serial numbers for both games. That way DayZ will work the next time you try to play it.           ERROR: "Connection Failed" or "Bad version, server rejected connection"   SOLUTION 1: Sort servers by "Mission" and look for missions labeled as "DAYZ" (Note the all caps.) These are the only servers you can join with just the Steam version. It only gives access to DayZ Vanilla.   SOLUTION 2: Download DayZ Commander[www.dayzcommander.com] or DayZ Launcher[www.dayzlauncher.com] to keep DayZ, ARMA 2, and all unofficial maps and community-variants of the mod up-to-date. This is the BEST THING you can do if you want the most out of DayZ. (while DayZ Commander is a much more sturdy and well laid out mod launcher it does require you to manually insert the mod string (launch perameters) These generally take the form of "-mod=[the mods the server is running] most servers will display their required mod string in the server name and info or on the server website       PROBLEM: v1.62 instead of v1.62.xxxxxx (This issue is rarely seen since the move over to Steam from Gamespy but some players still use the Beta version to launch)   SOLUTION 1: Download and run ARMA 2: Operation Arrowhead Beta, and launch DayZ with the beta patch.   SOLUTION 2: Download DayZ Commander[www.dayzcommander.com] for easier handling of everything you need for DayZ.   SOLUTION 2: Download a beta patch manually from here: http://www.arma2.com/beta-patch.php   WHY: You are missing a Beta Patch. DayZ Commander is the best solution for getting one, because you can easily pick and choose which build to use.       ERROR: "BattleEye initialization failed."   SOLUTION 1. Open your Steam library and right ciick on Arma 2 Operation Arrowhead. Click on Properties and then the LOCAL FILES tab. Click on Browse local files. In the window that pops up scroll down and find the 3 applications                                              ARMA2OA exe                                              ARMA2OA_BE exe and just a little further down arma2oaserver exe   Delete these 3 applications. now close the window and go to your LOCAL FILES tab again. At the end click "Verify integrity of game cache". Let it complete. It will take about 2 to 5 minutes. When it is complete launch Arma 2 Operation arrowhead from Steam and let it reach the main menu. When it does shut down the game and go back to your launcher. Now join your chosen server.   SOLUTION 2. Similar to the first solution.. go the Steam Library, properties, LOCAL FILES, browse local files... this time when the window pops up open the folder named Expansion. Then open the folder named Battleye. Launch the application UninstallBE. Now on the LOCAL FILES tab verify integrity of game cache. Let it complete and then Launch the game to main menu once. it should re install Battleye. Now join your server of choice.     SOLUTION 3: Manually download and re install BattlEye. You can download BattlEye from here: http://www.battleye.com/download.html   WHY: ARMA 2 does its best to try and connect to BattlEye's update server, but sometimes there's a problem either on your end(most likely) or their end. When this happens, it's simply better to just download it yourself.   [battleye update Failed]  (there are two methods by which Battleye updates itself. One is when you are at the multiplayer setup menu of the server. In the lower left corner red writing will tell you 'Battleye has initialized' however you should watch this writing as sometimes it says Battleye is updating. This requires you to wait for it to complete before clicking OK. The issue many have is they click "OK" and dont notice that BE is updating and so it causes the update to fail .The other method and more recent form of Battleye update is a black cmd window opens when the client launches the game. Some mistake this as the game launching twice and close the second window again causing the update to fail   **ALL OF THE SOLUTIONS FOR BATTLEYE INITIALIZATION FAILED WILL WORK FOR THIS TOO.**       ERROR: "No entry 'bin\config.bin/CfgInGameUI/MPTable.shadown'."   SOLUTION 1(unsure): Update your DirectX driver. Make sure you have the latest version of DirectX .   SOLUTION 2(untested): 1. Go to .\Steam\steamapps\common\arma 2 operation arrowhead\ 2. Run the "_runA2CO.cmd" or "_runA2CO_beta.cmd" to launch the game.   SOLUTION 3: 1. Go to .\Steam\steamapps\common\arma 2 operation arrowhead\ 2. Delete the @DayZ -folder. 3. Verify integrity of game cache. 4. Run ARMA 2: Operation Arrowhead 5. Close ARMA2OA and try running DayZ again. (After re-download.)   SOLUTION 4: (I always suggest this as a last resort and rarely tell anyone to uninstall and re install but sometimes there are exceptions) 1. Uninstall ARMA 2: Operation Arrowhead through Steam. 2. Close Steam and run it as administrator.  3. Reinstall ARMA 2: Operation Arrowhead.  4. VERIFY INTEGRITY OF GAME CACHE FIRST. 5. Run ARMA 2: Operation Arrowhead.  6. Close ARMA2OA and try running DayZ again.   WHY: ---  
          ERROR: "Error compiling pixel shader PSSpecularAlpha:0" (This one is rarely seen these days however it is seen)   SOLUTION 1: Update your DirectX driver. Make sure you have the latest version of DirectX .   SOLUTION 2: Close Steam and run it as administrator.   WHY: ---  
      ERROR: "Addon 'dayz_anim' requires addon 'CA_Dubbing_Counterattack'"   SOLUTION: 1. Go to .\Steam\steamapps\common\arma 2\ 2. Copy the content of the 'addons' folder. 3. Go to .\Steam\steamapps\common\arma 2 operation arrowhead\Common\ 4. Paste and replace/merge the files. (5. Additionally, copy the entire Addons folder into A2OA's main folder.)   WHY: The required animations are in the ARMA 2 addon folder. Copying them over to ARMA 2: Operation Arrowhead will also add them to where DayZ can find them. Not everybody are required to do this. (Assuming they don't have the error.)         PROBLEM: Black screen and/or Crash to desktop on start-up   SOLUTION: 1. Go to C:\Users\...\Documents\ArmA 2\ (Path may vary depending on which version of Windows you are running. Look for your "My documents" or "Users and Documents" if you're running older versions of Windows like Windows XP or Vista.) 2. Open the arma2oa.cfg in notepad, notepad++, or other simple text editor. 3. Find these lines: Resolution_W=1920; (The value after '=' might be different.) Resolution_H=1200; (The value after '=' might be different.) 4. Change the _W value to your screen WIDTH 5. Change the _H value to your screen HEIGHT and save. 6. Run the game again.   SOLUTION: 2. Go to C:\Users\...\Documents\ArmA 2\ 2. Open ArmA2OA.cfg with notepad, notepad++ or similar. 3. Find "Windowed=0;" and change the 0 to 1. 4. Save the file. 5. Start the game, (re)set your graphic settings. (optional) 6. Close the game and change the 1 back to 0 and save. Note that if you can't find the part that says "Windowed", type it to the end of the list yourself. DON'T FORGET the ; at the end. You will get a new error if you don't place it there.   WHY: Because most likely your monitor/system is having problems trying to open the game with the default resolution. In the first solution you are going into the settings file and manually changing the resolution that the game launches in. Manually changing the game to launch in a window is a more fail-safe method of fixing the issue.           PROBLEM: Spawn as a crow/bird.   SOLUTION 1: Find another server.   SOLUTION 2: Download DayZ Commander to update your version of DayZ (or variation of) to the version the server you're trying to connect to is running on.   WHY: What you're experiencing is the Spectator Mode. It's a normal part of ARMA 2, but is caused by a server-side glitch in DayZ. Most likely because of an incorrect version.         PROBLEM: No servers showing up in the server browser.   SOLUTION 1: Reset your filters, make sure you have no ping limits, either.   SOLUTION 2: Make sure your anti-virus software isn't blocking the game. Either create an exception for the game(HIGHLY recommended.), or disable your firewall. Make sure to turn off your Windows firewall as well, but always turn them back on after you're done playing or when browsing the internet!   SOLUTION 3: Download DayZ Commander, WithSix, or any other third-party server browser. (Those two are recommended, however.)   WHY: Some anti-virus software, like Norton Anti-Virus, is known to block internet access from new software. This prevents your game from pinging servers to add them to your server browser. And for some people, pings tend to spike while the game is looking for servers, hence having a ping limit will hide most if not all servers.           PROBLEM: Really low FPS. (i7-processor)   SOLUTION: Disable Hyperthreading.To do this you need to access your BIOS. Restart your computer and as it begins you will be prompted to press a key to enter the BIOS It is different on every motherboard but some of the more common ones are F8,F10,F11,F12,End key. Again each Bios is different but navigate your way to the processor menu and disable Hyperthreading in the menu then save and restart.   WHY: ARMA 2 does not (properly) support more than 4 cores. Hyperthreading drags the performance even lower.       PROBLEM: Missing Czech Republic DLC   SOLUTION: the problem ist that the combined operations batch file does not contain the ACR extension when launching combined ops. To corrct that, go to "%PATHTOSTEAM%\SteamApps\common\arma 2 operation arrowhead" and edit the "_runA2CO.cmd" file with an editor of your choice. Find the lines that read ":runs "%_STEAMPATH%\steam.exe" -applaunch 33930 "-mod=%_ARMA2PATH%;EXPANSION;ca;ACR"" (near the end of that file) and edit the -mod line as follows:   Original: "%_STEAMPATH%\steam.exe" -applaunch 33930 "-mod=%_ARMA2PATH%;EXPANSION;ca"   New One: "%_STEAMPATH%\steam.exe" -applaunch 33930 "-mod=%_ARMA2PATH%;EXPANSION;ca;ACR"   If you start combined ops now, you'll get the ACR Expansion too.   Note that you'll still have to run Steam as Administrator and start _runA2CO as Administrator, to enable the expansion in general, if you haven't already done so.   WHY: The batch file is missing the ACR from its launch parameters.            ERROR: "Instruction at X referenced memory at 0x000000XX. The memory could not be read."   SOLUTION 1: Go into .\Steam\Steamapps\Common\ARMA 2\DirectX\ and run DXSETUP.exe to install/update DirectX and its components.   SOLUTION 2: Go into .\Steam\Steamapps\Common\ARMA 2\BEsetup\ and run setup_BattlEyeARMA2.exe to install/update BattlEye and its components.   SOLUTION 3: Reboot your computer after completing the two above solutions. (Using DayZ Commander is advised.)   WHY: Because something is either corrupted or not up to date.         ERROR: "No Entry 'bin\config.bin/CfgMagazines.ItemNails'."   SOLUTION 1: Find a server that is running on version 1.8 of the official DayZ mod.   SOLUTION 2: Download DayZ Commander, and use it to download DayZ   WHY: You can ONLY join servers running on the SAME version as you, so if you are trying to join an outdated server while having a different Arma or Mod version installed, you will get stuck in the authentication process and/or receive the file error.         .ERROR. Failed to load file "pmc|addons|air_pmc.pbo" - decryption of headers failed (can also be seen with baf in the place of pmc)   SOLUTION. Go to your Steam Library and right click on Arma 2 British Armed Forces. go to the properties and then navigate tot he LOCAL FILES tab. Click on Verify integrity of game cache. You will be prompted with a window to uninstall BAF. click yes. Now do the same for Arma 2 Private Military Company. When prompted to uninstall again click yes. Now Launch Arma 2 Operation Arrowhead and it will begin to reinstall British Armed Forces and Private Military Company. Allow it to reach the main menu and then shut it down. Now join a server.   WHY Something in the path file of the DLC has caused it to launch incorrectly. More often that not it is launching your mod on the DLC when it should be launching on Arma 2 Operation Arrowhead and reading the DLC separately. To put it simply it failed to recognize what to lunch and what addon to run. for lack of a better explanation the above actions will cause it to kick start again the correct way.   Hope this guide helps many of you. Remember to be patient with it. After all it is a mod of a now old game and when it is trying to run mission files, database, custom scripts and pull DLC and files from everywhere it has a tendency to mess up sometimes.
    • By KiKoZl
      Hello guys so I installed AI- Mission but every time I am kicked by SETDAMAGE # 0 can someone help me know this and 1 problem BE filters but do not think as it fixes   :(
    • By GaspArt
      Hello. Tried to understand system of creating "windows" on GUI, but unsuccesfull..
      Tried to understand this system by reading this topic on wiki, but didnt understand it....


      So could somebody make a guide how to make ur own gui, add "windows" and another thing, will be very-very cool.

      If somebody very clever havent time to make guide, I can pay for private lessons. 

  • Advertisement
  • Supporters
  • Discord

  • Create New...