[ad_1]
MW2 gamers have seen that the UAV kill streak is inconsistent with the way it operates throughout the sport.
The UAV, sometimes a modest killstreak in Fashionable Warfare 2, is designed to disclose enemy places with every sweep, granting gamers invaluable intel.
Nevertheless, an rising variety of avid gamers have reported cases the place this seemingly humble killstreak has an surprising surge of energy, copying the capabilities of an Superior UAV.
UAV Killstreak Is Bugged in MW2
The UAV kill streak in MW2 is just not working as supposed. Often, it performs periodic map sweeps, revealing the enemy’s static positions. Nevertheless, it’s now working in one among 3 ways:
- The UAV capabilities as supposed, revealing stationary dots throughout each sweep.
- The UAV operates as an Superior UAV, with dots changing into fastened upon every sweep.
- It briefly exposes enemy motion throughout every sweep, offering a glimpse into the place they’re shifting.
Presently, the rationale for the surprising conduct of this killstreak stays unknown. When using a UAV, it seems there’s a random likelihood of receiving one among three totally different choices.
The UAV is the bottom killstreak in MW2, attainable by selecting up 4 kills or reaching a rating of 500 in-game. Consequently, it stands as an easy-to-earn killstreak reward.
Nevertheless, if gamers occur to get the glitch the place the UAV acts as an Superior UAV, it could possibly considerably disrupt the gameplay and break the sport steadiness.
The builders deliberately designed the Superior UAV as a troublesome killstreak to earn. If gamers can effortlessly get an Superior UAV by acquiring the common model, it could possibly considerably alter the results of matches.
This game-breaking bug is just not on the developer’s radar, because it doesn’t seem on their Trello board.
Name of Responsibility content material creator TheXclusiveAce first identified the UAV killstreak bug. He was the one who found the UAV has three potential outcomes when it ought to solely have one.
You possibly can watch his video about this bug under:
[ad_2]
Source link
