While it's a common complaint when being shot down in Warzone that you didn't see the enemy coming or it appears they came out of nowhere, that could actually be the case right now.
A new skin that can be equipped in the popular battle royale title reportedly makes players invisible to other players, and it's not gone unnoticed in the Warzone community.
In fact, some players have reported this problem taking place since mid-December during the game's Festive Furvor Christmas event.
User tamicheal said on the CODWarzone subreddit: "I think I saw this twice unfortunately I was able to record it.
"The battle pass final skin at 100 every time I seen this guy today he turns invisible or was already. Am I the only one seeing this sometimes?"
Another user commented on the post: "I saw someone with the middle of their body missing and their torso was cut on an angle. I literally died cause I didn't know what it was lol"
In a competitive game like Warzone having an unfair advantage like this is understandably causing a lot of frustration for players.
The Operator skin that appears to be causing the invisibility glitch comes from the Season 1 Battle Pass which can be unlocked at Tier 100.
Called the Awoken Francis skin, many players have reported that only a floating orange mask can be seen after a distance of around 35 meters or so.
Since long-distance fights are a staple in almost every Warzone match, this makes it incredibly difficult for players to actually spot their targets while they could be in full view of the enemy exploiting this glitch.
Some players have even referred to the skin as "pay-to-win" which refers to a system in games where spending money on items gives an unfair advantage over players who don't spend money.
Fallen_EH on Twitter replied to a tweet by Raven Software last week noting they should "Fix pay to win invisible operator skin? Maybe?"
While no official statement has been released by Raven Software on the invisibility glitch yet, it's safe to assume that someone at the company has been made aware of it and it's likely a hotfix will be introduced soon - although it's been two weeks already.
