BattlEye: Difference between revisions
m (Improved table min width.) |
m (Removed obsolete code) |
||
| Line 41: | Line 41: | ||
| removeBan [ban #] || Remove ban (get the ban # from the bans command). | | 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 | You can either enter them via BE RCon or in-game using "#beserver [command]" (if logged in as admin). For example | ||
Revision as of 15:55, 19 November 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.
Setup
Installation
Installation of the BattlEye client is an option during the initial Game Setup.
Configuration
Client
Apart from installation there is no additional configuration required for game clients running BattlEye.
Server
Refer to the server.cfg section on how to enable BattlEye on a game server.
BE commands
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:
| 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". |
| 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.
- Download the BattlEye RCon tool (BERCon.exe).
- Create a file called BEServer.cfg in BattlEye working directory on the server.
- Set your private RCon password in the BEServer.cfg.
- Start the RCon tool on your computer.
- Connect to your server with its IP, port and RCon password.
Sample BEServer.cfg
RConPassword xyzxyz
More information
- Support
- Frequently Asked Questions:
- I am getting kicked for the following violation(s). I don't use hacks, so what can I do to resolve this?
- How do I enable BattlEye in-game to be able to play on BE-enabled servers?
- Are administrator rights required when playing with BattlEye enabled?
- I am using a 64-bit operating system but can't seem to find the right files in the download section. Is 64-bit unsupported?
- I am running multiple dedicated servers from one installation. Is there anything I have to keep in mind regarding BattlEye?
- BI forum sticky threads