Many Battlefield 6 players are struggling with the Support Specialist 2 (Tier 3) challenge, where the Incendiary Airburst Launcher only tracks direct impact damage instead of counting airburst explosions or burn damage. This makes the challenge extremely tedious, nearly impossible to complete normally, and far more demanding than intended.
Here’s the fast explanation:
Battlefield 6 is incorrectly tracking the Airburst Launcher damage source. Instead of recognizing splash, burn, or proximity explosions, the game is counting only direct-impact hits as valid progress. This is almost certainly a progression bug, not a difficulty design.
Before diving deeper, here’s a quick workaround you can try:
Quick Fix: Aim for close-range impacts rather than airbursts, or swap to small indoor fights where direct-hit splash becomes easier. This won’t fix the bug but maximizes progress while waiting for the official patch.
Why the Incendiary Airburst Only Counts Direct Impacts
This challenge is bugged because Battlefield 6 is misclassifying the Airburst Launcher’s damage types. The game should credit:
- Airburst proximity explosions
- Burn DoT (damage over time)
- Indirect splash hits
- Multi-target flame radius damage
But instead, it credits only direct projectile impact damage. That means even if you hit multiple enemies with the explosion — the challenge progress will show 0% unless the projectile physically touches the target.
This is a consistent progression tracking error and is not intended design.
Fix #1: Restart Battlefield 6 to Refresh Challenge Tracking
In some cases, challenges fail to track because the game loads outdated progression data.
Try:
- Close BF6 completely
- Restart
- Re-attempt direct impacts
- Check the progression bar afterward
A restart forces the game to reload challenge scripts.
Fix #2: Switch Specialists, Then Return to Support
Switch to another specialist, play a match, then return to Support Specialist 2.
This refreshes the specialist-specific challenge logic, which sometimes forces the Airburst challenge to start tracking again.
Fix #3: Use Direct Impact Shots in Tight Spaces
Since indirect damage is not counted due to the bug, the fastest workaround is to:
- Fight in small rooms
- Ambush enemies in hallways
- Shoot targets at close range
This increases your odds of landing direct hits despite the bug.
Fix #4: Play Domination or Close-Quarters Maps
Modes like Domination and Infantry-focused playlists make direct impacts much easier.
Recommended locations:
- Indoor control points
- High-traffic hallways
- Corridors where enemies funnel
This lets you complete the challenge faster while waiting for a fix.
Fix #5: Disable Crossplay to Improve Challenge Syncing
Crossplay can cause progression desync, especially for weapon-based challenges.
Steps:
- Turn Crossplay OFF
- Restart BF6
- Attempt direct hit kills again
Some players report the challenge begins tracking correctly afterward.
Fix #6: Clear Cache (PS5/Xbox) or Verify Files (PC)
Challenge data sometimes fails to sync because cached files become outdated.
Console:
- Clear system cache
- Rebuild PS5 database if necessary
PC:
- Steam → Verify integrity
- EA App → Repair
This refreshes gameplay scripts tied to challenge tracking.
Fix #7: Get a Kill, Switch Loadouts, and Check Progress
Occasionally, challenge progress doesn’t update until the player switches weapons or classes mid-match.
Do this:
- Get 1 direct-impact kill
- Switch to another loadout
- Return to Support
- Check challenge tracking
This forces a UI refresh.
Fix #8: Complete Another Challenge First (Triggers Backend Sync)
Sometimes BF6 will not update a bugged challenge until another unrelated challenge completes.
Try:
- Using another weapon
- Completing a quick ribbon
- Finishing an alternate Specialist challenge
Progress for the Airburst challenge may update immediately after syncing.
Fix #9: Re-equip the Incendiary Airburst Launcher
Unequip the launcher, back out of the menu, then re-equip it.
This resets the weapon profile and enables fresh tracking scripts.
Fix #10: Wait for EA Patch (Confirmed Tracking Issue)
This is almost certainly a server-side challenge bug. When challenges require damage types that aren’t being read correctly, fixes must come from EA’s backend.
Signs it’s a patch-level issue:
- Direct hits track, but explosions do not
- Same bug reported by other players
- Challenge progress stuck after multiple matches
- Launcher sometimes tracks 1 kill, then stops
EA typically patches challenge-tracking bugs in hotfixes or mid-season updates.
Is the Battlefield 6 incendiary Airburst coded to ignore DOT (burn) damage?
It appears that the Battlefield 6 Incendiary Airburst Launcher is currently coded in a way that ignores DOT (burn) damage for challenge tracking. Players report that splash damage, fire damage-over-time, and proximity flames do not count toward the Support Specialist challenge. Only direct impact hits register progress, which is not how an incendiary airburst weapon is supposed to function.
In Battlefield 6, burn damage is usually recorded as a secondary damage event. When the projectile explodes, the game should create two separate events:
- The explosion impact event
- The burn-over-time DOT event
Right now the challenge script seems to recognize only the first one. Anything that comes from the flame radius or lingering burn effect appears invisible to the challenge tracker.
This does not necessarily mean the weapon is intentionally coded to ignore DOT. Instead, it suggests a bug where the progression script is linked only to “direct projectile contact” rather than all Airburst-related damage.
This is consistent with other BF6 tracking issues where certain weapons fail to credit kills unless damage comes from the exact expected event ID. DOT damage uses a different internal tag, so if the challenge doesn’t reference that tag, the progress bar never updates.
Until EA updates the tracking logic, DOT damage from the Incendiary Airburst will likely continue to be ignored.
Did the latest Battlefield 6 update break weapon damage registration?
Many players believe the most recent Battlefield 6 update partially broke weapon damage registration, especially for new support gadgets and area-of-effect weapons. After the update, several devices — including the Incendiary Airburst Launcher — stopped registering their full damage types correctly. The game now recognizes direct impacts normally, but indirect explosion damage or burn effects often fail to register in challenges or progression tasks.
This symptom strongly points to an update accidentally modifying internal weapon tags or damage classification tables. When a patch adjusts modifiers, weapon categories, or backend balance settings, certain weapons may lose the link between their damage events and progression events. That appears to be exactly what happened here.
Signs that the update caused a registration problem include:
- Splash kills not updating challenges
- Burn damage not being detected
- Proximity detonations showing zero progress
- Damage numbers appearing but not counting for tasks
- Cross-platform players reporting identical issues
These are classic indicators of a backend patch altering the event identifiers attached to new weapons.
Weapon damage in gameplay still works, which means the damage engine is fine — the problem is that progression scripts aren’t detecting the damage events created by updated weapons.
This points toward a post-update regression rather than intended design.
Does this bug affect other incendiary weapons like shotguns or grenades?
Yes — this bug may also affect other incendiary weapons in Battlefield 6, including incendiary grenades, shotgun fire rounds, and fire-based equipment. While the exact impact varies, several players report that incendiary grenade burns, flame shotgun pellets, and certain gadget-based fire effects are not being tracked properly for challenges or ribbons.
Short explanation:
Incendiary weapons in BF6 rely on two forms of damage:
- Initial impact or explosion
- Secondary burn (DOT) effect
When the tracking system fails to detect the second category, any weapon that relies on fire-over-time becomes inconsistent. For example:
- Incendiary grenades sometimes count only the initial explosion, not the burn damage
- Shotgun incendiary rounds may award kills but not track challenge progress
- Explosive gadgets with flame effects produce hit markers but no progression updates
Because these weapons share similar damage tags with the Incendiary Airburst, the same backend issue can cause multiple fire weapons to break simultaneously.
Players across PS5, Xbox, and PC have confirmed that some incendiary devices feel inconsistent after recent updates. While the problem isn’t universal, Battlefield 6 clearly has incomplete or broken event detection for fire-based damage categories.
This strengthens the case that the bug is systemic and not limited to the Airburst Launcher alone.
Is Battlefield 6 missing damage event tracking for ongoing fire effects?
Yes — current evidence strongly suggests that Battlefield 6 is missing or misreading damage event tracking for ongoing fire effects, especially DOT-based flame damage. Normally, the game tracks multiple hit events when a target stands in fire or takes continuous burn damage. These events should count toward challenges and XP milestones.
However, many players report:
- Burn ticks showing hit markers but awarding no progress
- Fire kills not updating class or weapon challenges
- DOT-related kills behaving inconsistently across modes
- Only direct damage being counted toward objectives
This means BF6’s tracking system is detecting the initial explosion or initial pellet impact, but not the repeating damage-over-time events that follow.
This can occur when:
- Damage-over-time tags are not mapped to the same progression logic
- Backend event IDs get changed during updates
- Fire effects use a separate scripting channel that isn’t hooked to challenges
- UI and backend are referencing two different damage tables
The Airburst Launcher issue highlights this problem clearly — the weapon is functioning, fire effects occur, damage numbers appear, but the challenge refuses to advance.
This type of bug is usually resolved through backend database adjustments, meaning EA can fix it without a full client-side patch.
Can this be fixed through backend assignment sync or weapon rebalancing?
Yes — this bug can absolutely be fixed through backend assignment sync, without requiring a large update or full weapon rebalancing. Battlefield 6 uses server-side configuration files for progression, unlock requirements, challenge tracking, and damage event mapping. If the Incendiary Airburst Launcher (and other incendiary weapons) are producing damage events that aren’t linked to the correct backend IDs, EA can adjust them directly on the server.
Here’s what a backend fix might involve:
- Re-linking burn and splash damage tags to the Support Specialist challenge
- Updating the assignment script to accept multiple damage types
- Adding DOT damage event IDs into the tracking conditions
- Re-syncing all weapon progression tables across platforms
These adjustments do not require a client patch, meaning EA can push the fix quietly during a backend update window.
Weapon rebalancing is a secondary approach. If the Airburst Launcher needs mechanical tuning, EA might include damage adjustments, radius tweaks, or consistency improvements in the next patch. But the core issue — challenges counting only direct hits — is a tracking error, not a balance problem.
The fastest solution is a backend sync, which EA has applied many times in past Battlefield titles for broken assignments and weapons.
Final Thoughts
The Battlefield 6 Support Specialist Tier 3 challenge is currently bugged, and only direct impacts from the Incendiary Airburst Launcher are counting. While frustrating, it’s not intended design — it’s a progression-tracking error.
Your best options right now are:
✔ Aim for direct hits
✔ Play close-quarters modes
✔ Reset challenge data via cache, menu swaps, and restarts
✔ Wait for EA’s patch to fix the Airburst damage classification