New BattlEye Features

$able · 05-10-2009, 07:54 AM

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.

[HUD]Dorph · 05-10-2009, 08:50 AM

Thank you - this is much apriciated as arma always have been a pain in the *** to be admin on. This makes it going the right way.
By the way is "#beserver players" the only command avail at the mom?

kju · 05-10-2009, 08:59 AM

Wow

This came completely unexpected. This is excellent news indeed!
Great additions and very much looking forward to see the features used by admins.

Thanks for the hard work $able.

Deadfast · 05-10-2009, 09:29 AM

Wow, very good job!

mr.g-c · 05-10-2009, 01:35 PM

Absolutely Awesome, was always looking forward to something like this

Is version "v1.054" of BE, right?
Edit: Is version v1.054

Ideas:
- Can it be made possible that the "#beserver player" command prints that out also ingame like the normal "#userlist" command? or don't you have influence on that since its Arma core?
- Ultra nice would be of course to ban on guid and ip during ingame when logged in as admin (maybe with a #beserver ban "guid" "ban-time" " ?)

HitmanFF · 05-10-2009, 02:19 PM

Excellent feature indeed!

Being able to see the list of banned IPs and IDs would be nice as well, something like
#beserver iplist / #beserver guidlist
Also being able to remove bans in-game would be quite useful,
#beserver unban ip / #beserver unban guid

Edit: Do you need to have actually started a map to see the players? I tried #beserver players with two people on the server (in the lobby), and the result was

Quote:

16:48:14 BattlEye Server: Players on server:
16:48:14 [#] [Name] [IP Address]:[Port] [GUID]
16:48:14 ----------------------------------------
16:48:14 (0 players in total)

blazer01 · 05-10-2009, 03:11 PM

nice work man

$able · 05-10-2009, 03:45 PM

Quote:

Originally Posted by [HUD]Dorph

By the way is "#beserver players" the only command avail at the mom?

Yes, it is.

Quote:

Originally Posted by mr.g-c

Ideas:
- Can it be made possible that the "#beserver player" command prints that out also ingame like the normal "#userlist" command? or don't you have influence on that since its Arma core?
- Ultra nice would be of course to ban on guid and ip during ingame when logged in as admin (maybe with a #beserver ban "guid" "ban-time" " ?)

It's not possible for #beserver commands (because the BE Server executes them and prints the results in the server console), but I will add a #beclient command soon so that it can be displayed in-game.

I will also add banning commands and more soon.

Quote:

Originally Posted by HitmanFF

Excellent feature indeed!

Being able to see the list of banned IPs and IDs would be nice as well, something like
#beserver iplist / #beserver guidlist
Also being able to remove bans in-game would be quite useful,
#beserver unban ip / #beserver unban guid

Edit: Do you need to have actually started a map to see the players? I tried #beserver players with two people on the server (in the lobby), and the result was

As I said, I will add more commands soon. And yes, the players are only added to the BE Server when they join the game.

HitmanFF · 05-10-2009, 04:26 PM

Quote:

Originally Posted by $able

As I said, I will add more commands soon.

Thanks, much appreciated!

mr.g-c · 05-10-2009, 06:27 PM

Very Very awesome!
I hope that BIS will engage you also for Arma2!

05-10-2009, 07:54 AM	#1
$able BattlEye Developer Join Date: Mar 2008 Location: Germany Posts: 164	New BattlEye Features 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. Last edited by $able; 05-12-2009 at 07:02 PM.

05-10-2009, 08:50 AM	#2
[HUD]Dorph Sergeant Join Date: Aug 2007 Posts: 129	Thank you - this is much apriciated as arma always have been a pain in the *** to be admin on. This makes it going the right way. By the way is "#beserver players" the only command avail at the mom? Last edited by [HUD]Dorph; 05-10-2009 at 09:02 AM.

05-10-2009, 09:29 AM	#4
Deadfast Sergeant Major Join Date: Dec 2006 Location: Prague Posts: 1,726	Wow, very good job! __________________ ArmA Addons: Bike Steering Fix \| Deadfast's Cartridges \| Action Menu Editor ARMA 2 Addons: FPS Counter \| RH pistols replacement \| RH AKs replacement NEW \| Chat position fix ARMA 2 Resources: On-the-fly GFX Changer Videos: ArmA II translations \| ArmA II videos

05-10-2009, 01:35 PM	#5
mr.g-c Sergeant Major Join Date: Jan 2007 Location: Germany Posts: 1,929	Absolutely Awesome, was always looking forward to something like this Is version "v1.054" of BE, right? Edit: Is version v1.054 Ideas: - Can it be made possible that the "#beserver player" command prints that out also ingame like the normal "#userlist" command? or don't you have influence on that since its Arma core? - Ultra nice would be of course to ban on guid and ip during ingame when logged in as admin (maybe with a #beserver ban "guid" "ban-time" " ?) __________________ Marek Spanel: [...] Every single element is well taught so that it fits together. So this is a significant change, because with ArmA 1 it was just random, really. We made some units because we had to. There wasn't much passion from our side with the first ArmA, to be honest. This time it's different. (Videogamer.com Interview Please BIS: Arma2 must become a TRUE MASTERPIECE - Not a middle-heavy catastrophe! Last edited by mr.g-c; 05-10-2009 at 02:01 PM.

05-10-2009, 03:11 PM	#7
blazer01 Staff Sergeant Join Date: Apr 2004 Posts: 279	nice work man __________________ Albert Einstein 'The most beautiful thing we can experience is the mysterious.' Science without religion is lame, religion without science is blind.” We can't solve problems by using the same kind of thinking we used when we created them.” But a Big Gun Help's Blaz

05-10-2009, 08:59 AM	#3
kju Join Date: Oct 2001 Posts: 5,793	Wow This came completely unexpected. This is excellent news indeed! Great additions and very much looking forward to see the features used by admins. Thanks for the hard work $able.

05-10-2009, 06:27 PM	#10
mr.g-c Sergeant Major Join Date: Jan 2007 Location: Germany Posts: 1,929	Very Very awesome! I hope that BIS will engage you also for Arma2! __________________ Marek Spanel: [...] Every single element is well taught so that it fits together. So this is a significant change, because with ArmA 1 it was just random, really. We made some units because we had to. There wasn't much passion from our side with the first ArmA, to be honest. This time it's different. (Videogamer.com Interview Please BIS: Arma2 must become a TRUE MASTERPIECE - Not a middle-heavy catastrophe!

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode