Jump to content
Sign in to follow this  
$able

Testing new BattlEye feature

Recommended Posts

From now on BattlEye will show a player's GUID in the server console right when he connects. Keep in mind that this GUID is not verified, however as the BE GUID is based on the cd-key hash sent by the client, trying to fake it won't get a hacker far. The regular GameSpy cd-key check would still quickly kick the hacker from the server in this case.

This feature is a workaround to the current engine restriction of only loading the BE Client after the lobby, when the player joins the actual game/mission, and therefore being unable to show a player's BE GUID before that.

In the future it will be possible to block banned players from even entering the lobby. Due to the nature of this workaround these bans won't be like the current ones though, they will instead be based on blocking the player's network packets to prevent him from entering the server, i.e. firewalling against him.

Share this post


Link to post
Share on other sites

Excellent job $able :bounce3:

Share this post


Link to post
Share on other sites

This is great news! Thanks so much =)

Share this post


Link to post
Share on other sites

+1 / Like. :D

I dare say that's the kind of custom tailored support we wouldn't be seeing if Arma2 used Punkbuster or some other solution. I hope $able will be sticking around for the upcoming BIS games. ;)

Share this post


Link to post
Share on other sites
+1 Great

Sadly there is an 'increase' of "illegal" activities lately on MP :(

Can improve it a lot if you run the latest 1.60 betas, BE and v2 signatures-only.

Hopefully more will deploy this especially once official 1.60 patch is released.

Share this post


Link to post
Share on other sites

Very good news indeed. Many thanks for the continued effort to outwit the hackers !

Share this post


Link to post
Share on other sites

$able

i have some suggestions. this new function you added opens up a possibility to lobby kick with rcon. if you could do 1 thing.

#1 include the name on the line.

New player FooBar (1.2.3.4:2304) connected - GUID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx (unverified)

instead of just New Player (....

This is because if your offial rcon we will then be able to do lobby kick by using arma kick command.

#kick Foobar

it would also be nice if you could implement a command which list unverified guids-. " lobby players"

something as simple as

listv : would basicly be the same be as players so this it not nesesary-

listu : would list unverified players connected. "lobby connections"

Share this post


Link to post
Share on other sites
$able

i have some suggestions. this new function you added opens up a possibility to lobby kick with rcon. if you could do 1 thing.

#1 include the name on the line.

instead of just New Player (....

This is because if your offial rcon we will then be able to do lobby kick by using arma kick command.

#kick Foobar

it would also be nice if you could implement a command which list unverified guids-. " lobby players"

something as simple as

listv : would basicly be the same be as players so this it not nesesary-

listu : would list unverified players connected. "lobby connections"

Good suggestion! Something like that is already planned and will be added soon.

Regarding the player name, I will try to add support for it as well.

Share this post


Link to post
Share on other sites
Regarding the player name, I will try to add support for it as well.

it would be a nice thing to add. you can kick people who has been sitting in lobby and ideling all the time. this can helpe public Warfare where some idler has taken up a slot. or any other mission where the slot has a important class for players.

however the only problem with it is that. if you dont have the ID. arma id returned by #userlist and the name of the player has some wanky encoding. example

a russian player named какой-то чувак conected. and you cant type his name.

so you need his id returned by #userlist to be able to kick him.

since we can get the ingame #mission list. would it not be possible to get the ingame #userlist back too?

but it would open up for 3rd party rcons to example. directly autokick players who has shitty nicknames. or if you dont want other encodings than latin. so admin can type his name :p on the server. auto kick on idlers etc etc :D

Edited by nuxil

Share this post


Link to post
Share on other sites

question, can u with this new feature run maxping from the lobby?

so a highpinger doenst come trough the game and desync all Player´s cause of JIP.

Share this post


Link to post
Share on other sites
it would be a nice thing to add. you can kick people who has been sitting in lobby and ideling all the time. this can helpe public Warfare where some idler has taken up a slot. or any other mission where the slot has a important class for players.

however the only problem with it is that. if you dont have the ID. arma id returned by #userlist and the name of the player has some wanky encoding. example

a russian player named какой-то чувак conected. and you cant type his name.

so you need his id returned by #userlist to be able to kick him.

since we can get the ingame #mission list. would it not be possible to get the ingame #userlist back too?

but it would open up for 3rd party rcons to example. directly autokick players who has shitty nicknames. or if you dont want other encodings than latin. so admin can type his name :p on the server. auto kick on idlers etc etc :D

Getting the #userlist result is currently not possible. It might be possible to show the unique player ID though, I will investigate that.

---------- Post added at 12:40 ---------- Previous post was at 12:39 ----------

question, can u with this new feature run maxping from the lobby?

so a highpinger doenst come trough the game and desync all Player´s cause of JIP.

Unfortunately that's not possible.

Share this post


Link to post
Share on other sites

FYI, the new BE Server version fully supports the listing, kicking and banning of players that are in the lobby. It all works the same as before, so there is nothing new to learn.

Also, BE GUIDs are now verified, therefore it's no longer possible to spoof cd-keys and hence GUIDs of other players (it was possible before due to an exploit in the GameSpy cd-key SDK).

Edited by $able

Share this post


Link to post
Share on other sites
FYI, the new BE Server version fully supports the listing, kicking and banning of players that are in the lobby. It all works the same as before, so there is nothing new to learn.

Also, BE GUIDs are now verified, therefore it's no longer possible to spoof cd-keys and hence GUIDs of other players (it was possible before due to an exploit in the GameSpy cd-key SDK).

THANK CHRIST!

Huge breakthrough $able!

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×