Call of Duty: Infinite Warfare is a pretty good game! While its multiplayer may be lacking this year, its being hailed for its engaging single player campaign, which leaves the confines of our planet and its moon. It takes several steps away from the established Call of Duty formula, doing fresh and exciting things when it’s not trying to be Call of Duty.
That said, once you’re done with it, you’re probably going to want to play its multiplayer – even if it is almost just like the multiplayer found in the last game. If you’re planning on buying the game on PC though, you may want to skip the Windows 10 Store version.
While it seems to work well enough, this version unfortunately puts you behind a walled garden. The Windows 10 versions of Call of Duty: Infinite Warfare and Modern Warfare Remastered won’t let you play with other PC players who’ve activated their copies through Steam.
This is a pretty serious oversight, as it splits the already dwindling PC Call of Duty player base in two. The Windows 10 version doesn’t have cross play with the Xbox One version either, so there is absolutely no benefit to grabbing the game on the Windows 10 store – other than price.
Right now, on the Windows 10 Store in South Africa, Call of Duty Infinite Warfare is R809. It’s R999 on Steam. The Legacy Edition on Steam (which includes Modern Warfare Remastered) is R1499 on Steam, while it’s R1039 on the Windows 10 Store.
If you’re planning on getting them for their single player, it may be worthwhile – just don’t expect full lobbies in multiplayer. Hopefully this can be rectified with a patch – because walled gardens like this are against the very nature of PC gaming.
According to Microsoft, they’re not to blame here – as evidenced by the cross play between the Windows 10, regular and even Xbox One versions of Gwent being able to talk to each other. That places the blame on Activision, and also suggests it’s something that can be fixed.
Last Updated: November 4, 2016
Viking Of Science
November 4, 2016 at 08:18
screw it, I’m going to blame UWP for this anyway.
November 4, 2016 at 08:21
ActiSoft strikes again…
(Not really, but it sounds cool)