Call of Duty: Warzone’s under-barrel shotguns look broken



[ad_1]

Call of Duty: Warzone and Modern warThe fifth season is underway and the players have discovered a potential oversight. The new season has increased the range of the FR 556 rifle, and at least one YouTuber thinks he may have broken another aspect of the gun: the shotgun under the barrel.

In Call of Duty: Warzone, players can attack shotguns under the barrel on some of their weapons, allowing them to switch to a close range weapon very quickly without occupying a second weapon slot. According to TheXclusiveAce, the FR 556’s under-barrel shotgun is normally a two- or three-round shot – not as powerful as the average shotgun. But since the patch, the FR 556’s sub-gun kills with one shot at long range.

In their video, TheXclusiveAce points out that the FR 556’s sub-gun can now kill a fully armored opponent in one hit from 15 meters away. But that’s not a simple buff for all shotguns below the barrel. This only works with the FR 556.

As TheXclusiveAce says, this FR 556 sub-cannon buff is highly unlikely to be intentional. This poses serious problems for Warzone players, because shotguns are generally not as effective at this distance – and certainly not when it is a prop instead of a real shotgun.

The attachment started to gain popularity since the Season 5 patch, with streamers like HusKerrs using it to take out an entire team at once.

In a comment thread on TheXclusiveAce’s video on the Warzone subdirectory, user metalhead4 also claims to have used the FR 556 sub-canon to cause some chaos. “Yeah, I just wiped out a team of 3 very easily with it. One tapped on each of them. Use it while you can, it’s like the only time a shotgun has ever been REAL in this game. ”

TheXclusiveAce mentions some advantages of the bug, like the fact that the FR 556 is not too useful for Warzone, and that you cannot replenish the shotgun under the barrel with standard shotgun ammo. But the alleged bug will continue to frustrate gamers until Infinity Ward implements a fix.

We have contacted Infinity Ward to confirm if this is a bug or if it is working as expected, and will update the story when we have a response.

[ad_2]

Source link