XPLOITR
Report a bug or exploit
Call of Duty: Modern Warfare 4Call of Duty: Modern Warfare 4 · PC · version Early access (Campaign), still at launch

"Losing Ground" mission fails with a false friendly-fire message

UnconfirmedUnpatched

Updated

In the Campaign mission Losing Ground, right after the café holdout when the tanks arrive, some players fail the mission with "friendly fire will not be tolerated" even though they are not firing, and it can repeat on every reload. Players reported it from early access and again at launch; restarting the whole mission is the reported workaround.

Lifecycle

Reported · stage 1 of 5

13days open

Since first report

  1. Reported (reached) · now
  2. Confirmed (not yet)next
  3. Acknowledged (not yet)—
  4. Partial (not yet)—
  5. Patched (not yet)—
In current stage 13d
Workaround available
Game
Call of Duty: Modern Warfare 4
Platform
PC
Affected version
Early access (Campaign), still at launch
Kind
Bug
Confirmation
Unconfirmed
Patch status
Unpatched
First reported
Last updated
Latest fix or workaround
Workaround, : Oct 23: restarting the mission got this player past it. Source
How we label issues

Kind

  • Exploit: Repeatable and clearly advantageous to the player using it; essentially cheating.
  • Bug: Everything else: crashes, launch errors, broken features, visual or audio faults.

Confirmation

  • Confirmed: A developer or official account acknowledged it, an official known-issues board lists it, it appears in official patch notes, or 100+ corroborating posts on X were actually counted.
  • Unconfirmed: None of the above yet. Press articles are reports and never confirm an issue on their own.

Patch status

  • Unpatched: Known and open; no fix has been claimed.
  • Reported as unpatched: Players credibly report it persisting, including after a fix claim that never appeared in patch notes.
  • Partially patched: Official patch notes list a fix, but credible later reports say it still happens, or the notes only cover part of it.
  • Reported as patched: A developer, official account or player says it is fixed, but no official patch notes list it.
  • Patched: Official patch notes (a Steam news post or the publisher's patch notes page) list the fix, and nothing credible says it still happens.

Active means still affecting players: Unpatched, Reported as unpatched or Partially patched. Patched and Reported as patched issues are closed.

Estimated impact runs from 0.1 to 9.9 with one decimal. xploitr sets it from the rubric below. Factors: advantage to other players, reach, play blocked or progress lost, frequency, and whether a reliable workaround exists. Patched issues keep their historical impact.

Signed-in community members can report new issues and suggest status changes, such as Fixed or Still unpatched, with their platform, version and a source. Every report and suggestion is reviewed by an editor before anything on the record changes. A new issue is published only when the report has at least three independent sources (distinct accounts, or distinct sites for web pages, after blocked sources are removed), unless the owner approved that issue by hand. Approved input appears as a dated Update from the xploitr community source on the issue's timeline, credited to the member's username (reports can opt out and stay anonymous); nothing is counted or published automatically.

Impact bands

  • 0.1–2.9 Low: Cosmetic, audio, text and UI glitches with no effect on play.
  • 3.0–4.9 Moderate: Narrow gameplay bugs or small exploits, rare or with a workaround.
  • 5.0–6.9 Elevated: Bugs most players in a mode notice: hit registration, desync, balance-breaking damage.
  • 7.0–8.4 High: Widely abused competitive or economy exploits; crashes many players hit.
  • 8.5–9.9 Severe: Launch blockers, widespread progress or item loss, exploits that break the game for everyone.

Each issue has a dated timeline of updates (report, acknowledgement, announcement, fix, workaround). Update summaries are our own words; quotes and excerpts are the source's words, or our English translation when marked.

Estimated impactEstimated impact 4.0 out of 9.9, ModerateOur estimate from how many players it reaches and what it costs them.

Updates · 4

  1. Report

    Oct 16: after the café holdout, the mission keeps failing with "friendly fire will not be tolerated" when the tanks arrive, though the player isn't firing.

    Saft Lad · Steam · Forum thread ·
    “after surviving the cafe holdout im in a constant loop of getting the "friendly fire will not be tolerated" failure right when the tanks show up and start firing, i'm not firing my gun and no one is taking damage, anyone else had or having this issue?”
    Saft Lad · Steam · Forum thread · Open source
  2. Report

    Oct 23: another player has the same issue.

    piotrek47 · Steam · Forum reply ·
    “I have the same issue :/”
    piotrek47 · Steam · Forum reply · Open source
  3. Workaround

    Oct 23: restarting the mission got this player past it.

    emmanuelhg710 · Steam · Forum reply ·
    “Restart the mission, once you see the tank start running and exit the building”
    emmanuelhg710 · Steam · Forum reply · Open source
  4. Report

    Oct 25: another player hit the false mission failure and, with the checkpoint locked, had to restart the whole mission.

    Community report · Steam · Forum reply ·
    “I just got the bug.”
    Community report · Steam · Forum reply · Open source
Sources · 44 CommunitySaft LadSteam · Forum thread+ 3 similar community reportsShow all →
Saft LadSteam · Forum thread
“after surviving the cafe holdout im in a constant loop of getting the "friendly fire will not be tolerated" failure right when the tanks show up and start firing, i'm not firing my gun and no one is taking damage, anyone else had or having this issue?”
  • piotrek47Steam · Forum replyOpen
    “I have the same issue :/”
  • Community reportSteam · Forum replyOpen
    “I just got the bug.”
Show all 4 sources