Friendly Fire Removal in Ground Battles created a consequence gap – Proposed Solution

Friendly fire used to exist in GRB. It was removed to prevent deliberate teamkilling griefing, a totally valid reason. However, the removal created an unintended consequence: harassment behavior (sustained fire on teammates, ramming) now has zero in-game penalty.

GRB already has a partial friendly fire deterrent system in place for aircraft-related cases. This post explores extending that existing mechanic to ground-to-ground conduct.

Why the Report System Isn’t Enough

From community experience across squadrons, the report system is only effective for catching automated violations (slurs). For behavioral griefing, players have collectively given up on it being effective. A report filed after the match does nothing to deter behavior happening in real-time.

The Problem

Friendly fire damage is disabled in GRB, which is sensible. However, a player continuously firing MG or cannon rounds into an allied vehicle still causes real tactical harm through direct visual and audio exposure. Tracer rounds fired at an allied vehicle leave a visible trail that any attentive enemy can follow (both back to the shooter and forward to the victim).

  • Hits on allied vehicles render visible sparkle effects.
  • Ricochets produce audible sound cues.

None of these require a HUD indicator or spotting system to be exploited; they are direct sensory information available to any enemy in range.

The same applies to repeated deliberate ramming. Pushing an allied vehicle out of cover, into an enemy sightline, or off an elevated position causes direct tactical harm with no current feedback mechanism for the offender.

Hull-down positions, ambushes, and flanking routes can all be compromised through both of these behaviours. The player causing it rarely connects their actions to the outcome, because without a feedback mechanism the loop is completely absent.

Proposed Implementation

Rather than importing the Air Realistic Battles system wholesale, this proposal extends the existing GRB mechanic with a two-stage escalation mirroring what already exists within the game:

  • Stage 1 – Warning: a visible on-screen message is displayed to the shooter when sustained direct fire on an allied vehicle, or repeated deliberate ramming of the same ally (identified as the vehicle carrying the higher speed at the moment of impact), is detected. [The exact trigger thresholds are for the development team to determine]; the principle is simply to distinguish a single accidental shot, brief stray burst, or incidental collision (all of which are genuinely hard to avoid) from deliberate or negligent sustained behaviour.
  • Stage 2 – Kick: if the behaviour continues beyond a reasonable grace period after the warning, the player is removed from the match.

Edge Cases

To avoid false positives:

  • Artillery and area-of-effect weapons: splash damage or explosions affecting nearby allies should not trigger this system. Detection should apply only to direct, targeted fire at a specific allied vehicle.
  • Ally driving into line of fire: a single accidental hit on a teammate who moves into an active engagement should not trigger Stage 1. The threshold logic should account for this, as the existing GRB aircraft system already handles analogous ambiguities.
  • Accidental collisions: given how frequently these occur naturally (particularly in urban maps and tight corridors) a single collision should never trigger the system. The threshold should require repeated high-speed contact against the same ally within a short timeframe, with the system attributing responsibility to the faster-moving vehicle at the moment of impact. This clearly distinguishes a genuine accident from deliberate pushing.

Precedent

The Air Battles’ friendly fire system operates on two parallel triggers: cumulative teamkills, and sustained fire volume on a friendly regardless of whether the target is destroyed. The latter being the mechanic most directly relevant here. Ground Battle’s existing system already follows similar logic for aircraft-related cases. This suggestion adds the ground-to-ground cases to complete the picture.

As an additional benefit, this system would serve as a passive deterrent against targeted harassment, such as players deliberately firing on teammates displaying specific national insignia or decals.

Final Note

Beyond the tactical argument, this implementation would have a broader positive effect on the game environment. A significant portion of the behaviours described here fall into deliberate harassment — players who actively undermine their own team’s efforts with no current consequence. A deterrent system does not need to be punitive to be effective; in many cases a visible warning alone is enough to correct inattentive players, while persistent offenders are removed before the damage compounds. The result would be a measurable improvement to gameplay quality, a reduction in toxic behaviour, and a stronger foundation for the kind of teamplay that makes GRB and SB worth playing at a serious level.

The system asks nothing of players who are already behaving reasonably — it only affects those who aren’t.

Should GRB’s existing friendly fire system be extended to include ground-to-ground sustained fire and ramming cases?

  • Yes
  • Yes, but implementation details need further discussion
  • No
0 voters
2 Likes

Doing this is against the games TOS btw

can you do it in sim too its really annoying with all these captured tanks like how am i suppossed to know the danish M24 was a dannish M24 rushing around the corner at 25 mph while im under fire from 3 other tanks

Ramming a teammate out of cover is the only thing I have a problem with. Shooting teammates is fine since it does absolutely nothing. Also sometimes having dumb teammates is kinda funny, so I don’t even mind high speed crashes in an M18.

