I think a good way to address that without a clunky 'making games always playable' is requiring a disclosure of what the end state of a game looks like when development / support ceases and then let people speak w/ their wallets. If indefinite support is indicated or the intention, well then it has to be spelled out what happens if circumstances prevent that from being fulfilled - ie 'should the servers no longer be available then the game would no longer be accessible'. Same with any dependencies. We're going to hit a point where some indie game is going to rely on some LLM to function and that LLM is going to go away or that endpoint no longer exist and.. poof. That dependency could be spelled out and the potential consequences of that loss to the product being purchased.
Much of this was always implied by any game w/ a mandatory online connection before though, and we've seen this play out in the past so... this still comes across as just a big mob and rabble rousing to me. I get the general intention, and if the end result is better information before someone makes a purchase, great. If it's going to mandate some clunky support / code requirements of all future games released - not so much.
Much of this was always implied by any game w/ a mandatory online connection before though, and we've seen this play out in the past so... this still comes across as just a big mob and rabble rousing to me. I get the general intention, and if the end result is better information before someone makes a purchase, great. If it's going to mandate some clunky support / code requirements of all future games released - not so much.
- 2