The most recent Call of Duty: Warzone update is causing some unusual changes to parts of the map, creating a strange distortion on Ashika Island. Warzone, with its iconic locations like Al Mazrah, Verdansk, and the Pacific Caldera, has undergone various changes since 2020, and the current map reflects a Modern Warfare 3 theme due to the recent patch.
In addition to the battle royale experience, players can also enjoy an open-world adventure in the new Call of Duty Zombies and the Modern Warfare 3 campaign. While these modes have had their share of issues, Warzone itself has faced a few bugs. The latest update is leading to some confusion as the Ashika Island map undergoes visual alterations, making navigation a bit more challenging.
A Reddit user named Open24Seven recently shared a clip showcasing their Warzone character exploring Ashika while being pursued. The video starts with the player leaving a looted building, only to discover parts of the map floating in the sky. Upon approaching this section, several buildings in the point of interest can be seen far above the usual playing field. The player proceeds to collect items from a Loot Cache before reaching the floating parts of the map. As they get closer, the elevated Warzone map locations flicker in and out of view, occasionally revealing glimpses of what’s supposed to be there.
In the video, Open24Seven is near sections of the map that shouldn’t be there, resembling Verdansk or Al Mazrah instead of Ashika. Many Call of Duty fans have pointed out that this bug has occasionally occurred since the beginning of Warzone Season 1. Some players suggest that it only happens in games with high latency, indicating potential lag on either the player’s end or the server side.
As Warzone is a competitive game, a distracting bug like this could impact a player’s chances of winning. However, considering that Infinity Ward and Raven Software regularly update Call of Duty: Warzone, there’s hope that a future patch will address this issue. Given that players have encountered variations of this bug since the start of Season 1, it’s likely that the developers are already aware and working on a solution.