1 Like

Ramming into walls & enemy fire is a punishable offense in War Thunder.

Machine gun fire I haven’t processed occurring in months due to me filtering it out. It’s an audible distraction at most.

Firstly:

If you want to create a suggestion you can do so in the suggestion section here on the forum. That section is however pre-moderated and only posts that follow their rules and guidelines will get posted and it can take a couple of weeks for a post to get reviewed for publication. If it gets accepted and made public it then has a chance to get sent to the developers as a suggestion later on.


Secondly; some details i want to correct:

Incorrect, if reported correctly such behaviour is punished. ( A guide on how to create a correct report for each issue can be found here: (How to properly report players and contact Game Masters!). Please note that some issues cannot be reported using the in-game complaint system as the reports won’t contain the necessary logs to investigate. )

Those punishments are listed in the “Fair Play” cheater ban waves together with the teamkill bans, here is an example from the latest such post:

( [Fair Play] Fair Play: June 2026 ), and here they all are sorted from newest to oldest: ( Search results for ‘Fair Play in:title #official-news-and-information order:latest_topic’ - War Thunder — official forum ). They do however only mention those punishments that are 7 days or more, there are many more punishments issued that are shorter.

There is no automatic moderation (with the exception of teamkills/team damage that show up in the destruction feed), all reports are manually handled.

Sad sentiment to see, those reports are actioned and punishments are handed out. perhaps not to the extent or efficiency that you personally would like to see, but it does happen. Long term offenders are even permanently banned as showcased in the quote from the “Fair Play” post above.

Correct, it’s more of a long term thing.

They do eventually get punished for it. if they continue doing it after a punishment the length of the next one will increase, until it’s eventually permanent.

Reasonable suggestion, this would fall in line with the already existing automatic teamkill-ban system. I suggest you make an actual Suggestion post though as you have made this in the wrong section (see info at the start of my reply).

As stated above, there are consequences, though long term and not immediate.

All in all you do have some valid points in my personal opinion, but you also have some of the facts wrong. I recommend re adjusting the suggestion and submitting it correctly.

I appreciate the clarification on the report system. You’re right that griefing is eventually punished. The Fair Play posts confirm that. However, my suggestion addresses a separate issue: there’s no in-game consequence that prevents the behavior during the match.

Post-match reports are reactive and long-term. A warning/kick system would be preventive and immediate. The ARB system already does this for aircraft. I’m not saying the report system doesn’t work. I’m saying an in-game deterrent would work better at stopping behavior before it happens.

Regarding posting in Suggestions: I attempted to submit there but was directed to Game Discussion first to build community support. I’ll resubmit to Suggestions with the clarifications you mentioned.

1 Like

Proof in action: harassment based on national insignia and tactical exposure

I just experienced exactly this at minute 6:20 of a recent replay.
https://warthunder.com/en/tournament/replay/489025324216141378
A friendly SPAA began shooting my vehicle; which displays a Ukrainian flag. Immediately, our position was compromised. Checking other players’ perspectives, an enemy Leopard 1A5 heard and saw the harassment, changed course directly toward me, and ambushed me. I barely survived.

“Shooting teammates does absolutely nothing” but it exposed my position in real-time. The enemy player’s decision to push was a direct response to that exposure. That’s not nothing. That’s tactical harm. And when that harassment is targeted based on national insignia, it becomes exactly what the deterrent suggestion addresses.

Whether it’s intentional harassment or negligence, the outcome is identical: I nearly got killed because a teammate deliberately fired on me. That’s why a warning/kick system matters.

2 Likes

No

Speaking of ramming, I respawned in a t-10A, got rammed by a maus who was trying to push me into the open so I’d die. Just J’d out at that point and watched him die instead. I would rather die on my own terms than let someone force me to die to an enemy by ramming me into the open. The fact I could do nothing to escape that fate after I just spawned is ridiculous. Before you say I would have J’d out otherwise, no. I was going to ambush the spawn campers but the rammer ruined it. I will not be a meat shield for someone who does that intentionally.

1 Like

This is exactly what the suggestion addresses. You spawned, had a plan, and a teammate deliberately undermined it through ramming. You had zero in-game way to correct that behavior or prevent it from happening again in future spawns. A warning/kick system would give you that recourse, and it would’ve detered the Maus driver trying and doing it again.

No wonder you J’d out but it also shows the cost: you lost your opportunity to contribute tactically for the team. That’s real damage from a single ramming action. Thanks for sharing it🤙

Based on the clarification from Game Master, Necronomica, I’ve contacted a Senior Suggestion Moderator regarding routing this post to Suggestions/Gameplay. It will probably be up in the next few days to build on the community discussion

1 Like