• aksdb@lemmy.world
    link
    fedilink
    English
    arrow-up
    13
    ·
    16 hours ago

    I imagine it’s rather licensing. If they have to provide the software at some point, they can’t use components they are not allowed to distribute. And I agree, that this will impact development costs. But with the law in place, this is not an unexpected cost but one that can be factored in. Might be, that some live services are then no longer viable… but I don’t care. There are more games than anyone could play and games are cancelled or not even started to develop all the time for various reasons. One more or less is just noise.

    • Zagorath@aussie.zone
      link
      fedilink
      English
      arrow-up
      14
      ·
      15 hours ago

      Devs have numerous options for how to address the SKG initiative. The top three that come to my mind are:

      • Release server binaries (along with modifying clients to have a setting to connect to the right server)
      • Modify multiplayer to work over LAN (good when the server’s only/main job is matchmaking)
      • Modify the game itself to no longer require online connectivity

      In the case of live service games, I would suggest option 3 is the most appropriate. If the main gameplay is singleplayer, but it’s online so you can dole out achievements and gatekeep content, the answer is simple: stop doing that. Patch it to all work in-client. And keep in mind that this will be a requirement at end-of-life from the beginning. If it’s an unexpected requirement, that’s going to be a huge development cost. If it’s expected, making that EOL change easy to implement will be part of the code architecture from the start.