As you might have noticed, the random BE kicking problems have finally (!) been resolved in ArmA 1.16. On top of that, I would like to inform you of new features that are now available in the newest BattlEye updates.
Here we go:
New BE GUID
The 128-bit BattlEye GUID (globally unique identifier) can be used to identify and track players. It is based on the secure GameSpy cd-key hash that has never been publicly accessible in ArmA. However the ArmA server uses it each time a player joins to verify that his cd-key is original (i.e. issued by BIS/GameSpy) and has not been "artificially" generated. ArmA only used its own clientside-generated player ID for identification so far, and as I have repeatedly heard, hackers managed to alter their player ID and therefore were able to evade server bans without changing their cd-key or even assume other people's identities.
This is no longer possible with the BE GUID. It is based on persistent unique data and 100% generated on the server using the secure irreversible MD5 algorithm.
The BE GUID of each player is now printed in the server console on game join.
GUID Banning
As the BE GUID is automatically displayed in the server console, a server admin can easily track players and possibly ban them if need be.
You can use this feature by creating a file called "guidbans.txt" in your server's application data (not install!) BattlEye folder (default is "C:\Documents and Settings\[User Name]\Local Settings\Application Data\ArmA\BattlEye" or the -profiles path in case you use it) and adding GUIDs "one-per-line" to it. Optionally you can also specify a unix time stamp describing the release time for the ban. If you don't use it, the ban is permanent. You can also add comments. The BE Server will automatically read this file every 5 minutes, so you don't need to restart the server for changes to take effect.
Example line:
Code:
098f6bcd4621d373cade4e832627b4f6 1242545854 caught hacking 10 times
IP Banning
Not only the BE GUID, but also the IP address of a player is now displayed in the server console. The server admin can use it to ban a player based on IP.
You can use this feature by creating a file called "ipbans.txt" in your server's application data (not install!) BattlEye folder (default is "C:\Documents and Settings\[User Name]\Local Settings\Application Data\ArmA\BattlEye" or the -profiles path in case you use it) and adding IPs "one-per-line" to it. Optionally you can also specify a unix time stamp describing the release time for the ban. If you don't use it, the ban is permanent. You can also add comments. The BE Server will automatically read this file every 5 minutes, so you don't need to restart the server for changes to take effect.
Example line:
Code:
123.123.123.123 1243150654 evil hacker constantly changing his cd-key
BE Server Commands
To execute BE Server commands, normally log in as the server admin in-game and then type "#beserver [command]", e.g. "#beserver players". The BE Server will write possible info to the server console.
- players: You can use this command to list all relevant info (#, name, IP, GUID) of each player on the server.
BE Client Commands
To execute BE Client commands, type "#beclient [command]", e.g. "#beclient players". The BE Client will write possible info to the console/chatlog.
- guid: Show your own GUID.
- players: You can use this command to list all relevant info (#, name, GUID) of each player on the server. Note: The IP address is not available here for privacy reasons.
I will update this thread as I add new features and commands.
Comments are welcome and appreciated.