BattlEye: does it really work?

[DeMo]

Let's go straight to the point.
BattlEye: does it REALLY work?

I'm a server admin, dedicated 24/7 server (soldat.click21.com.br:28900), and since the release of Soldat 1.4 I have NEVER seen a player get kicked by BattlEye for using hacks. The only kicks I see are those BE violations "client failed to update" and "corrupted memory #0" stuff.

I know other server admins, I play the game regularly, and it seems that BE is just standing there watching the hackers without taking any action. Some days ago we spotted a guy using the Rambo Bow in a TeamMatch server. Yesterday I saw a screenshot where a guy was using that hack that teleports him to the position of the other players and he kills them with the knife.

So I'm gonna ask again: is BE really working?
I see it kicking a lot of innocent people for those buggy violations and actual hackers having a lot of fun spoiling the game.

After the release of 1.4.2 some players simply can't play Soldat anymore.
For some of them the game won't even start, for another part it's the crappy fonts, video compatibility doesn't work anymore (yeah, even with updated video drivers) and for the rest is BE kicking them for stupid reasons. Some people even started asking us to downgrade the servers back to 1.4.1.

Any clues?
Thank you for your time.

[SirJamesaford]

Didnt read any of this but all i have to say is that ive only seen ONE hacker since BE was put into use.....so IMO yes BE works.....and it works like a mother fucker.....THANK YOU BATTLEYE AND TY SABLE.....

[NinjaGimp369]

BE does work, I've seen about 2-3 hackers getting kicked since it came out. Some hackers have found a way to get around it though..

[ChromedGun]

Yesterday I saw a screenshot where a guy was using that hack that teleports him to the position of the other players and he kills them with the knife.

I was there and he was obviously unexperienced because I could kill him several times.

Okay, BE doesn't stop all the hackers, we can see them but we can't see the ones hacking that BE kicks. On the outside it may seem like it kicks someone innocent.
We also don't know how many that got discouraged to hack because they don't want to be busted by BE. I have also seen one of the bigger server owners (Leo, EnEsCe) that claimed that BE indeed have kicked hackers.

So I think it works, it's still pretty new so it doesn't work 100% and it's pretty much impossible to keep up with hackers since they are always one step ahead about what's hackable and what's not.

[Leo]

It works quite good. Not 100% hack-proof but there is no such system yet and never going to be.

[Will]

the thing is, there's plenty of "invisible hacks" there. Like no-realistic mode while you're playing realistic, no bink, no mov acc and etc. And I think that BE is doing a great job keeping them all out of the game.

[DeMo]

BE does work, I've seen about 2-3 hackers getting kicked since it came out.

That's my problem, I've never seen BE working. I know there are cheaters out there but the only kicks I see are the buggy ones.

I was there and he was obviously unexperienced because I could kill him several times.

You probably weren't there.. I'm talking about a brazilian server.

the thing is, there's plenty of "invisible hacks" there. Like no-realistic mode while you're playing realistic, no bink, no mov acc and etc. And I think that BE is doing a great job keeping them all out of the game.

EXACTLY Will. That's what we see the most here in Brazil. The most popular gamemode here is TM with Survival and everybody using barretts. We're tired of seeing people with no bink, no mov-acc and no startup time (aka no delay). Still I don't see any of them getting booted out the servers.

[Will]

I've seen some of those kicks. I havent played that much on pubs, mostly in my server with a couple of friendds, but the kicks I saw were real.

[SpiltCoffee]

...and "corrupted memory #0" stuff.

Corrupted Memory errors are caused by anything that corrupts the players memory, including hacks. Therefore, BE has been doing it's job, according to this statement.

Of course, not all hacks can be stopped. Really, the aim of BE is to stop n00bs from hacking.

[Leo]

...and "corrupted memory #0" stuff.

Corrupted Memory errors are caused by anything that corrupts the players memory, including hacks. Therefore, BE has been doing it's job, according to this statement.

Exactly, you will never seen a "banned for speed hack" message. Corrupt memory message IS the hack.

[$able]

So I'm gonna ask again: is BE really working?
I see it kicking a lot of innocent people for those buggy violations and actual hackers having a lot of fun spoiling the game.

After the release of 1.4.2 some players simply can't play Soldat anymore.
For some of them the game won't even start, for another part it's the crappy fonts, video compatibility doesn't work anymore (yeah, even with updated video drivers) and for the rest is BE kicking them for stupid reasons. Some people even started asking us to downgrade the servers back to 1.4.1.

1. Yes, it works.
2. These are no buggy violations. "Corrupted memory" includes hacks. If people are kicked for other "stupid" reasons in 1.4.2, its their very own fault, and not BE's - e.g. some used the old 1.4.1 BE update package that doesnt work in 1.4.2.
3. Quit thinking the buggy "Kicked for possible cheating" is in any way caused by BE.

@SpiltCoffee: If you ask me, that is not the aim.

[SpiltCoffee]

Well, you can't stop someone if they have the skills and really want to get past BE... not until they do, usually.

I'd say that, for the most part, it stops people from using premade hacks.

[$able]

Of course, I cant garantuee that no one will ever be able to get around it.

But BE does more than just detecting publicly released hacks.

[Will]

The kicked for possible cheating is Soldats own fault I think, and it has nothing to do with battleye itself. And I haven't even realized there were so many hackers in the game until this version. The pubs seem kinda empty right now. Good thing is, most hacking n00bs don't know what a dynamic IP is.

[Clash]

...and "corrupted memory #0" stuff.

Corrupted Memory errors are caused by anything that corrupts the players memory, including hacks. Therefore, BE has been doing it's job, according to this statement.

There should be no such thing as corrupted memory #0, how the hell would Soldat actually use the address #0?

I'm with DeMo on this, I barely see any people getting kicked for the correct reasons.

[NeonUsui]

I'm with DeMo on this, I barely see any people getting kicked for the correct reasons.

I agree... Never saw any hacker get kicked by BE! And I have played a lot. :/

[.::Blaze::.]

i think it works...but it also has many faults...but doesn't every good thing? and you can't make it perfect

[$able]

How can you judge over BE if you have no clue? No, it has no faults atm, this is the truth.

Also Clash, are you serious? You do know that # stands for "number"? Its just a number to identify the exact violation.

[Espadon]

I've seen BE in action myself, some lolwut guy pops in TW1 and flyhacks to cap the flag. Problem is, BE takes a little bit to kick into gear and he already capped before BE kicked for un-updated client. He actually got back a second time (where I somehow shot him down with a Barrett while he was warping) and then a third time, whereupon he was finally kicked for corrupted memory.

[$able]

Problem is, BE takes a little bit to kick into gear and he already capped before BE kicked for un-updated client.

There is not a single thing you can do about this. Players have to be allowed to update and this takes time (might become shorter in the future though).