PlayerUnknown’s Battlegrounds has been using BattlEye to detect and identify cheaters in the game. In a new Twitter post, the company has proudly announced that over 1.5 million players have been banned with it help. Not only is that an impressive number of players, period, for most games, but to realize that that’s just the booted players is mind boggling.
Update on the number of PUBG bans: 1,500,000.
— BattlEye (@TheBattlEye) December 28, 2017
The numbers have been going up since PUBG implemented BE’s technology.
- 50,000 in August
- 300,000 in October
- 700,000 in November
- 1.5M in December
At this rate, there won’t be many of those 26 million Steam PC players left in a few months. All kidding aside, the bans are an assertive move by PUBG Corp to keep the game as cheat-free as possible.
How do you feel about anti-cheat software? Do you know anyone who’s been banned?
What is BattlEye?
To ensure that you can focus on the important parts of game development without having to directly deal with cheating yourself, we made sure that BattlEye is very easy to integrate into any game, making it ready for release within days. BattlEye has no special system requirements: Being very user-friendly, BE needs only little resources regarding CPU, RAM and network bandwidth. The player simply will not notice that BattlEye is running in the background. Integration happens on the server- and client-side part of the game, ensuring that cheaters can be effectively removed from any game session. BattlEye is distributed together with the other game files, so a manual download from our website is generally not required.
BattlEye at its core is a proactive protection system which puts a strong shield around the entire game. That way most hacking is completely blocked to begin with. This system is constantly evolving to cover new forms of attacking games. The remaining hacking is covered by an intelligent dynamic on-the-fly detection system, ensuring that unrelenting cheaters are globally banned quickly. BattlEye thereby does its entire job independently without requiring any input from the developer’s side.
