$able

Let's kick off March with two new features added in BE Server v1.131 and BE Client v1.151: 1. New script detection/logging that is fully customizable by server admins You can now easily set up your BE Server to scan clients for certain strings that are used in script attacks on your server, for example "createVehicle", "serverCommand", "setVehicleInit" or anything else that could potentially be exploited on your server. All you need to do to enable this is create a file called "scripts.txt" in your BE working directory (in the game's application data / profiles / BEpath folder, not the install folder - where bans.txt is placed as well) with per-line entries formatted as follows: [type] [string to search for] The following types exist: 1 - Log detections to "scripts.log" 2 - Log detections to server console 4 - Kick for detections ("Script Restriction #X") When logging detections, the BE Server logs an extract of 100 characters of the script being executed showing the detected string. You can combine types by adding them, so e.g. 3 causes positive detections to be logged both to scripts.log and server console, 5 causes detections to be logged to scripts.log and kicked for at the same time, 7 combines all methods, etc.. See the following random scripts.txt example (please do not use the list below unless You know what's command for/why): 1 createVehicle 1 setVehicleInit 3 serverCommand 4 godmode 3 Bo_Mk82 3 #shutdown 7 disableUserInput true Important update: http://forums.bistudio.com/showthread.php?131759-New-BattlEye-features-for-server-admins&p=2192402&viewfull=1#post2192402 2. Messaging players via RCon RCon admins can now directly send in-game messages to players using the new "say" command: say [player #] [message] If player # is -1, the message is sent to all players. Otherwise the message is sent privately to the specific player. Note that player # is the one shown when entering "players", not the one used by the game itself. Also, keep in mind that only in-game players can be messaged, not those that are still in the lobby. Example: say 11 hey mate, how are you doing today? I hope you like these new features. Feedback of any sort, as always, is welcome. :)

Everyone please read the following: http://steamcommunity.com/app/33930/discussions/0/617328415066127195/. Note that if you are using a cracked copy of Windows you might no longer be able to use BE from now on (this is related to BE's new protection).

This is only a workaround that works for some users. Also, it might break other software on your system. Everyone please read the following: http://steamcommunity.com/app/33930/discussions/0/617328415066127195/.

Could you check if this only happens on BE-enabled servers?

I'm sorry for the confusion, I have just identified an issue with the current BE Service version on Windows XP. It should be fixed by tomorrow.

Your current user account has administrator permissions, right? There is something on your system that prevents BE from loading properly then (error display is not fully implemented in the BE Launcher yet). Did this problem only start recently? Please check your anti-virus or similar software (even if disabled).

On Windows XP please make sure you select the first option in the "Run As" dialog and uncheck "Protect my computer and data from unauthorized program activity": http://i.stack.imgur.com/8aJUu.png.

Could you guys please directly contact support@battleye.com?

The latest version of this overlay should be supported now.

Starting with BE Server v1.178, BE filters are parsed as regular expressions and hence server admins can now implement more complex and flexible search/filter rules. That also means that regex metacharacters ({}[]()^$.|*+? and \) now have to be escaped using '\' if they should be used as literals. See the following examples: 1 "SomeVariable[1|2] = [0-9]+" 5 "if \(whatever\) then \{ player setPos \[0,1,2\]; \};" Note that currently the regex syntax can only be used for the server-side BE filters, support for scripts.txt will be added shortly.

BE Server v1.156 in combination with the latest OA 1.62 beta server now provides new powerful features for server admins. Keep in mind that this is work-in-progress, so these features will be improved and more will be added over time. Special thanks go out to Ondřej Španěl / Suma without whom this wouldn't have been possible. 1.) Log and/or block all vehicle and unit spawns via "createvehicle.txt" By creating this file in your BE working directory and adding rules/filters to it, you can now log and/or block all calls of the "createVehicle" and "createUnit" scripting commands. Logging is done to "createvehicle.log". The filters look exactly the same as in the scripts.txt file, see here for more information: http://forums.bistudio.com/showthread.php?131759-New-BattlEye-features-for-server-admins. Note that each command is automatically blocked if the corresponding filter has kicking enabled (type "4"). See the following examples: 1 "" This simply causes all vehicle/unit spawns to be logged to createvehicle.log. 1 !"WeaponHolder" !"TinCan" !"Rabbit" !"Goat" !"WildBoar" !"Sheep" !"Hen" !"Cow01" !"Cow02" !"Cow03" !"Cow04" !"zZombie_Base" !"z_hunter" !"z_teacher" !"z_suit1" !"z_suit2" !"z_worker1" !"z_worker2" !"z_worker3" !"z_villager1" !"z_villager2" !"z_villager3" !"z_soldier" !"z_soldier_heavy" !"z_policeman" !"z_priest" !"BoltSteelF" !"Land_Fire_DZ" !"SodaCan" !"JackDaniels" !"RoadFlare" !"ChemRed" !"ChemBlue" !"ChemGreen" !"Survivor1_DZ" !"Survivor2_DZ" !"SurvivorW2_DZ" !"Bandit1_DZ" !"CZ_VestPouch_EP1" !"DZ_Patrol_Pack_EP1" !"DZ_CivilBackpack_EP1" !"DZ_ALICE_Pack_EP1" !"SmokeShell" !"SmokeShell" !"SmokeShellRed" !"SmokeShellGreen" 5 "SeaGull" This was created by Dwarden for DayZ. The first line causes everything but the listed vehicle/unit types to be logged to createvehicle.log. The second line causes all "SeaGull" spawns to be logged, blocked and kicked for. A typical createvehicle.log entry looks like this: 12.08.2012 14:20:26: SomePlayer (95.7.111.10:2304) d3dcf429c679f9af82eb9a3b31c4df44 - #0 "MedBox0" 92:4 [-18594,25833,369] #0 is the number of the filter/restriction in createvehicle.txt, usually line number - 1, "MedBox0" is the type of the vehicle/unit being created, 92:4 is the network ID ([client ID]:[object ID]) and [-18594,25833,369] is the spawn position. 2.) Log and/or block all remote code executions via "remoteexec.txt" By creating this file in your BE working directory and adding rules/filters to it, you can now log and/or block all attempts to execute code remotely on the server or other clients (usually done via "setVehicleInit"). Logging is done to "remoteexec.log". The filters look exactly the same as in the scripts.txt file, see here for more information: http://forums.bistudio.com/showthread.php?131759-New-BattlEye-features-for-server-admins. Note that each command is automatically blocked if the corresponding filter has kicking enabled (type "4"). See the following examples: 1 "" This simply causes all remote code executions to be logged to remoteexec.log. 1 !"this enableSimulation false;this allowDammage false;this disableAI 'FSM';this disableAI 'ANIM';this disableAI 'MOVE';" 5 "dayz_serverObjectMonitor set [count dayz_serverObjectMonitor, _object];" 5 _xcompiled 5 loadFile 5 removeAllWeapons 5 removeAllItems 5 disableUserInput 5 serverCommand This was created by Dwarden for DayZ. The first line causes everything but the listed script/code to be logged to remoteexec.log. The other lines cause code containing the listed strings/commands to be logged, blocked and kicked for. I'd like to point out that "5 loadFile" entirely prevents the exploit allowing hackers to steal files from your server. Typical remoteexec.log entries look like this: 12.08.2012 19:13:23: SomeCheater (101.200.55.117:2304) 9d1e49be7ef3b16519bf66c400cc6cdd - #0 "{ if((getPlayerUID _x) == '5230977') then { _x hideObject true; }; } forEach playableUnits;" 12.08.2012 21:18:25: AnotherCheater (77.109.3.18:2304) 29ff7be2045eea48db69e249baf2ffbd - #0 "if (name player == "SomePlayer") then { player setpos mypos;player setVariable["lastPos",0, true];};" 12.08.2012 21:32:37: YetAnotherCheater (210.133.66.11:2304) 65be87266db9e5d78624a4d9c780a878- #0 "if (name player == "SomePlayer") then { removeAllWeapons player;removeAllItems player;[dayz_playerUID,dayz_characterID,"Goat"] spawn player_humanityMorph;player addWeapon "NVGoggles"; };" 3.) Log and/or block all public variable events via "publicvariable.txt" By creating this file in your BE working directory and adding rules/filters to it, you can now log and/or block all public variable events (triggered via "publicVariable" and its variants) that are often exploited to execute code remotely on the server or other clients by overwriting certain game variables/functions/symbols. Logging is done to "publicvariable.log". The filters are applied on the name of the public variable and look exactly the same as in the scripts.txt file, see here for more information: http://forums.bistudio.com/showthread.php?131759-New-BattlEye-features-for-server-admins. Note that each command is automatically blocked if the corresponding filter has kicking enabled (type "4"). See the following example: 1 "" 5 BIS_Effects 5 player_medMorphine The first line causes all public variable events to be logged to publicvariable.log. The other lines cause public variable names containing the listed strings (function names that are typically exploited at the moment) to be logged, blocked and kicked for. Note that you can use the new loadEvents RCon command to (re-)load createvehicle.txt, remoteexec.txt and publicvariable.txt while the server is running. Ok, that's all for now. As a final note, these features cannot be circumvented with a client-side hack. ;)

The latest versions available on the following page should be supported: http://exkode.com/dxtory-downloads-en.html.

Did you read my PM? There was a BE Service update earlier today that should have fixed that, so could you test again with the latest version (restart Steam to force the update)?

A new feature is now available on BattlEye-enabled servers that will provide a great enhancement to server administrators: Since BattlEye Server version 1.102 you can control your server remotely (without having to be in-game) from anywhere on the internet with the new BattlEye RCon tool. All you have to do to enable it is creating a BEServer.cfg file in your BattlEye working directory (in the application data / profiles / BEpath folder, not the install folder) with a line containing "RConPassword [password]" (without [] of course) and (re-)start your ArmA 2 server. That's it. No need to open an additional port in your firewall or anything. You can now easily connect with the BE RCon tool using the server's IP address, its usual game port and the specified RCon password. Note that this can be done by multiple admins at the same time (unlike ArmA 2's in-game admin feature). When logged in, you can enter BE Server commands and ArmA 2 server commands prefixed with #. In addition you will see all BE Server messages (like information about new players) live in the console. To log out, simply type "logout". To quickly close the tool, type "exit". A command to display all available BE Server commands will be added soon. The main commands for now are: "players" (display player list including BE GUIDs and pings), "kick [player#]" (kick a player, his # can be found in the player list), "RConPassword [password]" (change the RCon password), "MaxPing [ping]" (if a player has a higher ping, he will be kicked from the server). More commands will follow over time. BattlEye RCon v0.9 beta can be downloaded here: http://www.battleye.com/downloads/BERCon.exe Keep in mind that this is a beta and changes will still be made. Make sure you always have the most recent version so everything works correctly (especially if there are RCon protocol changes). Feedback, including bug reports, is welcome. :) Newly BIKI page added http://community.bistudio.com/wiki/BattlEye#RCon

First of all, this is totally the wrong topic to post this in (same as your last post). Secondly, did you actually change your shortcut as described in this message? If so please let me know via PM how/when I can check this via TeamViewer. Please contact the BE support address next time you need immediate help. I don't read/find every single post in this forum (especially if posted in unrelated threads) nor do I respond to everything.

Ok, I'm trying to solve this. Do you remember if there was a delay (a few seconds) between this message and "Installing BattlEye Service..." or did it follow immediately? Also, do you know if your friends got the exact same error?

No, a restart is not required. May I ask what exact problem/error you and your friends had?

What does your console window say (if you see one)?

Are you logged into an adminstrator account when starting your game? The installation only succeeds then.

See this: http://forums.bistudio.com/showthread.php?179755-Battleye-refuses-to-start&p=2721948&viewfull=1#post2721948.

Yes, Windows XP is problematic here because it falsely reports that the installation succeeded when it actually didn't. Please select the first option in that dialog and uncheck "Protect my computer and data from unauthorized activity" - only then the BE Service can be successfully installed. I'm sorry for the confusion.

This is a XP-related issue. Please launch "ArmA2OA_BE.exe" in your game directory directly once to properly install the BE Service. No, actually the above is the original name. You must have renamed yours if it's different for you?

Apparently that server is using BE, otherwise you wouldn't get this message. Regarding your other problem, please try again now. A fix for this issue was released earlier today.

Those are all the solutions that are currently known, so I wanted to make sure you tried all of them (this thread is quite cluttered as well). Could you clarify what exact error you get at this point? Note that the original BE installer is not related to the issues being discussed here.

No problem. I have now identified the cause of this issue (it happens when the ArmA2OA.exe is set to run as administrator but ArmA2OA_BE.exe is running as a normal user), so it will be fixed shortly.