Documentation

Below you can find information on how to use BE’s custom features that are provided for players and server admins. If you have any questions regarding this information please feel free to send us an email.


Client-side BE commands

You can send commands to the BE Client by entering “#beclient [command]” in the chat area on BE-enabled servers. The following commands are currently available:

guid
Show your own BE GUID.

players
Show information about all players on the server, including their GUID and ping.

NOTE: The BE Client is designed to work independently on all clients and therefore doesn’t require any manual configuration affecting its performance.


Server-side BE commands

You can send commands to the BE Server by connecting via BE RCon and entering the commands in the console. Previously it was also possible to log in as a game admin in-game and issue commands via “#beserver [command]”, but for security reasons this feature has been disabled. You can also automatically execute any commands on server launch by putting them into a file called “BEServer.cfg” (“beserver.cfg” on Linux) in your BE working directory. The following commands are currently available:

RConPort [port]
Specify the port used to access the server via BE RCon (required). Note that this port needs to be different from the game server’s port(s).

RConIP [ip]
Specify the IP address the server should bind to for BE RCon access. This setting is optional and should only be used by experts. For most servers (especially those that only use a single network interface) it should not be needed.

RConPassword [password]
Specify the password required to access the server via BE RCon (required).

maxPing [ping]
Specify the maximum ping allowed on the server. Players will be kicked when violating this limit for a while. If ping is -1 there is no limit (default).

version
Show the current BE Server version.

update
Immediately check for a BE Server update.

players
Show information about all players on the server, including their GUID and ping. The player # being shown is used for other commands described below.

admins
List all RCon clients/admins that are currently connected.

kick [player #] [reason]
Kick the player from the server and optionally show him a reason.

loadBans
(Re)load the BE ban list from bans.txt in your BE working directory. This command is automatically issued on server launch.

writeBans
Re-write the current ban list to bans.txt. This command can be used to remove expired 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. Optionally you can also display a reason.

addBan [GUID or IP address] [time in minutes] [reason]
Same as “ban”, but allows to ban a player that is not currently on the server.

removeBan [ban #]
Remove a ban (get the ban # from the “bans” command).

missions
List all mission files available on the server.

say [player #] [message]
Send an in-game message to players. If the player # is -1, the message is sent to all players, otherwise the message is sent privately to the specific player.

loadScripts
(Re)load the client-side script scans/filters (explained below). This command is automatically issued on server launch.

loadEvents
(Re)load the server-side event filters (explained below). This command is automatically issued on server launch.

maxCreateVehiclePerInterval [amount] [interval in seconds]
Specify the maximum amount of “createVehicle” events a player is allowed to send per interval. If amount is -1 there is no limit (default), if amount is 0 the use of the command is completely forbidden.

maxDeleteVehiclePerInterval [amount] [interval in seconds]
Specify the maximum amount of “deleteVehicle” events a player is allowed to send per interval.

maxSetPosPerInterval [amount] [interval in seconds]
Specify the maximum amount of “setPos” events a player is allowed to send per interval.

maxSetDamagePerInterval [amount] [interval in seconds]
Specify the maximum amount of “setDamage” events a player is allowed to send per interval.

maxAddWeaponCargoPerInterval [amount] [interval in seconds]
Specify the maximum amount of “addWeaponCargo” events a player is allowed to send per interval.

maxAddMagazineCargoPerInterval [amount] [interval in seconds]
Specify the maximum amount of “addMagazineCargo” events a player is allowed to send per interval.

maxAddBackpackPerInterval [amount] [interval in seconds]
Specify the maximum amount of “addBackpackCargo” events a player is allowed to send per interval.

NOTE: You can also use the BE Server to issue commands to the game itself by using the “#” prefix. For example, entering “#mission [mission]” causes the game


The BattlEye working directory

The BattlEye working directory is the location the BE Client and BE Server are actually loaded from. On Linux the BE installation directory is equal to the BE working directory. On Windows however, they are not loaded from the BE installation directory because they usually don’t have write access there and therefore would not be able to automatically update or save new bans on the server.

The BE working directory is located in one of three places:
– A folder named “BattlEye” in the game’s application data folder (e.g. “C:\Users\[username]\AppData\Local\ArmA 2 OA”) (default)
– A folder named “BattlEye” in the path specified by the “-profiles” command-line parameter
– A folder specified by the “-BEpath” command-line parameter

The BE Server loads all of its configuration files (BEServer.cfg, bans.txt, scripts.txt, etc.) from the working directory and therefore placing them into your BE install folder has no effect, unless you specify the BE working directory to be equal to the install folder.

NOTE: Even with a custom BE working directory the BE files in the BE installation directory need to be present at all times. Otherwise the game client or server will assume that BE was uninstalled and will also delete the BE files from the working directory as a cleanup process.

More Tweets

Over 322,000 cheaters have been banned from PUBG so far, more than twice as many as posted by @PLAYERUNKNOWN just a month ago. 7 days ago