[p]Hey Soldier,
[/p][p]We saw ongoing discussion on how match infection rate (MIR) could be effectively calculated when cheaters and cheat developers aim to avoid detection. While we can’t share every detail, we can explain the fundamentals of its design. MIR includes both confirmed cheaters – all of which are banned – and those we suspect based on the full set of detections and signals that are constantly growing and updating. These signals include ones we can’t use as conclusive evidence by themselves such as player reports, gameplay footage from social media, etc.
[/p][p]Every match that includes either a confirmed cheater or suspected cheater is marked as infected. We then calculate all the confirmed and suspected infections versus the total number of matches to determine the MIR. As Javelin and Battlefield engineers introduce new detection signals, and our game integrity analysts refine, add, update, or retire existing ones, MIR updates automatically to reflect those developments. This allows it to effectively shift alongside the evolving threat landscape and maintain an accurate view of the overall match health.
[/p][p]Because MIR was designed as a look-back metric to reflect these shifts and minimize rework, it needs time to mature and stabilize. This is why we are looking at the previous month in these updates. For example, after this additional month the overall MIR calculated for December 31st matured to 2.28% from its previous value of 3.09% as reported in our earlier December post.[/p][p]
[img src="https://clan.akamai.steamstatic.com/images/45712411/2e05cb31d9442d8b1a94c0ee606003007a02ddee.png"][/img][/p][p]Match Infection Rate: The percentage of matches across the title that were negatively impacted by at least one cheater. This includes all suspected cheaters, even those we might not have enough evidence to enforce against.[/p][p][/p][p]In January, MIR started at 2.38%. Over the course of the month, gradually increasing with only a few periods of decline. There were two significant reasons for this: one was a significant increase in our ability to detect and ban 6 additional “Stealth” cheats that purposefully avoid being high impact and therefore avoid player reports and obvious detection signals. The other was a new ban acceleration method tested on the 18th, and then initially deployed on 26th. January still saw that gradual increase end at 3.60% on the 31st as of this update.
[/p][p]Through January, EA Javelin Anti-Cheat prevented 384,918 attempts to cheat or tamper with the game before they could impact matches. We are still tracking 224 cheat-related programs, hardware solutions, vendors, resellers, and their associated communities. Of those, now 212 of them (94.64%) are reporting related feature failures, detection notices, downtime, or fully taking their cheats offline.
[/p][p]We’ll continue reviewing your questions and feedback and will be sharing February’s metrics in roughly another month’s time.[/p][p]
[/p][p]Keep it fair out there - see you on the Battlefield.[/p]