everyone plays Call of Duty: Modern Warfare II, which came out today on Xbox or PC find themselves in the shallow trenches of video games, but not in the way they were hoping. Infinity Ward’s first-person shooter seems to have a console preference among Xbox gamers unable to switch off cross play, a feature that allows people on different platforms to play together during the actual gameplay. Meanwhile, PlayStation users can toggle the feature with happy abandon thanks to a built-in option.
Angry Xbox gamers want to avoid PC cheats and precision mice and keyboards, while PC users would rather stay away from consoles. smooth aim assist. PlayStation users, meanwhile, are keeping themselves busy with audio dropouts and be prompted to do so delete their files when they tried to secretly launch a game in another region to get early access.
But at least they’re not worried about crossplay. And Sony has further sweetened its deal – close to release, the call of Duty website listed a few PS4 and PS5 specific perks including monthly Double XP events, +25% Weapon XP when playing with other PS users in a party, and two additional loadout slots after reaching level 4.
Console wars are an expectation for call of Duty
G/O Media may receive a commission
A gift for literally everyone.
Gifts under $20, $10 and even $5. It’s Wish, the catch-all shop for all of the above.
Activision’s current partner Sony instead treats the franchise like a valuable prodigy. And, perhaps to the dismay of Xbox gamers, even after the Microsoft deal is complete, Sony will be in charge call of Duty
So call of DutyThe console wars in the background are not ending any time soon. Meanwhile, Xbox players can go into their settings and block crossplay in the Online Safety & Family tab. From there, select Communication & Multiplayer, then Block People From Outside of Xbox Live. Do this to play Modern Warfare IIhowever, will likely increase your queue times as you can only find more LiGroup of players with the same security settings. You just can’t win.
Update 11:33 am: We’ve updated the headline to reflect the workaround mentioned in the article.