Not really, it will be the consequence of requiring the game to be given to the community after the EOL.
> the community are free to reverse engineer the service it relies on
While that is true, it is much harder than receiving the code with the most logic intact. We already do reverse engineer the binaries, including the server protocols, so we know how hard it is. And that's why we know that it's not the way to go.
"I'm not calling for it, but if it happens to be the only way to achieve what I want then so be it".
> While that is true, it is much harder than receiving the code with the most logic intact. We already do reverse engineer the binaries, including the server protocols, so we know how hard it is. And that's why we know that it's not the way to go.
But for many games, the logic _is_ in the remote service calls. Who decides what calls are reversible and which aren't? In a chess game, matchmaking is probably the most important part, for example.
Again, I'm not advocating for some specific architecture. There is more than one way to make a game hostable by players.
> But for many games, the logic _is_ in the remote service calls
Exactly, and this is the issue - you shut down the server and the game becomes bricked.