Windows 10 Store Refunds ‘Call of Duty’ Player Because Nobody's Playing It
motherboard.vice.com
motherboard.vice.com
> Gamers are used to the separation of console and PC multiplayer communities. But PC players aren’t used to companies gating them off based on where they purchased their game. It’s a ludicrous policy that doesn’t serve anyone’s interest and it’s another black eye for a digital storefront that PC gamers already avoid like the plague.
I think that Steam might actually be to blame here. Steam provide the SteamWorks API [1] which handles all the low level networking 'boilerplate' stuff for you so you don't have to, and that actually adds up to quite a lot of functionality: setting up lobbies, player connecting/disconnecting, player authorisation via Steam IDs, voice chat, sending/recieving packets for PvP play, setting up dedicated servers, NAT punching, matchmaking search with filters and so on. There is also the integration with Steam achievements and the Steam Workshop.
For a developer, the API is a no-brainer to use when targeting Steam as a distribution platform. It is problematic though when you want to distribute elsewhere as games using SteamWorks actually require the Steam client to be running in the background in order to work. So I imagine the Windows Store version of the game must use a completely different networking API under the hood, and therefore is incompatible with the Steam version of the game sadly.
Even if the reason for 'cannot work together' would be Steam, I'd say that's great. Let the Windows Store die, sooner the better.
But I don't think that I can follow your thoughts here. If you have to rewrite parts of your code for a non-Steam version (fine, makes sense, sounds plausible) then .. I still don't see why that version is unable to talk to the versions on Steam. In the end these games are talking UDP I assume. If you use Steam for a lot of boiler plate code or implement that stuff differently/yourself: The inability of these two "ports" of the game to talk to one another is not a technological problem, I think. It's a problem of policy/politics.
Assuming there isn't a barrier, then really it is Activision's fault for not integrating the network code properly so Steam and non-Steam players can play together. in either case, I fail to see how this is the Windows Store's fault.
Unlikely. There are Steam games that play cross-platform with PS4/XBONE; Rocket League comes to mind.
I'm sure it's possible to program yourself into a corner in regards to this, but I don't think Steam is forcing you to do so.
I wouldn't exactly blame Steam unless they were forcing you to use their API. I couldn't get to that page. Are they?
Other titles handle it just fine (Rocket League, for example, allows cross play between Steam, Xbox One, and PS4)
It seems this is still on course: http://www.pcworld.com/article/3049669/software-games/the-wi...
If the Windows Store dies (or stays irrelevant for games, forever and ever) than that's a good thing. I agree with your sibling comment: This is good for Valve and as long as Microsoft DOES refund people that use the Windows Store I'd say there's no harm done.