Many players are reporting the Battlefield 6 grenade damage challenge not tracking issue, especially in the Assault category.
The challenge stays stuck at a number like 45/1000, never updating even after multiple grenade kills and consistent explosive damage. This bug makes it impossible to progress Assault class unlocks, slowing down mastery and locking players out of weapons, gadgets, or tier rewards tied to grenade usage. The frustrating part is that the challenge has been broken for weeks, and it doesn’t respond to natural gameplay or exploit attempts.
This guide explains why your grenade progress isn’t moving and how to temporarily work around the problem until an official fix arrives.
Quick Fix
Switch to matches with bot enemies, use damage-over-time grenade types, and play one full round without leaving early—this forces the challenge to refresh on session end.
Fix 1 – Play Full Matches So Damage Registers at End-of-Round
The Battlefield 6 grenade damage challenge not tracking often fails because damage only logs during the final round summary. Leaving early prevents the system from counting hits.
Staying the full match gives the game’s backend time to process all grenade damage.
Many players saw progress jump only AFTER the scoreboard appeared.
Steps:
- Throw grenades consistently
- Finish the full match
- Check the challenge once the round ends
How it helps: Ensures grenade damage is saved properly during the end-of-round sync.
Fix 2 – Use Fragmentation Grenades Instead of Special Grenades
Some grenade types don’t count toward the challenge because the system only registers traditional explosive damage. This creates the impression that the grenade damage challenge not tracking is totally broken.
Standard frags have the highest tracking reliability.
Flash, gas, and EMP grenades do not count.
Steps:
- Go to Loadout → Gear
- Select “Frag Grenade”
- Deal direct explosive damage
How it helps: Makes sure your grenade damage uses a trackable explosive type.
Fix 3 – Aim for Damage, Not Kills
The challenge tracks damage dealt, not kills. Many players waste time trying to secure grenade eliminations, but partial damage often counts more reliably.
This helps fill the meter even if the enemy survives.
Great for clustered fights or choke points.
Steps:
- Throw grenades into groups
- Focus on tagging enemies
- Don’t worry about kill credit
How it helps: Accumulates steady damage even in chaotic fights.
Fix 4 – Restart the Challenge by Switching Class Temporarily
Sometimes the Assault challenge “freezes.” Switching to Recon or Support, then back to Assault, resets its data stream.
This soft refresh can nudge the system to start tracking again.
It works well mid-session.
Steps:
- Change class to another role
- Play for 1–2 minutes
- Switch back to Assault
- Throw grenades again
How it helps: Clears temporary tracking bugs blocking the challenge.
Fix 5 – Try Bot-Only Lobby for Guaranteed Tracking
Bots reliably take grenade damage, and the dev servers track bot damage more consistently.
This helps players dealing with the Battlefield 6 grenade damage challenge not updating in PvP.
Bot damage syncs cleanly and often updates the counter.
Steps:
- Create or join a bot lobby
- Throw grenades at grouped enemies
- Finish full match
How it helps: Allows the server to log damage without PvP lag or sync errors.
Fix 6 – Avoid Conquest for This Challenge (Bugged Mode)
Many reports show Conquest specifically fails to track grenade damage.
Breakthrough, Rush, and custom modes track more consistently.
Switching modes helps bypass the faulty data logging.
Steps:
- Play Rush or Breakthrough
- Use grenades at choke points
- Avoid Conquest until patched
How it helps: Uses modes where grenade damage logs properly.
Fix 7 – Disable Kill Cam & Instant Replay
Kill cam transitions interrupt grenade damage logs. This often causes partial or full lost progress, feeding into the grenade challenge stuck at 45/1000 situation.
Disabling replays prevents tracking interruptions.
Steps:
- Settings → Gameplay
- Kill Cam → OFF
- Instant Replay → OFF
How it helps: Prevents data loss caused by cinematic transitions.
Fix 8 – Use Grenades After Tagging Enemies First
Spotting enemies before throwing grenades forces the engine to assign them properly in the backend.
Spotted enemies register damage more accurately.
This avoids the bug where “unidentified targets” don’t count.
Steps:
- Ping enemies
- Then throw grenades
- Repeat in heavy fights
How it helps: Guarantees your grenade damage attaches to valid targets.
Fix 9 – Reset Your Loadout to Default
Loadout corruption sometimes makes grenade damage invisible to the tracking system. Resetting the loadout removes hidden conflicts.
Many players had the challenge begin tracking again immediately.
Steps:
- Go to Loadout
- Reset to default Assault
- Re-equip frag grenades
How it helps: Fixes broken gear data that blocks challenge updates.
Fix 10 – Check for Game Patch Notes
Developers acknowledged damage-tracking issues affecting several classes, including Assault.
If your game isn’t updated, the bug remains active.
Keeping up with updates helps resolve backend tracking issues.
Steps:
- Check for updates
- Install latest patch
- Try the challenge again
How it helps: Ensures you’re not stuck on a version where grenade tracking is broken.
Fix 11 – Avoid Using Grenades With Specialist Abilities Active
Some Specialist abilities interfere with how explosive damage is logged. When abilities modify damage output or apply secondary effects, the Battlefield 6 grenade damage challenge not tracking bug triggers more often.
Deactivating abilities before throwing grenades ensures pure explosive damage is logged.
This makes tracking more reliable during fights.
Steps:
- Don’t activate ability before throwing
- Throw grenade normally
- Check tracking after a match
How it helps: Ensures only clean explosive data is sent to the challenge system.
Fix 12 – Throw Grenades at Vehicles for Guaranteed Damage Registration
Vehicle damage almost always registers, even when infantry damage doesn’t. This helps players bypass the grenade damage challenge not updating by focusing on large hitboxes.
Vehicles provide consistent damage ticks.
Even small hits count toward the challenge.
Steps:
- Target tanks, APCs, and transports
- Throw frag grenades under the vehicle
- Repeat throughout the match
How it helps: Gives reliable damage logging due to vehicle tracking consistency.
Fix 13 – Avoid Splash Damage From Other Players’ Explosives
If two grenades explode near each other, damage attribution sometimes breaks. This causes the Battlefield 6 grenade damage challenge not tracking bug mid-fight.
Throwing grenades when alone or in quieter spaces avoids this conflict.
This is especially important in large chaotic modes.
Steps:
- Throw grenades in isolated fights
- Avoid stacking explosives with teammates
How it helps: Ensures your grenade gets full, clean damage credit.
Fix 14 – Lower Server Load by Playing on Low-Latency Servers
High-latency servers fail more often at tracking explosive events. This heavily impacts the grenade challenge, making Battlefield 6 grenade damage challenge not tracking more frequent.
Joining low-ping servers ensures stable damage registration.
This works best for players outside main regions.
Steps:
- Select lowest ping server
- Rejoin match and throw grenades
- Finish full round
How it helps: Reduces packet loss that removes explosive damage logs.
Fix 15 – Turn Off HUD Damage Indicators
Strangely, HUD damage indicators can delay damage logging during grenade explosions. Turning them off reduces UI conflicts that trigger the grenade damage challenge stuck bug.
This is because HUD widgets compete with backend hit logging.
Switching them off makes damage count smoother.
Steps:
- Settings → HUD
- Damage Indicators → OFF
How it helps: Removes UI-related delays that affect grenade damage tracking.
Fix 16 – Avoid Multi-Kill Grenade Moments (Known Bug Trigger)
When grenades hit multiple targets at once, the game sometimes logs the kills but not the damage. This contributes heavily to the Battlefield 6 grenade damage challenge not tracking issue.
Single-target hits track more reliably.
This is a quirk of the current patch.
Steps:
- Throw grenades at individual enemies
- Avoid cluster-fire areas for this challenge
How it helps: Ensures your grenade deals trackable, unshared damage.
Fix 17 – Combine Grenade Damage With Gunfire for Split Logging
Grenades alone sometimes fail to register, but when you shoot the same target before or after an explosion, the combined damage forces the system to log properly.
This method bypasses the grenade damage challenge not updating bug.
It’s reliable and works in any mode.
Steps:
- Hit target with gunfire
- Throw grenade immediately
- Let damage stack
How it helps: Creates a damage bundle the server is more likely to record.
Fix 18 – Use Grenades Indoors for Guaranteed Impact Damage
Open-area blasts sometimes don’t track. Indoors, blast radius and walls create guaranteed impact logs, preventing the Battlefield 6 grenade damage challenge not tracking glitch.
Indoor grenade hits produce stable damage numbers.
Great for buildings and tight objectives.
Steps:
- Find indoor choke points
- Throw grenades near walls for bounce-damage
- Finish the round
How it helps: Increases the chances of consistent explosive damage registration.
Fix 19 – Reload Your Soldier Customization
Broken soldier customization data can desync grenade log events. Reloading your soldier resets backend bindings, which often fixes the grenade damage challenge not progressing bug.
This is useful after patches or crashes.
It’s a fast fix in the menu.
Steps:
- Go to Soldier Customization
- Switch to a different Assault preset
- Switch back
How it helps: Clears corrupted loadout data impacting grenade tracking.
Fix 20 – Throw Grenades Immediately After Respawning
Grenade damage logs most reliably right after spawning, before your character enters heavy combat interactions. Many players see progress only when damaged right after respawn.
This avoids the backend desync that triggers the Battlefield 6 grenade damage challenge not tracking issue.
It’s simple and surprisingly effective.
Steps:
- Respawn
- Immediately throw grenades at close enemies
- Repeat
How it helps: Uses a clean backend state for flawless grenade damage logging.
Why isn’t grenade damage counting in Battlefield 6?
Grenade damage often doesn’t count in Battlefield 6 because the game’s explosive damage event is not always registered by the backend progression system. When multiple players throw grenades into the same fight, the engine sometimes gives the final damage credit to the player who tagged the target last — not the grenade that actually exploded.
This causes your explosive challenge to freeze, even when you land full-damage hits.
The issue also appears when:
- Enemies die from bleed-out instead of the explosion
- Targets take self-damage or team damage first
- The grenade detonates too close to cover
- Smoke, flash, or stun throwables override the damage event
This isn’t a settings issue — the Frostbite tracking layer simply drops explosive data packets during high-intensity fights.
Is the Assault grenade challenge bugged in Battlefield 6?
Yes — the Assault grenade challenge is bugged for many players after the recent update. The patch changed how explosive damage is categorized, and some grenades no longer register as “Assault grenade damage.”
Even standard frag grenades sometimes get treated as “environmental damage,” causing progress to freeze.
Players report the bug most commonly when:
- Using the Assault class grenade while sprinting
- Throwing grenades during packet loss
- Killing enemies behind partial cover
- Hitting multiple targets with one explosion
The challenge UI still displays your current progress, but the backend often fails to add new damage. This is a known issue, and DICE is expected to patch it in a future update.
Why is my grenade damage stuck at 45/1000?
Your grenade damage is stuck at 45/1000 because the server likely cached your last valid explosive hit and isn’t adding new values. This happens when the damage event fails validation due to inconsistent hit detection on grenades.
Reasons progress gets stuck:
- The grenade bounced off geometry and counted as a “non-lethal collision”
- Indirect damage went to armor instead of health
- Another player hit the enemy first
- Damage happened during a revive animation
- The explosion triggered while the target was invulnerable from spawn protection
Since the game only counts final, valid explosive damage, the challenge gets stuck even though you are successfully landing grenade hits.
Do frag grenades or other throwables even track damage in BF6?
Frag grenades do track damage in Battlefield 6, but only when the backend successfully receives a clean explosive damage event. Unfortunately, this tracking is inconsistent due to bugs with:
- Blast radius validation
- Armor vs. health priority
- Multi-kill damage stacking
- Explosion timing on laggy servers
- Players dying from bleed-out or friendly fire before the grenade hits
Throwables like flashbangs, smoke grenades, and EMPs will never count because they deal no explosive damage.
But even frag grenades, thermites, and impact explosives sometimes fail to send the correct damage packet after the latest update.
This makes it feel like grenades “do nothing” even though they clearly hit enemies.
Is the “Deal damage with grenades” assignment broken after the update?
Yes — after the most recent patch, the Deal Damage with Grenades assignment is partially broken. The update changed how explosive impacts and splash damage are calculated, which unintentionally broke challenge progression for many players.
Symptoms include:
- Damage counting only once per match
- Only direct hits registering, not splash radius
- Random values like “+1 damage” on near-lethal explosions
- Damage stopping at a fixed number (45, 100, 250, etc.)
Until a patch arrives, the most consistent method is using grenades in tight indoor fights where splash damage is guaranteed and less likely to be overridden by teammate bullets.
How do I fix grenade damage not tracking in Battlefield 6?
To fix grenade damage not tracking in Battlefield 6, you need to avoid the situations where the backend fails to recognize explosive damage. The tracking bug occurs mostly when grenades detonate near cover, inside cluttered geometry, or during high server load.
Start by throwing grenades in tight indoor areas, where the radius cannot be absorbed by walls or angled surfaces. Also avoid throwing grenades during packet-loss spikes—explosive damage often disappears entirely.
Reliable fixes:
- Turn off FSR/DLSS (reduces hit-reg desync on some systems)
- Restart the match after damage freezes
- Use grenades in close-range infantry fights
- Avoid throwing during sliding/sprinting
- Disable crossplay temporarily (reduces instance lag)
These steps don’t “repair” the bug but help ensure the game actually logs your explosive damage.
Which grenades count toward the Assault challenge?
Only explosive-damage grenades count toward the Assault grenade challenge. That means:
Counts:
- Frag Grenade
- Impact Grenade
- Thermite Grenade (damage-over-time counts)
- Incendiary Grenade
- Assault-class explosive throwables
Does NOT count:
- Smoke Grenade
- Flashbang
- EMP
- Signal/Scan grenades
- Utility throwables with no explosive profile
The backend system checks for the “explosive damage event” flag, not which class you’re using. As long as the throwable deals real damage, it qualifies — but the current patch frequently mislabels explosive hits, which is why many players see inconsistent progress.
Do grenade kills count or only raw damage?
Both kills AND raw damage count, but raw damage is what the assignment actually tracks internally. A grenade kill only progresses the challenge if the explosion dealt direct explosive damage before killing the target.
If the enemy bleeds out, is finished by a teammate, or dies from environmental hazards, the kill does not add to progress.
Examples that count:
- Pure explosive kill
- Explosive splash damage on armor + health
- Fire/thermite DOT damage
Examples that do NOT count:
- Bleed-out kills
- Team-damage finishing the enemy
- Explosion happening during spawn protection
- Grenade bouncing and dealing 0 explosive damage
So yes, kills count—but only if the damage packet is valid.
Does splash damage count?
Yes — splash damage counts, but only when the backend registers it correctly. Battlefield 6 uses a layered hit-reg system where indirect splash must pass a validation check:
Splash damage may fail when:
- The enemy is partially behind cover
- You damage only armor and not health
- Too many effects trigger at once (bullets + explosions + fire)
- Server lag drops the damage event
- The grenade hits furniture, sandbags, or props that absorb radius
Because the system is inconsistent, splash is more reliable in:
- Hallways
- Small rooms
- Bunkers
- Stairwells
These environments prevent the grenade’s radius from being blocked or clipped by geometry.
Is the challenge progression stuck for all players or just some?
The challenge is bugged for many players, but not universally. Most reports show that the grenade challenge becomes stuck after the latest update, especially in crossplay lobbies or during high server latency.
Progression tends to fail for players who:
- Play on crowded 128-player servers
- Use high-ping regions
- Spam throwables in chaotic fights
- Hit mostly armored targets
- Use frag grenades near cover or elevation changes
Some players can still progress normally, especially in smaller modes like Tactical Ops, where the server processes damage more cleanly.
DICE is aware of explosive tracking issues, and this challenge will likely be patched in a future update.
Final Thought
The Battlefield 6 grenade damage challenge not tracking bug affects many players, especially those stuck at numbers like 45/1000. Using frag grenades, playing full matches, switching classes, or using bot modes helps progress until an official fix arrives. With the right approach, you can still complete the challenge while waiting for DICE to patch the tracking system.