BattlEye: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
Line 30: Line 30:
* ArmA II  
* ArmA II  
* Operation Arrowhead
* Operation Arrowhead
Now you need to put BEClient.dll to the right location:
* Windows 7
C:\Users\%USERNAME%\AppData\Local\ArmA 2 OA\BattlEye\
* Windows XP
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\ARMA 2 OA\BattlEye\
* STEAM
c:\Program Files (x86)\Steam\SteamApps\common\ARMA 2 Operation Arrowhead\Expansion\BattlEye\


====Automated installer====
====Automated installer====

Revision as of 09:54, 18 December 2010

Introduction

BattlEye website
Abbreviation: BE

BattlEye is an anti-cheat tool created by BattlEye Innovations. It is currently included in Bohemia Interactive's ArmA and ArmA 2 series as an optional installation and server configuration option. It works by scanning connected clients for various cheat an exploit methods and upon detection, disconnecting (kicking) the offending clients. You can find more details about the BE cheat scanning engine on the info page.

Privacy

BattlEye will never violate your privacy in any way. The EULA clearly states this when installing BattlEye. Any other statements found anywhere else are superseded by the EULA.

BattlEye always has and will secure the user's privacy and protect against any sort of software exploitation from outside.

Setup

Latest version

You can find out what the latest version is by visiting the news section.

Installation

Installation of the BattlEye client is an option during the initial game installation process.

BE updates itself automatically during a running MP session with internet access. However in the case of troubles you can:

Manual BE DLL download

a) Download the latest dll from the download section. Make sure to download the dll for the your series of ArmA:

  • ArmA
  • ArmA II
  • Operation Arrowhead

Now you need to put BEClient.dll to the right location:

  • Windows 7
C:\Users\%USERNAME%\AppData\Local\ArmA 2 OA\BattlEye\
  • Windows XP
C:\Documents and Settings\%USERNAME%\Local Settings\Application Data\ARMA 2 OA\BattlEye\
  • STEAM
c:\Program Files (x86)\Steam\SteamApps\common\ARMA 2 Operation Arrowhead\Expansion\BattlEye\

Automated installer

b) Download the new installer: Setup_BattlEyeARMA2OA.exe. Next run it and use "run as Administrator" (select file by left mouse click, right mouse click, select the "run as" option).

Do note that it is a very fast SILENT installer. So normally you do not notice anything - no widows, no progress bar, no completion info. Only if there are issues, it will speak up.

The process of the automated installer:

  1. If BE is same or newer then installer does nothing,
  2. If BE is older it updates BE version,
  3. If BE not found then it will install BE.

You can verify if it was installed by checking the software uninstall list. You find it under "BattlEye for OA uninstall".

Configuration

Client

Apart from installation there is no additional configuration required for game clients.

Server

Refer to the server.cfg section on how to enable BattlEye on a game server.

NOTE: If you run multiple game servers on one machine, you need to specify separate BE paths for each in the server startup parameters.

BE commands

NOTE: The #beserver command has been disabled for now, due to the game admin hijacking hack.
You need to use the BE RCon tool to ban players from your server.

GUID banning

BE can permanently or temporarily ban players from your server. The advantage over ArmA 2's PID banning is that the BE GUID cannot be hacked/changed client-side, therefore the only way for a player to get unbanned is to buy a new game/cd-key.

The following commands are available to manage GUID bans:

loadBans (Re)load the BE ban list from bans.txt.
bans Show a list of all BE server bans.
ban [player #] [time in minutes] [reason] Ban a player's BE GUID from the server. If time is not specified or 0, the ban will be permanent; if reason is not specified the player will be kicked with "Banned".
addBan [GUID] [time in minutes] [reason] Same as "ban", but allows to ban a player that is not currently on the server.
removeBan [ban #] Remove ban (get the ban # from the bans command).

You can either enter them via BE RCon or in-game using "#beserver [command]" (if logged in as admin). For example

#beserver ban 11

Keep in mind that the player # used here is the one listed by BE's "players" command.

BattlEye GUID and IP bans will now both be loaded from and saved to bans.txt (no longer guidbans.txt and ipbans.txt) in your server's BE working directory.

RCon

Latest version: b0.91.

Since BattlEye server version 1.102 you can control your ArmA game server remotely (without having to be in-game) the BattlEye RCon tool.

  1. Download the BattlEye RCon tool (BERCon.exe).
  2. Create a file called BEServer.cfg in BattlEye working directory on the server.
  3. Set your private RCon password in the BEServer.cfg.
  4. Start the RCon tool on your computer.
  5. Connect to your server with its IP, port and RCon password.

Sample BEServer.cfg

RConPassword xyzxyz
MaxPing 200

Support