OK let's get some things very clear. The intent behind the rule is that the intention is to protect either team from getting nailed by 203 fire in spawn to spawn combat. Imagine being at spawn and 3 seconds into it a 203 round from no where lands at your feet. THAT is what is no go.

203 "spam" in other conditions implies that you are firing 203's at nothing for the sake nothing except to luck out to get a kill.

This clearly does not qualify in instances of team oriented cover fire. The 203, much like the SAW, is very useful for firing for effect to cover the team. (I guess another weapon write up will be coming shortly). Be it the window in Weapons Caches, or the roof/windows in Insurgent Camp, etc, 203 shells make for a very intimidating -do not step into that window- message. It also can impair hearing of anyone in the vicinity (unlike the SAW) which can be VERY important for teammates moving up.

Originally Posted by Apophis

You're bombarding a known path/location immediately after round start with the intent of getting easy/free kills as opposed to actually achieving them through any combat/tactical prowess.

In this particular case in Weapons Cache, the assault team has to cover a lot of open ground between their building and the objective building. The window on the 3rd floor is a major threat. Popping 203 rounds up there while your team moves under it is very tactical for cover fire. Even if no defense is there, it is a big enough threat that an opfor can pop in that window throw out a cooked frag or 203 to devestate the incoming assault team.

I think that If someone is unlucky enough to walk in the path of good, tactically placed 203 cover fire, tough noogies.

Common sense here folks. There's a big difference between tactically correct 203 cover fire especially with teamwork in place versus Johnny Rambo running around shooting 203's at god knows what or spawn raping.

Let's not beat the pulp out of a simple rule.