Initial Battlefield 6 Tweaks Implemented Without Official Patch Release

Battlefield Studios, which encompasses the talented teams behind Battlefield 6 including DICE, Ripple Effect Studios, Criterion Games, and Motive Studio, recently announced a series of balancing adjustments to enhance gameplay. Notably, these tweaks were implemented seamlessly, without necessitating a patch download for players.

Summary of Changes

The recent updates focus on refining specific aspects of gameplay. Here are the key modifications:

Increased the ticket count in the Rush game mode to 100 from the previous cap of 75.
Decreased the muzzle velocity of the M2010 ESR from 900 m/s to 800 m/s.
Reduced the muzzle velocity of the PSR from 750 m/s to 720 m/s.
Shotgun projectiles will now factor in drag effects.

This set of adjustments marks just the initial phase of ongoing balancing efforts. Although Battlefield 6 launched robustly—achieving record player numbers on Steam and receiving favorable critical acclaim, including positive feedback from our review—the community’s desire for further refinements has been vocal. The developers will need to remain vigilant in monitoring and addressing live service dynamics.

Community Updates and Cheat Prevention Measures

In related news, discussions on Reddit have highlighted that the partnership between the developers and major console manufacturers, Sony and Microsoft, is yielding positive results in the fight against cheats involving Cronus Zen devices. Reports indicate that the first batch of permanent bans has been enacted against users employing these cheats. The creators of Cronus Zen have suggested to players to refrain from using the device temporarily:

We’re currently advising all Battlefield 6 players, especially those on PC using the Zen with any of our latest scripts, to pause usage for now. The team is actively testing to understand what’s causing it and ensure everything remains safe and stable. Please avoid using the Zen in Battlefield 6 until we confirm it’s fine to resume. We also ask that no one publicly shares or discusses any bans — this draws unnecessary attention to the community and makes testing more difficult.

For more detailed information on these updates, please refer to the > source.