|
|
|
|
|
|
by RandomGerm4n
17 days ago
|
|
|
> Am I responsible for providing a fallback to EOS, or Steam, or playfab in case their services are decommissioned? In this case, the company offering this service should be responsible for making it possible to host the service independently before discontinuing it. However, games that use such standardized services are actually less problematic in practice. For Steam, for example, there is the Goldberg Steam Emulator, which emulates Steam’s online features. Games that do not have additional DRM or any extra features but simply use the standard Steamworks SDK for multiplayer can be played entirely without the Steam client or server using this emulator.
Even for services that had already been shut down, like Gamespy back then, Openspy quickly emerged as an alternative. Not all games worked right away, but the community fixed most of the issues very quickly. So, in the end, the games that use some kind of custom solution built by the developer themselves are much more important. |
|
|
So AWS are now contractually required to offer all of their managed services to be self hostable or they can’t be used in games?
> For Steam, for example, there is the Goldberg Steam Emulator
So open source reverse engineered solutions are ok? Why aren’t they acceptable for games instead of the underlying platform? Why is it ok for a game that uses steam for online services but not epic (as there’s presumably no equivalent emulator), or an in house tech?
> Games that do not have additional DRM or any extra features but simply use the standard Steamworks SDK for multiplayer can be played entirely without the Steam client or server using this emulator
And those games are unaffected by anything that will come from this law.