Fairfight ban info

**dongingman** · 10-25-2016

Credit: JohnnySins

1. Aimbot
We know from the FairFight SDK headers that FF can see your position, the enemy position, camera angles, and therefore they can calculate the number of pixels moved between each frame. (FairFight SDK Headers) I've played around with my aimbot settings enough to know that FF is generally good at detecting it. Since pretty much everyone and their whole extended family here has aimbot in their hack (and uses it), here's what helps me avoid detection.

FOV of 30 degrees or lower
High smoothing factor
Bone randomization
Only lockon to visible enemies

I've had accounts last for the full 7 days with these settings, probably because I'm not snapping 360 degrees all over the place.

2. ESP
In other games with FF implementation, people have received bans for what they believe was caused by ESP.

Personally, I never had any issues with FF when I was playing on my premium account with ESP only. For the sake of saving time, I won't mention anything more about it - but know that people have raised flags about it in the past.

3. Magic Bullet / AutoHeal / StartEndDamage / BPS
When I first started hacking in BF4, I mainly used BPS values of 4-8 for over a year before I received my first level 3 monitoring ban. Generally, I've found that modifying BPS is usually safe (unless you always use some insane value netting one shot kills), but modifying StartEndDamage will almost certainly result in a ban.

Ever since I implemented magic bullet and auto heal, my accounts have never lasted over 12 hours while ***********. I did the following with no success:

Use a "realistic" damage value of anywhere between 16.0 to 25.0
Swap out the killfeed ID with KILLED
Swap out the killfeed ID with NO WEAPON
Randomize the killfeed ID with the enemy's own weapon
Only call autoheal if I'm not in vehicle, or if my health < 90

None of these tactics helped, which leads me to believe there's no way to use these two features safely. Calling the function hundreds of times per frame will lead to you sending over 2000 damage to a player -- something that would surely trigger FF. In addition, I've heard people say:
Quote:

"Swap out your killfeed to say KILLED, FF won't be able to detect that!1!1!1

I've tried all variations of this, didn't help me one bit. Even if FF doesn't know the type of weapon used to kill someone, they can still see the number of kills you're getting in an elapsed period of time.

4. Spectators
Now before you start laughing, this actually happened to me. Back when BF4 first came out, I hacked on a premium account for 4-5 months before I quit the game. At the time, I did not have spectator warning implemented in my hack and this happened:

\Someone recorded me hacking my balls off on metro with a friend and posted it on reddit. FF employees manually reviewed it, and added me to their suspension list to take effect when I next logged in.
I took a break from BF4 for about a year, came back and got level 3 monitoring after one game. While I've heard BF1 has no spectator mode, I wouldn't be surprised if they implement that feature later down the road. And if I'm not mistaken, the virtual function getSpectators() is still there, which is a sign it may return. At the end of the day, if you're on a premium account, try not to get recorded and banned for something like this.

5. Age of the account, hours played, rank
From the BF4 reddit:
Quote:

It really depends on a lot of things really, people who have had other accounts banned or are using gametime tend to get removed quicker. It also depends on what exactly they are doing, sometimes it takes longer to gather certain stats to make sure they are 100% a cheater. All of our bans have random delays but the time depends on how much they use the cheat and how much impact it is having on other players.
And yes you are correct, the first time a player is suspended in BF4 or Hardline (other games only use perm bans) they get a 1 week suspension and a stats reset and are closely monitored. The 2nd time they are banned they loose that account.

I can attest to this personally, I find that hacking lightly in the beginning of the account's lifespan (usually from 0 hours played -> 1-2 hours) will dramatically lengthen my gametime until an inevitable FF ban. "Hacking lightly" for me usually means the following:

No soldier or vehicle aimbot
No Magic Bullet
No Auto Heal
No BPS value > 4
No RAWR or XD-1
No Operation Locker

Generally, I find that the longer I take to "establish" a legitimate account with semi-plausible stats, the longer I can last when I decide I want to ragehack. Obviously if you're on gametime, it doesn't matter but this strategy really helps on premium accounts.

**Paralyze** · 10-26-2016

/stickied .

**mujugamma** · 10-26-2016

GOOD! ADVICE!!

**Impetus420** · 12-07-2016

"Screenshots, keyloggers and pc monitors are just 3 of the anti cheat mechanisms used in bf1."

Can someone expand a bit on how this works? It takes screenshots of my game screen and sends it do dice/EA? It also logs all button presses in game? And monitors all my processes and info about my computer?? This game is a privacy nightmare :/ But so is the internet in general

**dongingman** · 12-07-2016

Originally Posted by Impetus420

"Screenshots, keyloggers and pc monitors are just 3 of the anti cheat mechanisms used in bf1."

Can someone expand a bit on how this works? It takes screenshots of my game screen and sends it do dice/EA? It also logs all button presses in game? And monitors all my processes and info about my computer?? This game is a privacy nightmare :/ But so is the internet in general

Screenshots your IN GAME VIEW, nothing more. Other anticheats (in csgo for example...esea I think) screenshot you regularly if you are a high level.
Button presses is if, you suddenly click so much in game and not clicking at all at the keyboard input
Monitors processes is a norm in EVERY anticheat, they just check the hash and if it's modifying game files