Battlefield 6 Dev Investigates ‘Unexpectedly Fast’ Time-to-Death That Feels Rigged

Battlefield 6

Battlefield 6

The debut open beta for Battlefield 6 set new series records with a huge turnout on PC, PlayStation 5, and Xbox Series X/S.

Between August 7 and 10, players explored maps such as Liberation Peak, Siege of Cairo, and Iberian Offensive, trying out both classic elements and fresh additions like the well-received drag-and-revive system.

But despite the excitement, an unexpectedly fast time-to-death (TTD) became the main topic after the servers shut down, with many saying it broke combat flow.

What’s DICE’s First Move in Fixing the TTD Issue?

DICE’s principal game designer, Florian Le Bihan, swiftly addressed the matter on X, saying the team was going through beta feedback and asking players to send footage of “super bullets” or abnormally quick deaths.

Revives in Battlefield 6
expand image
Credit: DICE

In some cases, players were eliminated in a split second, sometimes without catching sight of the gunfire, or took all the damage in one hit instead of over time.

What Exactly Is Time-to-Death and Why Was It Controversial?

For those unfamiliar, TTD measures how long it takes from the moment a player starts taking damage to when they’re eliminated.

Battlefield 6 Wall
expand image
Credit: DICE

In theory, a fast TTD can make firefights feel tense and realistic. In practice, beta participants reported that the system felt wildly inconsistent.

Many claimed it could take half a magazine or more to kill an opponent, yet they would be cut down in what looked like one or two bullets.

Others described dying behind full cover, taking delayed damage seconds after disengaging, or losing gunfights to opponents they began shooting first.

Could Battlefield’s Netcode Be the Culprit?

Discussion soon centered on Battlefield’s netcode, with long-time players arguing the root cause could be server–client communication.

Battle 6 Tanks
expand image
Credit: DICE

If hit data is delayed and then delivered in a single burst, the receiving player experiences what’s known as a “one-frame death” — an instant kill with no time to react, even though multiple shots were actually fired.

The same frustration was present in Battlefield 4, reappeared in Battlefield V, and now appears once more. While improvements were made in past entries, the issue was never fully eradicated. 

Did Map Size and Design Make the TTD Issue Worse?

What made it more noticeable in the beta was the combination of high player counts, small map designs, and visual clutter.

Battlefield Tips for New and Returning Players
expand image
Credit: DICE

On infantry-focused maps with limited sightlines, even minor network delays could feel punishing. Gunfights favored cautious play, with players pre-aiming corners and holding angles, which many felt clashed with Battlefield’s dynamic style.

Le Bihan’s push for player footage is intended to track down the issue before the August 14–17 beta weekend. Using live match footage lets the devs recreate situations in a controlled setup and identify if the cause is server load, weapon balance, or network behavior.

That said, long-time fans warn that while tweaks can reduce the frequency and severity of bad TTD moments, netcode quirks are rarely fixed overnight. For now, DICE has made it clear that this is a priority heading into launch on October 10, 2025.

For more like this, stick with us here at Gfinityesports.com: the best website for gaming news.